From: Jonas Gorski <jonas.gorski@gmail.com>
To: linux-acpi@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: i2c-mux ACPI parent device references in example
Date: Wed, 8 Oct 2025 11:14:37 +0200 [thread overview]
Message-ID: <48d0fb45-096c-4caa-b51c-753c2f17f018@gmail.com> (raw)
Hi,
I'm currently trying to wrap my head around describing devices via SSDT.
While reading Documentation/firmware-guide/acpi/i2c-muxes.rst, the
references used for the devices behind the mux confuse me a bit.
The tree from the example is:
Device (SMB1)
{
Device (MUX0)
{
Device (CH00)
{
Device (CLIA)
{
Name (_CRS, ResourceTemplate () {
I2cSerialBus (0x50, ControllerInitiated, I2C_SPEED,
AddressingMode7Bit, "\\_SB.SMB1.CH00", 0x00,
ResourceConsumer,,)
}
}
}
Device (CH01)
{
Device (CLIB)
{
Name (_CRS, ResourceTemplate () {
I2cSerialBus (0x50, ControllerInitiated, I2C_SPEED,
AddressingMode7Bit, "\\_SB.SMB1.CH01", 0x00,
ResourceConsumer,,)
}
}
}
}
}
Is there a ".MUX0" missing in the references, or is it correct that it is not
present?
E.g. should it be "\\_SB.SMB1.MUX0.CH00" instead of "\\_SB.SMB1.CH00"?
FWIW, the references were changed from relative to absolute in e65cb011349e
("Documentation: ACPI: Fix parent device references").
Best regards,
Jonas
next reply other threads:[~2025-10-08 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 9:14 Jonas Gorski [this message]
2025-10-18 19:41 ` i2c-mux ACPI parent device references in example Andy Shevchenko
2025-10-21 7:31 ` Jonas Gorski
2025-10-23 18:59 ` Andy Shevchenko
2025-10-27 19:28 ` Jonas Gorski
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=48d0fb45-096c-4caa-b51c-753c2f17f018@gmail.com \
--to=jonas.gorski@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@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).