diff options
| author | Linus Walleij <linusw@kernel.org> | 2026-08-20 19:10:05 +0200 |
|---|---|---|
| committer | Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> | 2026-08-26 16:54:19 +0200 |
| commit | a38ad4bbd1f2862a7db1cb0a4ec27af166882e95 (patch) | |
| tree | 2caa4112a581a786ac5bb8f435f3906311f4a31f /scripts/Makefile.thinlto | |
| parent | df6501bf6fc4b16c9f502a7ab8e785ec91f3f7e3 (diff) | |
| download | linux-next-a38ad4bbd1f2862a7db1cb0a4ec27af166882e95.tar.gz linux-next-a38ad4bbd1f2862a7db1cb0a4ec27af166882e95.zip | |
gpio: generic: Avoid pinctrl calls when ranges are missing
Most calls to the pinctrl core is done through the generic helper
that go into gpiolib, where the library checks if there is a range
associated with the chip and just bails out silently if ther isn't.
gpio_mmio_dir_return() misses this check before calling
pinctrl_gpio_direction_output/input().
Fix this up with an explicit range check.
Reported-by: sashiko-bot@kernel.org
Closes: https://lore.kernel.org/linux-devicetree/20260820073920.909F71F000E9@smtp.kernel.org/
Signed-off-by: Linus Walleij <linusw@kernel.org>
Link: https://patch.msgid.link/20260820-fix-gpio-mmio-pinctrl-v1-1-62c2d7dd4903@kernel.org
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions