Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
33 lines
970 B
ReStructuredText
33 lines
970 B
ReStructuredText
===========================
|
|
Samsung GPIO implementation
|
|
===========================
|
|
|
|
Introduction
|
|
------------
|
|
|
|
This outlines the Samsung GPIO implementation and the architecture
|
|
specific calls provided alongside the drivers/gpio core.
|
|
|
|
|
|
GPIOLIB integration
|
|
-------------------
|
|
|
|
The gpio implementation uses gpiolib as much as possible, only providing
|
|
specific calls for the items that require Samsung specific handling, such
|
|
as pin special-function or pull resistor control.
|
|
|
|
GPIO numbering is synchronised between the Samsung and gpiolib system.
|
|
|
|
|
|
PIN configuration
|
|
-----------------
|
|
|
|
Pin configuration is specific to the Samsung architecture, with each SoC
|
|
registering the necessary information for the core gpio configuration
|
|
implementation to configure pins as necessary.
|
|
|
|
The s3c_gpio_cfgpin() and s3c_gpio_setpull() provide the means for a
|
|
driver or machine to change gpio configuration.
|
|
|
|
See arch/arm/mach-s3c/gpio-cfg.h for more information on these functions.
|