All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Adam Honse <calcprogrammer1@gmail.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: Detect secondary SMBus controller on AMD AM4 chipsets
Date: Tue, 14 Apr 2020 09:34:08 +0200	[thread overview]
Message-ID: <20200414093408.1a1209eb@endymion> (raw)
In-Reply-To: <20200410204843.3856-1-calcprogrammer1@gmail.com>

Hi Adam,

On Fri, 10 Apr 2020 15:48:44 -0500, Adam Honse wrote:
> The AMD X370 and other AM4 chipsets (A/B/X 3/4/5 parts) and Threadripper equivalents have a secondary SMBus controller at I/O port address 0x0B20.  This bus is used by several manufacturers to control motherboard RGB lighting via embedded controllers.  I have been using this bus in my OpenRGB project to control the Aura RGB on many motherboards and ASRock also uses this bus for their Polychrome RGB controller.
> 
> See this kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=202587
> 
> I am not aware of any CZ-compatible platforms which do not have the second SMBus channel.  All of AMD's AM4- and Threadripper- series chipsets that OpenRGB users have tested appear to have this secondary bus.  I also noticed this secondary bus is present on older AMD platforms including my FM1 home server.

Please wrap the patch description at 75 columns. Note that
./scripts/checkpatch.pl would tell you about that.

Maybe Wolfram can fix if for your this time, if not you'll have to
resubmit.

> 
> Signed-off-by: Adam Honse <calcprogrammer1@gmail.com>
> 
> ---
>  drivers/i2c/busses/i2c-piix4.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
> index 30ded6422e7b..69740a4ff1db 100644
> --- a/drivers/i2c/busses/i2c-piix4.c
> +++ b/drivers/i2c/busses/i2c-piix4.c
> @@ -977,7 +977,8 @@ static int piix4_probe(struct pci_dev *dev, const struct pci_device_id *id)
>  	}
>  
>  	if (dev->vendor == PCI_VENDOR_ID_AMD &&
> -	    dev->device == PCI_DEVICE_ID_AMD_HUDSON2_SMBUS) {
> +	    (dev->device == PCI_DEVICE_ID_AMD_HUDSON2_SMBUS ||
> +	     dev->device == PCI_DEVICE_ID_AMD_KERNCZ_SMBUS)) {
>  		retval = piix4_setup_sb800(dev, id, 1);
>  	}
>  

Fine with me.

Reviewed-by: Jean Delvare <jdelvare@suse.de>

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2020-04-14  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 20:48 [PATCH] i2c: Detect secondary SMBus controller on AMD AM4 chipsets Adam Honse
2020-04-14  7:34 ` Jean Delvare [this message]
2020-04-14  7:35 ` Jean Delvare
2020-04-15 10:28 ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2020-03-29 17:44 Adam Honse
2020-03-30 16:31 ` Jean Delvare
     [not found]   ` <CAD_xsFPMx5zPuqEcaCq3urdFzrpvrY1NuoH-WqTWvNPNXn+sVA@mail.gmail.com>
2020-04-10  7:55     ` Jean Delvare

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=20200414093408.1a1209eb@endymion \
    --to=jdelvare@suse.de \
    --cc=calcprogrammer1@gmail.com \
    --cc=linux-i2c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.