summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorMartin Schiller <ms@dev.tdt.de>2024-06-07 11:04:00 +0200
committerThomas Bogendoerfer <tsbogend@alpha.franken.de>2024-06-11 16:05:12 +0200
commit277a0363120276645ae598d8d5fea7265e076ae9 (patch)
treebd6b6ec3fe0a5d0a5f17f0687b620a77081508a2 /Kconfig
parentae9daffd9028f2500c9ac1517e46d4f2b57efb80 (diff)
downloadlinux-stable-277a0363120276645ae598d8d5fea7265e076ae9.tar.gz
linux-stable-277a0363120276645ae598d8d5fea7265e076ae9.tar.bz2
linux-stable-277a0363120276645ae598d8d5fea7265e076ae9.zip
MIPS: pci: lantiq: restore reset gpio polarity
Commit 90c2d2eb7ab5 ("MIPS: pci: lantiq: switch to using gpiod API") not only switched to the gpiod API, but also inverted / changed the polarity of the GPIO. According to the PCI specification, the RST# pin is an active-low signal. However, most of the device trees that have been widely used for a long time (mainly in the openWrt project) define this GPIO as active-high and the old driver code inverted the signal internally. Apparently there are actually boards where the reset gpio must be operated inverted. For this reason, we cannot use the GPIOD_OUT_LOW/HIGH flag for initialization. Instead, we must explicitly set the gpio to value 1 in order to take into account any "GPIO_ACTIVE_LOW" flag that may have been set. In order to remain compatible with all these existing device trees, we should therefore keep the logic as it was before the commit. Fixes: 90c2d2eb7ab5 ("MIPS: pci: lantiq: switch to using gpiod API") Cc: stable@vger.kernel.org Signed-off-by: Martin Schiller <ms@dev.tdt.de> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions