Re: [PATCH v2] pinctrl: intel: Fix Jasperlake HOSTSW_OWN offset

2020-11-12 Thread Andy Shevchenko
On Thu, Nov 12, 2020 at 11:11:00AM +0200, Mika Westerberg wrote: > On Wed, Nov 11, 2020 at 03:17:28PM -0800, Evan Green wrote: > > GPIOs that attempt to use interrupts get thwarted with a message like: > > "pin 161 cannot be used as IRQ" (for instance with SD_CD). This is because > > the HOSTSW_OWN

Re: [PATCH v2] pinctrl: intel: Fix Jasperlake HOSTSW_OWN offset

2020-11-12 Thread Mika Westerberg
On Wed, Nov 11, 2020 at 03:17:28PM -0800, Evan Green wrote: > GPIOs that attempt to use interrupts get thwarted with a message like: > "pin 161 cannot be used as IRQ" (for instance with SD_CD). This is because > the HOSTSW_OWN offset is incorrect, so every GPIO looks like it's > owned by ACPI. > >

[PATCH v2] pinctrl: intel: Fix Jasperlake HOSTSW_OWN offset

2020-11-11 Thread Evan Green
GPIOs that attempt to use interrupts get thwarted with a message like: "pin 161 cannot be used as IRQ" (for instance with SD_CD). This is because the HOSTSW_OWN offset is incorrect, so every GPIO looks like it's owned by ACPI. Fixes: e278dcb7048b1 ("pinctrl: intel: Add Intel Jasper Lake pin contro