On 06/04/17 14:18, Mika Westerberg wrote: > On Thu, Apr 06, 2017 at 12:05:28PM +0100, Marc Zyngier wrote: >>> There is a proper way to use GPIOs as interrupts in ACPI, namely GpioInt >>> resource but it has not been used in that particular machine for some >>> reason. >> >> OK, that explains it. One thing you could try would be to allocate the >> domain as a legacy one, which allows you to specify the virtual >> interrupt range you require. Not sure that's any better though. > > Yeah, then I would have to add a whole bunch of code to handle custom > irqdomain just to support this one machine (fingers crossed that it is > limited to only this particular machine). > > If no objections, I would rather stick to the approach used in this > patch. I will just update the DMI strings to include BIOS version/date. Fair enough. Though I have the ugly feeling that we're going to see this cropping up again in a couple of releases, when some ordering changes affect the interrupts allocated to this domain. Another thing worth exploring would be to actually quirk the i8042 driver to override the ACPI interrupt. That would have a better chance of working in the long term. Thanks, M. -- Jazz is not dead. It just smells funny... -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html