diff options
author | 2025-02-21 10:14:47 +0100 | |
---|---|---|
committer | 2025-03-05 09:46:09 +0530 | |
commit | 06daad327d043c23bc1ab4cdb519f589094b9e98 (patch) | |
tree | 1659a8e62f60d39214857df3bbaaaa307a63cdfe /tools/perf/scripts/python/export-to-postgresql.py | |
parent | arm64: dts: ti: k3-am62p: fix pinctrl settings (diff) | |
download | wireguard-linux-06daad327d043c23bc1ab4cdb519f589094b9e98.tar.xz wireguard-linux-06daad327d043c23bc1ab4cdb519f589094b9e98.zip |
arm64: dts: ti: k3-j722s: fix pinctrl settings
It appears that pinctrl-single is misused on this SoC to control both
the mux and the input and output and bias settings. This results in
non-working pinctrl configurations for GPIOs within the device tree.
This is what happens:
(1) During startup the pinctrl settings are applied according to the
device tree. I.e. the pin is configured as output and with
pull-ups enabled.
(2) During startup a device driver requests a GPIO.
(3) pinctrl-single is applying the default GPIO setting according to
the pinctrl-single,gpio-range property.
This would work as expected if the pinctrl-single is only controlling
the function mux, but it also controls the input/output buffer enable,
the pull-up and pull-down settings etc (pinctrl-single,function-mask
covers the entire pad setting instead of just the mux field).
Remove the pinctrl-single,gpio-range property, so that no settings are
applied during a gpio_request() call.
Fixes: 5e5c50964e2e ("arm64: dts: ti: k3-j722s: Add gpio-ranges properties")
Signed-off-by: Michael Walle <mwalle@kernel.org>
Link: https://lore.kernel.org/r/20250221091447.595199-2-mwalle@kernel.org
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions