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 recursively 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.
86 bool "Support pin controllers in TPL"
87 depends on TPL && TPL_DM
89 This option is an TPL variant of the PINCTRL option.
90 See the help of PINCTRL for details.
93 bool "Support pin controllers in VPL"
94 depends on VPL && VPL_DM
96 This option is an VPL variant of the PINCTRL option.
97 See the help of PINCTRL for details.
99 config SPL_PINCTRL_FULL
100 bool "Support full pin controllers in SPL"
101 depends on SPL_PINCTRL && SPL_OF_CONTROL
102 default n if TARGET_STM32F746_DISCO
105 This option is an SPL variant of the PINCTRL_FULL option.
106 See the help of PINCTRL_FULL for details.
108 config TPL_PINCTRL_FULL
109 bool "Support full pin controllers in TPL"
110 depends on TPL_PINCTRL && TPL_OF_CONTROL
112 This option is a TPL variant of the PINCTRL_FULL option.
113 See the help of PINCTRL_FULL for details.
115 config VPL_PINCTRL_FULL
116 bool "Support full pin controllers in VPL"
117 depends on VPL_PINCTRL && VPL_OF_CONTROL
119 This option is a VPL variant of the PINCTRL_FULL option.
120 See the help of PINCTRL_FULL for details.
122 config SPL_PINCTRL_GENERIC
123 bool "Support generic pin controllers in SPL"
124 depends on SPL_PINCTRL_FULL
127 This option is an SPL-variant of the PINCTRL_GENERIC option.
128 See the help of PINCTRL_GENERIC for details.
131 bool "Support pin multiplexing controllers in SPL"
132 depends on SPL_PINCTRL_GENERIC
135 This option is an SPL-variant of the PINMUX option.
136 See the help of PINMUX for details.
137 The pinctrl subsystem can add a substantial overhead to the SPL
138 image since it typically requires quite a few tables either in the
139 driver or in the device tree. If this is acceptable and you need
140 to adjust pin multiplexing in SPL in order to boot into U-Boot,
141 enable this option. You will need to enable device tree in SPL
145 bool "Support pin configuration controllers in SPL"
146 depends on SPL_PINCTRL_GENERIC
148 This option is an SPL-variant of the PINCONF option.
149 See the help of PINCONF for details.
151 config SPL_PINCONF_RECURSIVE
152 bool "Support recursive binding for pin configuration nodes in SPL"
153 depends on SPL_PINCTRL_FULL
154 default n if ARCH_STM32MP
157 This option is an SPL-variant of the PINCONF_RECURSIVE option.
158 See the help of PINCONF_RECURSIVE for details.
160 if PINCTRL || SPL_PINCTRL
163 bool "Apple pinctrl driver"
164 depends on DM && PINCTRL_GENERIC && ARCH_APPLE
167 Support pin multiplexing on Apple SoCs.
169 The driver is controlled by a device tree node which contains
170 both the GPIO definitions and pin control functions for each
171 available multiplex function.
173 config PINCTRL_AR933X
174 bool "QCA/Athores ar933x pin control driver"
175 depends on DM && SOC_AR933X
177 Support pin multiplexing control on QCA/Athores ar933x SoCs.
178 The driver is controlled by a device tree node which contains
179 both the GPIO definitions and pin control functions for each
180 available multiplex function.
183 bool "AT91 pinctrl driver"
186 This option is to enable the AT91 pinctrl driver for AT91 PIO
189 AT91 PIO controller is a combined gpio-controller, pin-mux and
190 pin-config module. Each I/O pin may be dedicated as a general-purpose
191 I/O or be assigned to a function of an embedded peripheral. Each I/O
192 pin has a glitch filter providing rejection of glitches lower than
193 one-half of peripheral clock cycle and a debouncing filter providing
194 rejection of unwanted pulses from key or push button operations. You
195 can also control the multi-driver capability, pull-up and pull-down
196 feature on each I/O pin.
198 config PINCTRL_AT91PIO4
199 bool "AT91 PIO4 pinctrl driver"
202 This option is to enable the AT91 pinctrl driver for AT91 PIO4
203 controller which is available on SAMA5D2 SoC.
206 bool "Standard Intel pin-control and pin-mux driver"
208 Recent Intel chips such as Apollo Lake (APL) use a common pin control
209 and GPIO scheme. The settings for this come from an SoC-specific
210 driver which must be separately enabled. The driver supports setting
211 pins on start-up and changing the GPIO attributes.
214 bool "Microchip PIC32 pin-control and pin-mux driver"
215 depends on DM && MACH_PIC32
218 Supports individual pin selection and configuration for each
219 remappable peripheral available on Microchip PIC32
220 SoCs. This driver is controlled by a device tree node which
221 contains both GPIO definition and pin control functions.
223 config PINCTRL_QCA953X
224 bool "QCA/Athores qca953x pin control driver"
225 depends on DM && SOC_QCA953X
227 Support pin multiplexing control on QCA/Athores qca953x SoCs.
229 The driver is controlled by a device tree node which contains both
230 the GPIO definitions and pin control functions for each available
234 bool "QE based pinctrl driver, like on mpc83xx"
237 This option is to enable the QE pinctrl driver for QE based io
240 config PINCTRL_ROCKCHIP_RV1108
241 bool "Rockchip rv1108 pin control driver"
244 Support pin multiplexing control on Rockchip rv1108 SoC.
246 The driver is controlled by a device tree node which contains
247 both the GPIO definitions and pin control functions for each
248 available multiplex function.
250 config PINCTRL_SANDBOX
251 bool "Sandbox pinctrl driver"
254 This enables pinctrl driver for sandbox.
256 Currently, this driver actually does nothing but print debug
257 messages when pinctrl operations are invoked.
259 config PINCTRL_SINGLE
260 bool "Single register pin-control and pin-multiplex driver"
263 This enables pinctrl driver for systems using a single register for
264 pin configuration and multiplexing. TI's AM335X SoCs are examples of
267 Depending on the platform make sure to also enable OF_TRANSLATE and
268 eventually SPL_OF_TRANSLATE to get correct address translations.
271 bool "STMicroelectronics STi pin-control and pin-mux driver"
272 depends on DM && ARCH_STI
275 Support pin multiplexing control on STMicroelectronics STi SoCs.
277 The driver is controlled by a device tree node which contains both
278 the GPIO definitions and pin control functions for each available
282 bool "ST STM32 pin control driver"
285 Supports pin multiplexing control on stm32 SoCs.
287 The driver is controlled by a device tree node which contains both
288 the GPIO definitions and pin control functions for each available
292 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver"
293 depends on DM && PINCTRL_FULL
295 I2C driver for STMicroelectronics Multi-Function eXpander (STMFX)
297 Supports pin multiplexing control on stm32 SoCs.
299 The driver is controlled by a device tree node which contains both
300 the GPIO definitions and pin control functions for each available
303 config SPL_PINCTRL_STMFX
304 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver in SPL"
305 depends on SPL_PINCTRL_FULL
307 This option is an SPL-variant of the SPL_PINCTRL_STMFX option.
308 See the help of PINCTRL_STMFX for details.
310 config ASPEED_AST2500_PINCTRL
311 bool "Aspeed AST2500 pin control driver"
312 depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
315 Support pin multiplexing control on Aspeed ast2500 SoC. The driver
316 uses Generic Pinctrl framework and is compatible with the Linux
317 driver, i.e. it uses the same device tree configuration.
319 config ASPEED_AST2600_PINCTRL
320 bool "Aspeed AST2600 pin control driver"
321 depends on DM && PINCTRL_GENERIC && ASPEED_AST2600
324 Support pin multiplexing control on Aspeed ast2600 SoC. The driver
325 uses Generic Pinctrl framework and is compatible with the Linux
326 driver, i.e. it uses the same device tree configuration.
329 bool "Kendryte K210 Fully-Programmable Input/Output Array driver"
330 depends on DM && PINCTRL_GENERIC
332 Support pin multiplexing on the K210. The "FPIOA" can remap any
333 supported function to any multifunctional IO pin. It can also perform
334 basic GPIO functions, such as reading the current value of a pin.
336 config PINCTRL_ZYNQMP
337 bool "Xilinx ZynqMP pin control driver"
338 depends on DM && PINCTRL_GENERIC && ARCH_ZYNQMP
341 Support pin multiplexing control on Xilinx ZynqMP. The driver uses
342 Generic Pinctrl framework and is compatible with the Linux driver,
343 i.e. it uses the same device tree configuration.
347 source "drivers/pinctrl/broadcom/Kconfig"
348 source "drivers/pinctrl/exynos/Kconfig"
349 source "drivers/pinctrl/intel/Kconfig"
350 source "drivers/pinctrl/mediatek/Kconfig"
351 source "drivers/pinctrl/meson/Kconfig"
352 source "drivers/pinctrl/mscc/Kconfig"
353 source "drivers/pinctrl/mtmips/Kconfig"
354 source "drivers/pinctrl/mvebu/Kconfig"
355 source "drivers/pinctrl/nexell/Kconfig"
356 source "drivers/pinctrl/nuvoton/Kconfig"
357 source "drivers/pinctrl/nxp/Kconfig"
358 source "drivers/pinctrl/renesas/Kconfig"
359 source "drivers/pinctrl/rockchip/Kconfig"
360 source "drivers/pinctrl/sunxi/Kconfig"
361 source "drivers/pinctrl/uniphier/Kconfig"
362 source "drivers/pinctrl/starfive/Kconfig"