On Tue, Mar 07, 2023 at 03:48:52PM +0100, Benjamin Tissoires wrote: > On Mar 07 2023, Daniel Kaehn wrote: ... > So I can see that the device gets probed, and that all ACPI resources > are tried to get the IRQ. > Right now, I see that it's attempting to bind to the acpi resource in > acpi_dev_resource_interrupt() (in file drivers/acpi/resources.c), but > instead of having a ACPI_RESOURCE_TYPE_EXTENDED_IRQ I only get a > ACPI_RESOURCE_TYPE_GPIO for the GpioInt() definition in the _CRS method. > > So I am missing the proper transition from GpioInt to IRQ in the acpi. I'm not sure I understand what this means. The Linux kernel takes either Interrupt() resource (which is IOxAPIC / GIC / etc) or GpioInt() (which is GPIO based). In both cases I²C framework submits this into client's IRQ field. -- With Best Regards, Andy Shevchenko
