[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90a41ea2-9a83-4245-88c7-b8dd97f5aabf@roeck-us.net>
Date: Thu, 26 Dec 2024 12:54:27 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: tjakobi@...h.uni-bielefeld.de
Cc: Derek John Clark <derekjohn.clark@...il.com>,
Joaquín Ignacio Aramendía <samsagax@...il.com>,
Jean Delvare <jdelvare@...e.com>, linux-hwmon@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] hwmon: (oxp-sensors) Separate logic from
device-specific data
On Thu, Dec 26, 2024 at 06:00:16PM +0100, tjakobi@...h.uni-bielefeld.de wrote:
> From: Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
>
> We currently have large switch-statements in all functions that
> write to EC registers, even though the bulk of the supported
> devices functions more or less the same.
>
> Factor the device-specific data out into a struct oxp_config. This
> only leaves logic in the corresponding functions and should make
> adding future devices much easier and less error-prone.
>
> Also introduce struct oxp_data which is going to be used in a
> later commit to cache device state.
>
> Signed-off-by: Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
> ---
> drivers/hwmon/oxp-sensors.c | 517 +++++++++++++++---------------------
> 1 file changed, 215 insertions(+), 302 deletions(-)
>
...
> +
> static const struct dmi_system_id dmi_table[] = {
> {
> .matches = {
> DMI_MATCH(DMI_BOARD_VENDOR, "AOKZOE"),
> DMI_EXACT_MATCH(DMI_BOARD_NAME, "AOKZOE A1 AR07"),
> },
> - .driver_data = (void *)aok_zoe_a1,
> + .driver_data = (void *)&config_aok_zoe,
I have not looked at hte rest of the code, but the whole point of
void * is that a tyoe cast to or from it is not necessary.
Guenter
Powered by blists - more mailing lists