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: Mon, 30 Mar 2020 18:31:08 +0200	[thread overview]
Message-ID: <20200330183108.58c63736@endymion> (raw)
In-Reply-To: <20200329174440.19342-1-calcprogrammer1@gmail.com>

Hi Adam,

On Sun, 29 Mar 2020 12:44:40 -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
> 
> Thanks,
> 
> Adam Honse (calcprogrammer1@gmail.com)

In order for this patch to be acceptable, this would need to be turned
into a proper Signed-off-by statement. Please see:

https://www.kernel.org/doc/html/v5.5/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin

> 
> ---
>  drivers/i2c/busses/i2c-piix4.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
> index 30ded6422e7b..6068364b84f6 100644
> --- a/drivers/i2c/busses/i2c-piix4.c
> +++ b/drivers/i2c/busses/i2c-piix4.c
> @@ -981,6 +981,11 @@ static int piix4_probe(struct pci_dev *dev, const struct pci_device_id *id)
>  		retval = piix4_setup_sb800(dev, id, 1);
>  	}
>  
> +	if (dev->vendor == PCI_VENDOR_ID_AMD &&
> +	    dev->device == PCI_DEVICE_ID_AMD_KERNCZ_SMBUS) {
> +		retval = piix4_setup_sb800(dev, id, 1);
> +	}
> +
>  	if (retval > 0) {
>  		/* Try to add the aux adapter if it exists,
>  		 * piix4_add_adapter will clean up if this fails */

I'm a bit worried about this change. Sure it works on the systems which
do have the second SMBus channel, but what about the systems which
don't? If there no device revision that needs to be checked to ensure
that the second channel is present?

This patch needs to be tested on tested on systems with CZ-compatible
CPUs which do not have the second SMBus channel. Or do you believe they
all do have it?

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2020-03-30 16:31 UTC|newest]

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

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=20200330183108.58c63736@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.