diff options
| author | Mehmet Fide <mehmet.fide@screeningeagle.com> | 2026-09-15 10:05:00 +0200 |
|---|---|---|
| committer | Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> | 2026-09-21 11:14:49 +0200 |
| commit | fc291104d01a4e42b44132925c46655d4be5ed13 (patch) | |
| tree | bc0537ddb86a650d609be1c5844849a9aa016ca5 /tools/perf/scripts/python | |
| parent | 9fbdc9ab1c304a99960cccb5300956cc73cb7020 (diff) | |
| download | linux-next-fc291104d01a4e42b44132925c46655d4be5ed13.tar.gz linux-next-fc291104d01a4e42b44132925c46655d4be5ed13.zip | |
gpiolib: add get_config() and gpiochip_generic_get_config()
A chip with a pin control backend sets a line's configuration through
set_config() and gpiochip_generic_config(), but has no way to read one
back. gpio-mmio needs that to learn the direction of a line whose
direction lives in the pin controller.
Add the optional get_config() callback, taking the packed parameter to
query and returning its bare argument the way pinctrl_gpio_get_config()
does, and gpiochip_generic_get_config() as the pin control backed
implementation, the mirror of gpiochip_generic_config(): a chip without
pin ranges, or a kernel without pinctrl, gets -ENOTSUPP.
Nothing in gpiolib calls get_config() and there is no consumer API; it
is for the chip's own use.
Suggested-by: Linus Walleij <linusw@kernel.org>
Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
Reviewed-by: Linus Walleij <linusw@kernel.org>
Link: https://patch.msgid.link/20260915080501.329424-4-mehmet.fide@gmail.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
