i2c: Detect secondary SMBus controller on AMD AM4 chipsets
PATCH 1/1 i2c: Detect secondary SMBus controller on AMD AM4 chipsets
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 ([email protected])
--- drivers/i2c/busses/i2c-piix4.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/i2c/busses/i2c-piix4.c +5 -0
@@ -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 */
Signature · 1 line
2.25.1
Hi Adam,
Quoted 7 lines · Adam Honse
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 ([email protected])
In order for this patch to be acceptable, this would need to be turned into a proper Signed-off-by statement. Please see:
Quoted 11 lines
--- drivers/i2c/busses/i2c-piix4.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/i2c/busses/i2c-piix4.c +0
-0@@ -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 );
drivers/i2c/busses/i2c-piix4.c static int piix4_probe(struct pci_dev *dev, const struct pci_device_id *id) · line 991
Quoted 10 lines
drivers/i2c/busses/i2c-piix4.c +5
-0} +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?
Signature · 2 lines
Jean Delvare SUSE L3 Support
Hi Adam,
Quoted 6 lines · Adam Honse
I'm not sure what all chipsets are covered by the KERNCZ ID. We have found that the secondary bus exists on all AM4 chipsets and on X399 as well. Considering the older Hudson 2 has the same secondary bus (which is correctly detected without a patch on my old FM1 home server, also at
0x0B20) I would believe the secondary bus exists on all chipsets. I could add a revision check though. My X370 reports (rev 59) in lspci.
Fair enough, let's assume it's present on all chipsets and we can refine later if needed.
If so, can you please merge the kerncz check with the hudson2 check right before as we do the same for both?
Then please submit with your Signed-off-by statement and I'll review and ack the patch for Wolfram to commit.
Thanks,
Signature · 2 lines
Jean Delvare SUSE L3 Support