From: Guenter Roeck <linux@roeck-us.net>
To: Frank Crawford <frank@crawford.emu.id.au>,
Ai Chao <aichao@kylinos.cn>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (it87) Add support for IT8625E
Date: Tue, 22 Oct 2024 06:40:57 -0700 [thread overview]
Message-ID: <300383ee-3ead-439e-893e-895f3ed49805@roeck-us.net> (raw)
In-Reply-To: <6cab565f05820eb2e1a1c55644be057427ecdf2e.camel@crawford.emu.id.au>
On 10/22/24 03:13, Frank Crawford wrote:
> On Tue, 2024-10-22 at 17:13 +0800, Ai Chao wrote:
>> Add support for IT8625E on Centerm P410.
>>
>> Signed-off-by: Ai Chao <aichao@kylinos.cn>
>> ---
>> change for v2
>> - Move IT8625E_DEVID after IT8623E_DEVID
>> ---
>> drivers/hwmon/it87.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/hwmon/it87.c b/drivers/hwmon/it87.c
>> index e233aafa8856..4aeb09f3bfdf 100644
>> --- a/drivers/hwmon/it87.c
>> +++ b/drivers/hwmon/it87.c
>> @@ -15,6 +15,7 @@
>> * IT8620E Super I/O chip w/LPC interface
>> * IT8622E Super I/O chip w/LPC interface
>> * IT8623E Super I/O chip w/LPC interface
>> + * IT8625E Super I/O chip w/LPC interface
>> * IT8628E Super I/O chip w/LPC interface
>> * IT8705F Super I/O chip w/LPC interface
>> * IT8712F Super I/O chip w/LPC interface
>> @@ -161,6 +162,7 @@ static inline void superio_exit(int ioreg, bool noexit)
>> #define IT8620E_DEVID 0x8620
>> #define IT8622E_DEVID 0x8622
>> #define IT8623E_DEVID 0x8623
>> +#define IT8625E_DEVID 0x8625
>> #define IT8628E_DEVID 0x8628
>> #define IT87952E_DEVID 0x8695
>>
>> @@ -2782,6 +2784,7 @@ static int __init it87_find(int sioaddr, unsigned short *address,
>> case IT8622E_DEVID:
>> sio_data->type = it8622;
>> break;
>> + case IT8625E_DEVID:
>> case IT8628E_DEVID:
>> sio_data->type = it8628;
>> break;
>
> Can I just add that it isn't a good idea to use the same type for
> different chips. There are some specific differences between the
> chips, which mean that it should have its own entry in
>
> static const struct it87_devices it87_devices[]
>
> even if currently they are very similar.
>
According to the information I have, the ADC voltage is different,
and 8628 supports PECI but 8625 doesn't. Most importantly, 8625
has multiple register banks. There are also some differences in
fan control; 8628 can explicitly turn fans off using register bits.
Just mapping the chip to it8628 may be convenient, but it is not
acceptable.
Guenter
next prev parent reply other threads:[~2024-10-22 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:13 Ai Chao
2024-10-22 10:13 ` Frank Crawford
2024-10-22 13:40 ` Guenter Roeck [this message]
2024-10-23 12:41 ` Ahmad Khalifa
2024-10-23 15:42 ` Guenter Roeck
2024-10-23 22:19 ` Ahmad Khalifa
2024-10-24 0:47 ` 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=300383ee-3ead-439e-893e-895f3ed49805@roeck-us.net \
--to=linux@roeck-us.net \
--cc=aichao@kylinos.cn \
--cc=frank@crawford.emu.id.au \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®