diff options
| author | Andy Shevchenko <andriy.shevchenko@linux.intel.com> | 2022-11-25 00:29:26 +0200 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2022-11-28 21:41:31 +0100 |
| commit | 6989ea4881c8944fbf04378418bb1af63d875ef8 (patch) | |
| tree | e447273b3767f6ac11a901fd53f2bf00dcec9ba4 /drivers/pinctrl/starfive | |
| parent | 11780e37565db4dd064d3243ca68f755c13f65b4 (diff) | |
| download | linux-6989ea4881c8944fbf04378418bb1af63d875ef8.tar.bz2 | |
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 'drivers/pinctrl/starfive')
0 files changed, 0 insertions, 0 deletions