diff options
| author | Mark Brown <broonie@kernel.org> | 2026-10-22 12:47:37 +0100 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-10-22 12:47:37 +0100 |
| commit | eecbee709cc4cb2edb6ca5e04cec7b80097d10a3 (patch) | |
| tree | 1b7961ab59487696f3eccb7c0551f9c8e5e9bfcd /Documentation/driver-api | |
| parent | 381a433896a1c9af12dd0a8f7976e31f779cae6c (diff) | |
| parent | b57f502a681296be357e5c9dc72b53b083b26472 (diff) | |
| download | linux-next-eecbee709cc4cb2edb6ca5e04cec7b80097d10a3.tar.gz linux-next-eecbee709cc4cb2edb6ca5e04cec7b80097d10a3.zip | |
Merge branch 'gpio/for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git
# Conflicts:
# MAINTAINERS
# drivers/gpio/gpiolib-kunit.c
Diffstat (limited to 'Documentation/driver-api')
| -rw-r--r-- | Documentation/driver-api/gpio/board.rst | 2 | ||||
| -rw-r--r-- | Documentation/driver-api/gpio/driver.rst | 7 |
2 files changed, 8 insertions, 1 deletions
diff --git a/Documentation/driver-api/gpio/board.rst b/Documentation/driver-api/gpio/board.rst index 4ac1e12cf872..83b74843ecf2 100644 --- a/Documentation/driver-api/gpio/board.rst +++ b/Documentation/driver-api/gpio/board.rst @@ -55,7 +55,7 @@ looked up by the gpiod functions internally) used in the device tree. With above Internally, the GPIO subsystem prefixes the GPIO suffix ("gpios" or "gpio") with the string passed in con_id to get the resulting string -(``snprintf(... "%s-%s", con_id, gpio_suffixes[]``). +(``snprintf(... "%s-%s", con_id, gpio_suffixes[])``). ACPI ---- diff --git a/Documentation/driver-api/gpio/driver.rst b/Documentation/driver-api/gpio/driver.rst index a4f160b95089..3e53374c7e9f 100644 --- a/Documentation/driver-api/gpio/driver.rst +++ b/Documentation/driver-api/gpio/driver.rst @@ -134,6 +134,13 @@ ending up in the pin control back-end "behind" the GPIO controller, usually closer to the actual pins. This way the pin controller can manage the below listed GPIO configurations. +The optional .get_config() callback reads a configuration back: the packed +parameter to query goes in, its bare argument comes out, the way +pinctrl_gpio_get_config() answers. gpiochip_generic_get_config() is its pin +control backed counterpart. Nothing in gpiolib calls it; it is for the GPIO +driver's own use, for example to learn the direction of a line when the pin +controller owns it. + If a pin controller back-end is used, the GPIO controller or hardware description needs to provide "GPIO ranges" mapping the GPIO line offsets to pin numbers on the pin controller so they can properly cross-reference each other. |