From: Jean Delvare <jdelvare@suse.de>
To: Jon P <theroguezeta@gmail.com>
Cc: linux-i2c@vger.kernel.org, Adam Honse <calcprogrammer1@gmail.com>,
Terry Bowman <Terry.Bowman@amd.com>
Subject: Re: i2c-tools does not work with AMD Cezanne APU's
Date: Wed, 19 Jan 2022 11:51:54 +0100 [thread overview]
Message-ID: <20220119115154.1ee789e9@endymion> (raw)
In-Reply-To: <CAPoa-_rS8foktCEU+aGFcWiVgmB7Tv92z5r0gX0Dk1DS0LcsiA@mail.gmail.com>
Hi Jon,
On Tue, 18 Jan 2022 17:26:03 -0800, Jon P wrote:
> After updating to a 5700G APU from a 2400G on my B450 board I am not
> able to access i2c interfaces which is a blocking issue to use OpenRGB
> on the DRAM and motherboard RGB controller (I am one of the developers
> of OpenRGB).
>
> I have opened an issue with the distribution that I am using and
> multiple other users are seeing the same issue but I have not seen any
> updates on the issue or request for more details so I am afraid that
> it has just gone into the void. Full details here:
> https://bugs.launchpad.net/bugs/1950062
>
> I see the same issues when using the i2c-tools as well when I am
> trying to read the DRAM so following the man page I would like to
> report a bug using the i2c-tools with AMD Cezanne APU's.
From your logs, the i2c bus itself is not working. So this is
definitely not an i2c-tools issue, but a kernel driver issue.
Most likely this is related to the required change of register access
method for recent AMD chipsets which has been discussed recently:
https://lore.kernel.org/linux-i2c/20220118221152.300444-1-terry.bowman@amd.com/T/#t
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2022-01-19 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPoa-_rth53JPWJB-c9hB+PCjyU=MvAHa2Db0h=ghciMgphvgQ@mail.gmail.com>
2022-01-19 1:26 ` i2c-tools does not work with AMD Cezanne APU's Jon P
2022-01-19 10:51 ` Jean Delvare [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=20220119115154.1ee789e9@endymion \
--to=jdelvare@suse.de \
--cc=Terry.Bowman@amd.com \
--cc=calcprogrammer1@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=theroguezeta@gmail.com \
/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).