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.
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.
92 config SPL_PINCTRL_FULL
93 bool "Support full pin controllers in SPL"
94 depends on SPL_PINCTRL && SPL_OF_CONTROL
95 default n if TARGET_STM32F746_DISCO
98 This option is an SPL-variant of the PINCTRL_FULL option.
99 See the help of PINCTRL_FULL for details.
101 config TPL_PINCTRL_FULL
102 bool "Support full pin controllers in TPL"
103 depends on TPL_PINCTRL && TPL_OF_CONTROL
105 This option is an TPL-variant of the PINCTRL_FULL option.
106 See the help of PINCTRL_FULL for details.
108 config SPL_PINCTRL_GENERIC
109 bool "Support generic pin controllers in SPL"
110 depends on SPL_PINCTRL_FULL
113 This option is an SPL-variant of the PINCTRL_GENERIC option.
114 See the help of PINCTRL_GENERIC for details.
117 bool "Support pin multiplexing controllers in SPL"
118 depends on SPL_PINCTRL_GENERIC
121 This option is an SPL-variant of the PINMUX option.
122 See the help of PINMUX for details.
123 The pinctrl subsystem can add a substantial overhead to the SPL
124 image since it typically requires quite a few tables either in the
125 driver or in the device tree. If this is acceptable and you need
126 to adjust pin multiplexing in SPL in order to boot into U-Boot,
127 enable this option. You will need to enable device tree in SPL
131 bool "Support pin configuration controllers in SPL"
132 depends on SPL_PINCTRL_GENERIC
134 This option is an SPL-variant of the PINCONF option.
135 See the help of PINCONF for details.
137 config SPL_PINCONF_RECURSIVE
138 bool "Support recursive binding for pin configuration nodes in SPL"
139 depends on SPL_PINCTRL_FULL
140 default n if ARCH_STM32MP
143 This option is an SPL-variant of the PINCONF_RECURSIVE option.
144 See the help of PINCONF_RECURSIVE for details.
146 if PINCTRL || SPL_PINCTRL
148 config PINCTRL_AR933X
149 bool "QCA/Athores ar933x pin control driver"
150 depends on DM && SOC_AR933X
152 Support pin multiplexing control on QCA/Athores ar933x SoCs.
153 The driver is controlled by a device tree node which contains
154 both the GPIO definitions and pin control functions for each
155 available multiplex function.
158 bool "AT91 pinctrl driver"
161 This option is to enable the AT91 pinctrl driver for AT91 PIO
164 AT91 PIO controller is a combined gpio-controller, pin-mux and
165 pin-config module. Each I/O pin may be dedicated as a general-purpose
166 I/O or be assigned to a function of an embedded peripheral. Each I/O
167 pin has a glitch filter providing rejection of glitches lower than
168 one-half of peripheral clock cycle and a debouncing filter providing
169 rejection of unwanted pulses from key or push button operations. You
170 can also control the multi-driver capability, pull-up and pull-down
171 feature on each I/O pin.
173 config PINCTRL_AT91PIO4
174 bool "AT91 PIO4 pinctrl driver"
177 This option is to enable the AT91 pinctrl driver for AT91 PIO4
178 controller which is available on SAMA5D2 SoC.
181 bool "Standard Intel pin-control and pin-mux driver"
183 Recent Intel chips such as Apollo Lake (APL) use a common pin control
184 and GPIO scheme. The settings for this come from an SoC-specific
185 driver which must be separately enabled. The driver supports setting
186 pins on start-up and changing the GPIO attributes.
189 bool "Microchip PIC32 pin-control and pin-mux driver"
190 depends on DM && MACH_PIC32
193 Supports individual pin selection and configuration for each
194 remappable peripheral available on Microchip PIC32
195 SoCs. This driver is controlled by a device tree node which
196 contains both GPIO definition and pin control functions.
198 config PINCTRL_QCA953X
199 bool "QCA/Athores qca953x pin control driver"
200 depends on DM && SOC_QCA953X
202 Support pin multiplexing control on QCA/Athores qca953x SoCs.
204 The driver is controlled by a device tree node which contains both
205 the GPIO definitions and pin control functions for each available
208 config PINCTRL_ROCKCHIP_RV1108
209 bool "Rockchip rv1108 pin control driver"
212 Support pin multiplexing control on Rockchip rv1108 SoC.
214 The driver is controlled by a device tree node which contains
215 both the GPIO definitions and pin control functions for each
216 available multiplex function.
218 config PINCTRL_SANDBOX
219 bool "Sandbox pinctrl driver"
222 This enables pinctrl driver for sandbox.
224 Currently, this driver actually does nothing but print debug
225 messages when pinctrl operations are invoked.
227 config PINCTRL_SINGLE
228 bool "Single register pin-control and pin-multiplex driver"
231 This enables pinctrl driver for systems using a single register for
232 pin configuration and multiplexing. TI's AM335X SoCs are examples of
235 Depending on the platform make sure to also enable OF_TRANSLATE and
236 eventually SPL_OF_TRANSLATE to get correct address translations.
239 bool "STMicroelectronics STi pin-control and pin-mux driver"
240 depends on DM && ARCH_STI
243 Support pin multiplexing control on STMicrolectronics STi 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
250 bool "ST STM32 pin control driver"
253 Supports pin multiplexing control on stm32 SoCs.
255 The driver is controlled by a device tree node which contains both
256 the GPIO definitions and pin control functions for each available
260 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver"
261 depends on DM && PINCTRL_FULL
263 I2C driver for STMicroelectronics Multi-Function eXpander (STMFX)
265 Supports pin multiplexing control on stm32 SoCs.
267 The driver is controlled by a device tree node which contains both
268 the GPIO definitions and pin control functions for each available
271 config SPL_PINCTRL_STMFX
272 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver in SPL"
273 depends on SPL_PINCTRL_FULL
275 This option is an SPL-variant of the SPL_PINCTRL_STMFX option.
276 See the help of PINCTRL_STMFX for details.
278 config ASPEED_AST2500_PINCTRL
279 bool "Aspeed AST2500 pin control driver"
280 depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
283 Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses
284 Generic Pinctrl framework and is compatible with the Linux driver,
285 i.e. it uses the same device tree configuration.
289 source "drivers/pinctrl/broadcom/Kconfig"
290 source "drivers/pinctrl/exynos/Kconfig"
291 source "drivers/pinctrl/intel/Kconfig"
292 source "drivers/pinctrl/mediatek/Kconfig"
293 source "drivers/pinctrl/meson/Kconfig"
294 source "drivers/pinctrl/mscc/Kconfig"
295 source "drivers/pinctrl/mtmips/Kconfig"
296 source "drivers/pinctrl/mvebu/Kconfig"
297 source "drivers/pinctrl/nexell/Kconfig"
298 source "drivers/pinctrl/nxp/Kconfig"
299 source "drivers/pinctrl/renesas/Kconfig"
300 source "drivers/pinctrl/rockchip/Kconfig"
301 source "drivers/pinctrl/uniphier/Kconfig"