pinctrl: cherryview: Associate IRQ descriptors to irqdomain
authorMika Westerberg <mika.westerberg@linux.intel.com>
Wed, 25 Apr 2018 10:32:11 +0000 (13:32 +0300)
committerLinus Walleij <linus.walleij@linaro.org>
Wed, 2 May 2018 12:35:59 +0000 (14:35 +0200)
commit83b9dc11312f48a561594a895672abb6cb2a2250
tree655ee05726ed132d35cbbdc1b636650433c3a59d
parentb84e54616a946f24eeeca8762cb70a9074b045e7
pinctrl: cherryview: Associate IRQ descriptors to irqdomain

When we dropped the custom Linux GPIO translation it resulted that the
IRQ numbers changed slightly as well. Normally this would be fine
because everyone is expected to use controller relative GPIO numbers and
ACPI GpioIo/GpioInt resources. However, there is a certain set of
Intel_Strago based Chromebooks where i8042 keyboard controller IRQ
number is hardcoded be 182 (this is corrected with newer coreboot but
the older ones still have the hardcoded Linux IRQ number). Because of
this hardcoded IRQ number keyboard on those systems accidentally broke
again.

Fix this by iteratively associating IRQ descriptors to the chip irqdomain
so that there are no gaps on those systems. Other systems are not
affected.

Fixes: 03c4749dd6c7 ("gpio / ACPI: Drop unnecessary ACPI GPIO to Linux GPIO translation")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=199463
Reported-by: Sultan Alsawaf <sultanxda@gmail.com>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
drivers/pinctrl/intel/pinctrl-cherryview.c