aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorLéo DUBOIN <lduboin@freebox.fr>2024-04-25 15:58:01 +0200
committerLinus Walleij <linus.walleij@linaro.org>2024-06-17 09:22:15 +0200
commitdb5032981ab37eb181810eea6037008c42d21ab3 (patch)
tree94c44e869235bd0ecaa8d8f9c156548049bdfe27 /tools/perf/util/scripting-engines/trace-event-python.c
parentf805e356313bbcafef48808c14eb9ce7f4ff2560 (diff)
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/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions