diff options
| author | Léo DUBOIN <lduboin@freebox.fr> | 2024-04-25 15:58:02 +0200 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2024-06-17 09:22:24 +0200 |
| commit | 9dfbcf2fc566c0be2de1c7685f29effd25696b75 (patch) | |
| tree | 5843db0c8ba231f900fc50006db28312f699ebf4 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | db5032981ab37eb181810eea6037008c42d21ab3 (diff) | |
pinctrl: core: reset gpio_device in loop in pinctrl_pins_show()
We were not resetting the pointer to the associated gpio_device once
we are done displaying a pin's information.
This meant that once we reached the end of a gpio-range, if there
were pins right after it that did not belong to any known range,
they would be associated with the previous range's gpio device.
This resulted in those pins appearing as <4294966783:old_gdev> instead
of the expected <0:?> (due to gpio_num being -1).
Signed-off-by: Léo DUBOIN <lduboin@freebox.fr>
Link: https://lore.kernel.org/r/c40d0634abefa19e689ffd450e0f48a8d63c4fc4.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