Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Aleksander Mazur <deweloper@wp.pl>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (f71882fg) Add support for F71858AD (0x0903)
Date: Sun, 5 Jun 2022 10:39:46 -0700	[thread overview]
Message-ID: <20220605173946.GA3144440@roeck-us.net> (raw)
In-Reply-To: <20220605012114.3d85a75a@mocarz>

On Sun, Jun 05, 2022 at 01:21:14AM +0200, Aleksander Mazur wrote:
> Treat F71858AD like F71858FG.
> 
> Tested on Igel D220.
> 
> Signed-off-by: Aleksander Mazur <deweloper@wp.pl>

Applied to hwmon-next.

Thanks,
Guenter

> ---
>  drivers/hwmon/f71882fg.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/hwmon/f71882fg.c b/drivers/hwmon/f71882fg.c
> index 6830e029995d..19b6c643059a 100644
> --- a/drivers/hwmon/f71882fg.c
> +++ b/drivers/hwmon/f71882fg.c
> @@ -49,6 +49,7 @@
>  #define SIO_F81768D_ID		0x1210	/* Chipset ID */
>  #define SIO_F81865_ID		0x0704	/* Chipset ID */
>  #define SIO_F81866_ID		0x1010	/* Chipset ID */
> +#define SIO_F71858AD_ID		0x0903	/* Chipset ID */
>  #define SIO_F81966_ID		0x1502	/* Chipset ID */
>  
>  #define REGION_LENGTH		8
> @@ -2638,6 +2639,7 @@ static int __init f71882fg_find(int sioaddr, struct f71882fg_sio_data *sio_data)
>  		sio_data->type = f71808a;
>  		break;
>  	case SIO_F71858_ID:
> +	case SIO_F71858AD_ID:
>  		sio_data->type = f71858fg;
>  		break;
>  	case SIO_F71862_ID:

      reply	other threads:[~2022-06-05 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 23:21 [PATCH] hwmon: (f71882fg) Add support for F71858AD (0x0903) Aleksander Mazur
2022-06-05 17:39 ` Guenter Roeck [this message]

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=20220605173946.GA3144440@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=deweloper@wp.pl \
    --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