From: Guenter Roeck <linux@roeck-us.net>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH] hwmon: Remove obsolete adm1021 and max6642 drivers
Date: Sat, 13 Jul 2024 11:53:00 -0700 [thread overview]
Message-ID: <e263f50e-ffc7-4208-b1a5-960be94569dd@roeck-us.net> (raw)
In-Reply-To: <ZpKbxZf6TOqid1cP@tzungbi-laptop>
Hi,
On 7/13/24 08:22, Tzung-Bi Shih wrote:
> On Fri, Jul 12, 2024 at 10:35:48AM -0700, Guenter Roeck wrote:
>> diff --git a/drivers/hwmon/adm1021.c b/drivers/hwmon/adm1021.c
> [...]
>> -static const struct i2c_device_id adm1021_id[] = {
>> - { "adm1021", adm1021 },
>> - { "adm1023", adm1023 },
>> - { "max1617", max1617 },
>> - { "max1617a", max1617a },
>
> The device ID "max1617a" only in Documentation/hwmon/lm90.rst but not in
> drivers/hwmon/lm90.c which results in max1617a is no longer supported after
> applying the patch.
>
Thanks for noticing. It is an oversight, really. The chip is the same.
max1617a is even mentioned in the lm90 documentation.
The chip is detected and supported as "max1617" in the lm90 driver.
Here are the notes from that driver.
* Note: Multiple chips with different markings labeled as
* "MAX1617" (no "A") were observed to report manufacturer ID
* 0x4d and device ID 0x01. It is unknown if other variants of
* MAX1617/MAX617A with different behavior exist. The detection
* code below works for those chips.
Not sure if I should mark the chips as max1617a instead of max1617
or just update the documentation.
Either case, all configurations enabling the adm1021 driver also enable the
lm90 driver, and that in turn prevents the adm1021 driver from being built.
Effectively that means that the adm1021 driver hasn't been built for a long
time.
Thanks,
Guenter
next prev parent reply other threads:[~2024-07-13 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 17:35 [PATCH] hwmon: Remove obsolete adm1021 and max6642 drivers Guenter Roeck
2024-07-13 15:22 ` Tzung-Bi Shih
2024-07-13 18:53 ` Guenter Roeck [this message]
2024-07-14 7:06 ` Tzung-Bi Shih
2024-07-14 12:38 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e263f50e-ffc7-4208-b1a5-960be94569dd@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=tzungbi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox