diff options
author | 2024-04-25 15:58:01 +0200 | |
---|---|---|
committer | 2024-06-17 09:22:15 +0200 | |
commit | db5032981ab37eb181810eea6037008c42d21ab3 (patch) | |
tree | 94c44e869235bd0ecaa8d8f9c156548049bdfe27 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | pinctrl: nuvoton: Add ma35d1 pinctrl and GPIO driver (diff) | |
download | wireguard-linux-db5032981ab37eb181810eea6037008c42d21ab3.tar.xz wireguard-linux-db5032981ab37eb181810eea6037008c42d21ab3.zip |
pinctrl: core: take into account the pins array in pinctrl_pins_show()
We previously only looked at the 'pin_base' of the pinctrl_gpio_ranges
struct for determining if a pin matched a GPIO number.
This value is present only if the 'pins' array is not NULL,
and is 0 otherwise. This means that GPIO ranges declared using
gpiochip_add_pingroup_range(), thus making use of pins, were always matched
by the pins in the range [0-npins] even if they contained pins in a
completely separate range.
Signed-off-by: Léo DUBOIN <lduboin@freebox.fr>
Link: https://lore.kernel.org/r/6df39bd47942156be5713f8f4e317d2ad3e0ddeb.1714049455.git.lduboin@freebox.fr
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions