2 # PINCTRL infrastructure and drivers
8 bool "Support pin controllers"
11 This enables the basic support for pinctrl framework. You may want
12 to enable some more options depending on what you want to do.
15 bool "Support full pin controllers"
16 depends on PINCTRL && OF_CONTROL
19 This provides Linux-compatible device tree interface for the pinctrl
20 subsystem. This feature depends on device tree configuration because
21 it parses a device tree to look for the pinctrl device which the
22 peripheral device is associated with.
24 If this option is disabled (it is the only possible choice for non-DT
25 boards), the pinctrl core provides no systematic mechanism for
26 identifying peripheral devices, applying needed pinctrl settings.
27 It is totally up to the implementation of each low-level driver.
28 You can save memory footprint in return for some limitations.
30 config PINCTRL_GENERIC
31 bool "Support generic pin controllers"
32 depends on PINCTRL_FULL
35 Say Y here if you want to use the pinctrl subsystem through the
36 generic DT interface. If enabled, some functions become available
37 to parse common properties such as "pins", "groups", "functions" and
38 some pin configuration parameters. It would be easier if you only
39 need the generic DT interface for pin muxing and pin configuration.
40 If you need to handle vendor-specific DT properties, you can disable
41 this option and implement your own set_state callback in the pinctrl
45 bool "Support pin multiplexing controllers"
46 depends on PINCTRL_GENERIC
49 This option enables pin multiplexing through the generic pinctrl
50 framework. Most SoCs have their own multiplexing arrangement where
51 a single pin can be used for several functions. An SoC pinctrl driver
52 allows the required function to be selected for each pin.
53 The driver is typically controlled by the device tree.
56 bool "Support pin configuration controllers"
57 depends on PINCTRL_GENERIC
59 This option enables pin configuration through the generic pinctrl
62 config PINCONF_RECURSIVE
63 bool "Support recursive binding for pin configuration nodes"
64 depends on PINCTRL_FULL
65 default n if ARCH_STM32MP
68 In the Linux pinctrl binding, the pin configuration nodes need not be
69 direct children of the pin controller device (may be grandchildren for
70 example). It is define is each individual pin controller device.
71 Say Y here if you want to keep this behavior with the pinconfig
72 u-class: all sub are recursivelly bounded.
73 If the option is disabled, this behavior is deactivated and only
74 the direct children of pin controller will be assumed as pin
75 configuration; you can save memory footprint when this feature is
79 bool "Support pin controllers in SPL"
80 depends on SPL && SPL_DM
82 This option is an SPL-variant of the PINCTRL option.
83 See the help of PINCTRL for details.
85 config SPL_PINCTRL_FULL
86 bool "Support full pin controllers in SPL"
87 depends on SPL_PINCTRL && SPL_OF_CONTROL
88 default n if TARGET_STM32F746_DISCO
91 This option is an SPL-variant of the PINCTRL_FULL option.
92 See the help of PINCTRL_FULL for details.
94 config SPL_PINCTRL_GENERIC
95 bool "Support generic pin controllers in SPL"
96 depends on SPL_PINCTRL_FULL
99 This option is an SPL-variant of the PINCTRL_GENERIC option.
100 See the help of PINCTRL_GENERIC for details.
103 bool "Support pin multiplexing controllers in SPL"
104 depends on SPL_PINCTRL_GENERIC
107 This option is an SPL-variant of the PINMUX option.
108 See the help of PINMUX for details.
109 The pinctrl subsystem can add a substantial overhead to the SPL
110 image since it typically requires quite a few tables either in the
111 driver or in the device tree. If this is acceptable and you need
112 to adjust pin multiplexing in SPL in order to boot into U-Boot,
113 enable this option. You will need to enable device tree in SPL
117 bool "Support pin configuration controllers in SPL"
118 depends on SPL_PINCTRL_GENERIC
120 This option is an SPL-variant of the PINCONF option.
121 See the help of PINCONF for details.
123 config SPL_PINCONF_RECURSIVE
124 bool "Support recursive binding for pin configuration nodes in SPL"
125 depends on SPL_PINCTRL_FULL
126 default n if ARCH_STM32MP
129 This option is an SPL-variant of the PINCONF_RECURSIVE option.
130 See the help of PINCONF_RECURSIVE for details.
132 if PINCTRL || SPL_PINCTRL
134 config PINCTRL_AR933X
135 bool "QCA/Athores ar933x pin control driver"
136 depends on DM && SOC_AR933X
138 Support pin multiplexing control on QCA/Athores ar933x SoCs.
139 The driver is controlled by a device tree node which contains
140 both the GPIO definitions and pin control functions for each
141 available multiplex function.
144 bool "AT91 pinctrl driver"
147 This option is to enable the AT91 pinctrl driver for AT91 PIO
150 AT91 PIO controller is a combined gpio-controller, pin-mux and
151 pin-config module. Each I/O pin may be dedicated as a general-purpose
152 I/O or be assigned to a function of an embedded peripheral. Each I/O
153 pin has a glitch filter providing rejection of glitches lower than
154 one-half of peripheral clock cycle and a debouncing filter providing
155 rejection of unwanted pulses from key or push button operations. You
156 can also control the multi-driver capability, pull-up and pull-down
157 feature on each I/O pin.
159 config PINCTRL_AT91PIO4
160 bool "AT91 PIO4 pinctrl driver"
163 This option is to enable the AT91 pinctrl driver for AT91 PIO4
164 controller which is available on SAMA5D2 SoC.
167 bool "Microchip PIC32 pin-control and pin-mux driver"
168 depends on DM && MACH_PIC32
171 Supports individual pin selection and configuration for each
172 remappable peripheral available on Microchip PIC32
173 SoCs. This driver is controlled by a device tree node which
174 contains both GPIO definition and pin control functions.
176 config PINCTRL_QCA953X
177 bool "QCA/Athores qca953x pin control driver"
178 depends on DM && SOC_QCA953X
180 Support pin multiplexing control on QCA/Athores qca953x SoCs.
182 The driver is controlled by a device tree node which contains both
183 the GPIO definitions and pin control functions for each available
186 config PINCTRL_ROCKCHIP_RV1108
187 bool "Rockchip rv1108 pin control driver"
190 Support pin multiplexing control on Rockchip rv1108 SoC.
192 The driver is controlled by a device tree node which contains
193 both the GPIO definitions and pin control functions for each
194 available multiplex function.
196 config PINCTRL_SANDBOX
197 bool "Sandbox pinctrl driver"
200 This enables pinctrl driver for sandbox.
202 Currently, this driver actually does nothing but print debug
203 messages when pinctrl operations are invoked.
205 config PINCTRL_SINGLE
206 bool "Single register pin-control and pin-multiplex driver"
209 This enables pinctrl driver for systems using a single register for
210 pin configuration and multiplexing. TI's AM335X SoCs are examples of
213 Depending on the platform make sure to also enable OF_TRANSLATE and
214 eventually SPL_OF_TRANSLATE to get correct address translations.
217 bool "STMicroelectronics STi pin-control and pin-mux driver"
218 depends on DM && ARCH_STI
221 Support pin multiplexing control on STMicrolectronics STi SoCs.
223 The driver is controlled by a device tree node which contains both
224 the GPIO definitions and pin control functions for each available
228 bool "ST STM32 pin control driver"
231 Supports pin multiplexing control on stm32 SoCs.
233 The driver is controlled by a device tree node which contains both
234 the GPIO definitions and pin control functions for each available
238 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver"
239 depends on DM && PINCTRL_FULL
241 I2C driver for STMicroelectronics Multi-Function eXpander (STMFX)
243 Supports pin multiplexing control on stm32 SoCs.
245 The driver is controlled by a device tree node which contains both
246 the GPIO definitions and pin control functions for each available
249 config SPL_PINCTRL_STMFX
250 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver in SPL"
251 depends on SPL_PINCTRL_FULL
253 This option is an SPL-variant of the SPL_PINCTRL_STMFX option.
254 See the help of PINCTRL_STMFX for details.
256 config ASPEED_AST2500_PINCTRL
257 bool "Aspeed AST2500 pin control driver"
258 depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
261 Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses
262 Generic Pinctrl framework and is compatible with the Linux driver,
263 i.e. it uses the same device tree configuration.
267 source "drivers/pinctrl/broadcom/Kconfig"
268 source "drivers/pinctrl/exynos/Kconfig"
269 source "drivers/pinctrl/mediatek/Kconfig"
270 source "drivers/pinctrl/meson/Kconfig"
271 source "drivers/pinctrl/mscc/Kconfig"
272 source "drivers/pinctrl/mtmips/Kconfig"
273 source "drivers/pinctrl/mvebu/Kconfig"
274 source "drivers/pinctrl/nxp/Kconfig"
275 source "drivers/pinctrl/renesas/Kconfig"
276 source "drivers/pinctrl/rockchip/Kconfig"
277 source "drivers/pinctrl/uniphier/Kconfig"