public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
	Andi Shyti <andi.shyti@kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	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 15:04:30 +0200	[thread overview]
Message-ID: <a601dab0-0a9a-4e03-a2ea-e75653758b1c@kernel.org> (raw)
In-Reply-To: <aN5DYZpX1TbF5aLm@kekkonen.localdomain>

Hi,

On 2-Oct-25 11:18 AM, Sakari Ailus wrote:
> Hi Hans,
> 
> On Thu, Oct 02, 2025 at 10:56:47AM +0200, Hans de Goede wrote:
>> Hi,

...

>>>> INTC10D2 is apparently already claimed by the LJCA I²C driver. Do you have
>>>> an actual system that uses USBIO and this HID?
>>>
>>> Actually it looks like i2c-ljca.c shouldn't list this HID. The same
>>> probably goes for all 10CF--10D3.
>>
>> I would not be so sure of this, there are at least some Dell systems
>> which use a combination of ljca and Meteor Lake and I believe these
>> do use the "INTC10D2" HID with LJCA for the I2C part and the same
>> goes for the GPIO / SPI parts.. One example of such a system is
>> the Dell Precision 5490.
> 
> LJCA on MTL is supposed to be 1008. Do you have the *SDT so we could verify
> this?

I just checked this in a ssh session to the Dell Precision 5490:

hans@prdel:~$ cd /sys/bus/auxiliary/devices/
hans@prdel:/sys/bus/auxiliary/devices$ ls
intel_ipu6.isys.40      intel_vsec.telemetry.2  soundwire_intel.link.2  usb_ljca.ljca-i2c.1
intel_ipu6.psys.40      snd_sof.hda-probes.0    soundwire_intel.link.3  usb_ljca.ljca-spi.0
intel_vsec.telemetry.0  soundwire_intel.link.0  usb_ljca.ljca-gpio.0
intel_vsec.telemetry.1  soundwire_intel.link.1  usb_ljca.ljca-i2c.0
hans@prdel:/sys/bus/auxiliary/devices$ cat usb_ljca.ljca-*/firmware_node/hid 
INTC10D1
INTC10D2
INTC10D2
INTC10D3

So as you can see this really is using the INTC10D* HIDs and these
are thus duplicate between the LJCA and USBIO IO-expanders.

Note this does not really cause problems since 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.

I've also asked for an acpidump, do you still want that once I receive it ?

Regards,

Hans






  parent reply	other threads:[~2025-10-02 13:04 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 [this message]
2025-10-02 15:52         ` Cepeda Lopez, Israel A
2025-10-02 17:49           ` Hans de Goede
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=a601dab0-0a9a-4e03-a2ea-e75653758b1c@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