From: Wolfram Sang <wsa@the-dreams.de>
To: Adam Honse <calcprogrammer1@gmail.com>
Cc: jdelvare@suse.de, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: Detect secondary SMBus controller on AMD AM4 chipsets
Date: Wed, 15 Apr 2020 12:28:24 +0200 [thread overview]
Message-ID: <20200415102823.GI1141@ninjato> (raw)
In-Reply-To: <20200410204843.3856-1-calcprogrammer1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Fri, Apr 10, 2020 at 03:48:44PM -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.
>
> Signed-off-by: Adam Honse <calcprogrammer1@gmail.com>
>
Reformatted the patch description, added Sebastians tags and applied to
for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-15 10:30 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
2020-04-14 7:35 ` Jean Delvare
2020-04-15 10:28 ` Wolfram Sang [this message]
-- 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=20200415102823.GI1141@ninjato \
--to=wsa@the-dreams.de \
--cc=calcprogrammer1@gmail.com \
--cc=jdelvare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).