pinctrl: bcm2835: Make pin freeing behavior configurable
Until now after a bcm2835 pin was freed its pinmux was set to GPIO_IN. So in case it was configured as GPIO_OUT before the configured output level also get lost. As long as GPIO sysfs was used this wasn't actually a problem because the pins and their possible output level were kept by sysfs. Since more and more Raspberry Pi users start using libgpiod they are confused about this behavior. So make the pin freeing behavior of GPIO_OUT configurable via module parameter. In case pinctrl-bcm2835.persist_gpio_outputs is set to 1, the output level is kept. This patch based on the downstream work of Phil Elwell. Link: https://github.com/raspberrypi/linux/pull/6117 Signed-off-by:Stefan Wahren <wahrenst@gmx.net> Message-ID: <20240503062745.11298-1-wahrenst@gmx.net> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org>
-
mentioned in commit 9a40de8c
-
mentioned in commit a1cad739
-
mentioned in commit d7e7a0cd
-
mentioned in commit c82b8f1e
-
mentioned in commit 63c37977
-
mentioned in commit ac310bcb
-
mentioned in commit 604bd70c
-
mentioned in commit 8e2c9a67
-
mentioned in commit e5216bac
-
mentioned in commit f0c0e8ba
-
mentioned in commit 19b18f44
-
mentioned in commit f87840e8
-
mentioned in commit 351cfa03
-
mentioned in commit f004af96
-
mentioned in commit cff0503e
-
mentioned in commit e3e0373d
-
mentioned in commit 84df4d53
-
mentioned in commit 58a56d3c
-
mentioned in commit 11043667
-
mentioned in commit b8762e02
-
mentioned in commit 7a35949a
-
mentioned in commit 22010d9e
-
mentioned in commit 59681aef
-
mentioned in commit 2920c1ea
-
mentioned in commit 4f7d2f1e
-
mentioned in commit cc266a41
-
mentioned in commit 61a47059
-
mentioned in commit f4b0a50f