public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Florian Eckert <fe@dev.tdt.de>
Cc: Konstantin Aladyshev <aladyshev22@gmail.com>,
	linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: Adding I2C devices to the SMBus (PIIX4) via the ACPI SSDT overlay method
Date: Fri, 8 Nov 2024 13:23:29 +0200	[thread overview]
Message-ID: <Zy30sTgK9MER2bD1@smile.fi.intel.com> (raw)
In-Reply-To: <7fc0f59b8264e965efc96c0aa0ba4c31@dev.tdt.de>

On Fri, Nov 08, 2024 at 10:27:08AM +0100, Florian Eckert wrote:
> On 2024-11-08 09:46, Andy Shevchenko wrote:
> > +Cc: Florian (as this indeed rang a bell to me)
> > 
> > https://lore.kernel.org/all/d84fb798722762862a7fb08f1e343b6a@dev.tdt.de/
> 
> The message was forwarded by Andy because I had a similar problem with my
> APU3 [1]
> from PC-engine [2], which is also using the PIIX4 for I2C (SMBUS).
> 
> > > Maybe I need to modify ACPI code somehow to create these
> > > 'physical_nodesX' folders for the relevant i2c-7/8/9 buses?
> 
> I don't know if that helps, but with the following SSDT overlay I managed
> to get the driver to feel responsible for the mcp23017 via the I2C (SMBUS)
> of the APU3. The mcp23017 is used on my APU3 to add additional LEDs to
> '/sys/class/leds'.

Thanks for prompt response!
Can you, folks, elaborate and update the in-kernel documentation [1]
by adding a section to it for the above topic, so next time I have got
a Q like this I can point to there?

[1]: Documentation/i2c/busses/i2c-piix4.rst

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-11-08 11:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 15:51 Adding I2C devices to the SMBus (PIIX4) via the ACPI SSDT overlay method Konstantin Aladyshev
2024-11-08  8:26 ` Andy Shevchenko
2024-11-08  8:29   ` Andy Shevchenko
2024-11-08  8:46 ` Andy Shevchenko
2024-11-08  9:27   ` Florian Eckert
2024-11-08 11:23     ` Andy Shevchenko [this message]
2024-11-08 11:48     ` Konstantin Aladyshev
2024-11-08 12:47       ` Andy Shevchenko
2024-11-11 12:09         ` Konstantin Aladyshev
2024-11-11 12:48           ` Andy Shevchenko

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=Zy30sTgK9MER2bD1@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=aladyshev22@gmail.com \
    --cc=fe@dev.tdt.de \
    --cc=linux-acpi@vger.kernel.org \
    --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