From: Hans de Goede <hansg@kernel.org>
To: "Cepeda Lopez, Israel A" <israel.a.cepeda.lopez@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 1/2] i2c: usbio: Add ACPI device-id for MTL-CVF devices
Date: Thu, 2 Oct 2025 19:49:12 +0200 [thread overview]
Message-ID: <056ae17a-5351-4be7-a14e-9becf8ec404c@kernel.org> (raw)
In-Reply-To: <DS4PPF11A2D567239809FF8803DAC6E7704FAE7A@DS4PPF11A2D5672.namprd11.prod.outlook.com>
Hi Israel,
On 2-Oct-25 5:52 PM, Cepeda Lopez, Israel A wrote:
> Hi Hans,
>
> LJCA and USBIO shouldn't be sharing HIDs.
Yes in practice we have shipping hardware that is sharing HIDs
and since this is hardware out there in the field there is
nothing we can do about this.
> What is the USB IO expander in that system (lsusb)?
Dell Precision 5490: 8086:0b63 usb-ljca device
with INTC10D1, INTC10D2 and INTC10D3 ACPI children
Dell Latitude 7450: 2ac1:20c9 usbio device
with INTC10D1 and INTC10D2 ACPI children
As I already mentioned earlier in this thread the shared HIDs are not
really a problem because we have the USB driver binding by USB VID:PID
first and only then the code looks for the ACPI HIDs for the GPIO/I2C/SPI
children so at this point we are already in LJCA resp. USBIO specific
code-paths.
Regards,
Hans
next prev parent reply other threads:[~2025-10-02 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 21:23 [PATCH 1/2] i2c: usbio: Add ACPI device-id for MTL-CVF devices Hans de Goede
2025-10-01 21:58 ` Sakari Ailus
2025-10-01 22:09 ` Sakari Ailus
2025-10-02 8:56 ` Hans de Goede
2025-10-02 9:18 ` Sakari Ailus
2025-10-02 12:03 ` Hans de Goede
2025-10-02 13:04 ` Hans de Goede
2025-10-02 15:52 ` Cepeda Lopez, Israel A
2025-10-02 17:49 ` Hans de Goede [this message]
2025-10-02 18:05 ` Cepeda Lopez, Israel A
2025-10-04 14:03 ` Hans de Goede
2025-10-09 1:50 ` Cepeda Lopez, Israel A
2025-10-06 6:29 ` Sakari Ailus
2025-10-14 11:58 ` Wolfram Sang
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=056ae17a-5351-4be7-a14e-9becf8ec404c@kernel.org \
--to=hansg@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wsa+renesas@sang-engineering.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