Commit 711e2e4f authored by Andrew Davis's avatar Andrew Davis Committed by Guenter Roeck

hwmon: (lm90) Remove use of i2c_match_id()

The function i2c_match_id() is used to fetch the matching ID from
the i2c_device_id table. This is often used to then retrieve the
matching driver_data. This can be done in one step with the helper
i2c_get_match_data().

This helper has a couple other benefits:
 * It doesn't need the i2c_device_id passed in so we do not need
   to have that forward declared, allowing us to remove those or
   move the i2c_device_id table down to its more natural spot
   with the other module info.
 * It also checks for device match data, which allows for OF and
   ACPI based probing. That means we do not have to manually check
   those first and can remove those checks.
Signed-off-by: default avatarAndrew Davis <afd@ti.com>
Link: https://lore.kernel.org/r/20240403203633.914389-18-afd@ti.comSigned-off-by: default avatarGuenter Roeck <linux@roeck-us.net>
parent 4cfd3cee
...@@ -2723,10 +2723,7 @@ static int lm90_probe(struct i2c_client *client) ...@@ -2723,10 +2723,7 @@ static int lm90_probe(struct i2c_client *client)
INIT_WORK(&data->report_work, lm90_report_alarms); INIT_WORK(&data->report_work, lm90_report_alarms);
/* Set the device type */ /* Set the device type */
if (client->dev.of_node) data->kind = (uintptr_t)i2c_get_match_data(client);
data->kind = (uintptr_t)of_device_get_match_data(&client->dev);
else
data->kind = i2c_match_id(lm90_id, client)->driver_data;
/* /*
* Different devices have different alarm bits triggering the * Different devices have different alarm bits triggering the
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment