summaryrefslogtreecommitdiffstats
path: root/samples/Kconfig
diff options
context:
space:
mode:
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>2022-11-24 23:29:26 +0100
committerLinus Walleij <linus.walleij@linaro.org>2022-11-28 21:41:31 +0100
commit6989ea4881c8944fbf04378418bb1af63d875ef8 (patch)
treee447273b3767f6ac11a901fd53f2bf00dcec9ba4 /samples/Kconfig
parentpinctrl: meditatek: Startup with the IRQs disabled (diff)
downloadlinux-6989ea4881c8944fbf04378418bb1af63d875ef8.tar.xz
linux-6989ea4881c8944fbf04378418bb1af63d875ef8.zip
pinctrl: intel: Save and restore pins in "direct IRQ" mode
The firmware on some systems may configure GPIO pins to be an interrupt source in so called "direct IRQ" mode. In such cases the GPIO controller driver has no idea if those pins are being used or not. At the same time, there is a known bug in the firmwares that don't restore the pin settings correctly after suspend, i.e. by an unknown reason the Rx value becomes inverted. Hence, let's save and restore the pins that are configured as GPIOs in the input mode with GPIROUTIOXAPIC bit set. Cc: stable@vger.kernel.org Reported-and-tested-by: Dale Smith <dalepsmith@gmail.com> Reported-and-tested-by: John Harris <jmharris@gmail.com> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=214749 Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com> Link: https://lore.kernel.org/r/20221124222926.72326-1-andriy.shevchenko@linux.intel.com Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'samples/Kconfig')
0 files changed, 0 insertions, 0 deletions