* pinctrl: kirkwood: gpio mode not being selected
@ 2020-07-28 4:53 Chris Packham
0 siblings, 0 replies; only message in thread
From: Chris Packham @ 2020-07-28 4:53 UTC (permalink / raw)
To: linux-arm-kernel, linux-gpio, linux-kernel
I'm in the process updating our platforms from a v4.4.x based kernel to
a v5.7 based one.
On one of our Marvell Kirkwood based boards I'm seeing a problem where a
gpio isn't being driven (the gpio happens to be a reset to a PHY chip
that our userspace switching code is attempting to talk to).
Our bootloader is inadvertently configuring MPP15 into uart0 RTS mode
(probably a copy and paste from the reference board).
Under the v4.4 kernel by the time userspace gets started the MPP15 pin
has been put into GPIO mode. With the latest v5.7 kernel the incorrect
mode is retained.
I haven't gone bisecting but I'm guessing something somewhere has
decided not to put the pin into GPIO mode (because that is the hardware
I probably need to define an explicit pinctrl node in my dts, but I
wanted to make sure that this was an intentional change in behaviour.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-28 4:53 pinctrl: kirkwood: gpio mode not being selected Chris Packham
Linux-GPIO Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-gpio/0 linux-gpio/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-gpio linux-gpio/ https://lore.kernel.org/linux-gpio \
Example config snippet for mirrors
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git