1# 2# PINCTRL infrastructure and drivers 3# 4 5menu "Pin controllers" 6 7config PINCTRL 8 bool "Support pin controllers" 9 depends on DM 10 help 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. 13 14config PINCTRL_FULL 15 bool "Support full pin controllers" 16 depends on PINCTRL && OF_CONTROL 17 default y 18 help 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. 23 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. 29 30config PINCTRL_GENERIC 31 bool "Support generic pin controllers" 32 depends on PINCTRL_FULL 33 default y 34 help 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 42 operations. 43 44config PINMUX 45 bool "Support pin multiplexing controllers" 46 depends on PINCTRL_GENERIC 47 default y 48 help 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. 54 55config PINCONF 56 bool "Support pin configuration controllers" 57 depends on PINCTRL_GENERIC 58 help 59 This option enables pin configuration through the generic pinctrl 60 framework. 61 62config PINCONF_RECURSIVE 63 bool "Support recursive binding for pin configuration nodes" 64 depends on PINCTRL_FULL 65 default n if ARCH_STM32MP 66 default y 67 help 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 76 no needed. 77 78config SPL_PINCTRL 79 bool "Support pin controllers in SPL" 80 depends on SPL && SPL_DM 81 help 82 This option is an SPL-variant of the PINCTRL option. 83 See the help of PINCTRL for details. 84 85config 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 89 default y 90 help 91 This option is an SPL-variant of the PINCTRL_FULL option. 92 See the help of PINCTRL_FULL for details. 93 94config SPL_PINCTRL_GENERIC 95 bool "Support generic pin controllers in SPL" 96 depends on SPL_PINCTRL_FULL 97 default y 98 help 99 This option is an SPL-variant of the PINCTRL_GENERIC option. 100 See the help of PINCTRL_GENERIC for details. 101 102config SPL_PINMUX 103 bool "Support pin multiplexing controllers in SPL" 104 depends on SPL_PINCTRL_GENERIC 105 default y 106 help 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 114 for this to work. 115 116config SPL_PINCONF 117 bool "Support pin configuration controllers in SPL" 118 depends on SPL_PINCTRL_GENERIC 119 help 120 This option is an SPL-variant of the PINCONF option. 121 See the help of PINCONF for details. 122 123config 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 127 default y 128 help 129 This option is an SPL-variant of the PINCONF_RECURSIVE option. 130 See the help of PINCONF_RECURSIVE for details. 131 132if PINCTRL || SPL_PINCTRL 133 134config PINCTRL_AR933X 135 bool "QCA/Athores ar933x pin control driver" 136 depends on DM && SOC_AR933X 137 help 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. 142 143config PINCTRL_AT91 144 bool "AT91 pinctrl driver" 145 depends on DM 146 help 147 This option is to enable the AT91 pinctrl driver for AT91 PIO 148 controller. 149 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. 158 159config PINCTRL_AT91PIO4 160 bool "AT91 PIO4 pinctrl driver" 161 depends on DM 162 help 163 This option is to enable the AT91 pinctrl driver for AT91 PIO4 164 controller which is available on SAMA5D2 SoC. 165 166config PINCTRL_PIC32 167 bool "Microchip PIC32 pin-control and pin-mux driver" 168 depends on DM && MACH_PIC32 169 default y 170 help 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. 175 176config PINCTRL_QCA953X 177 bool "QCA/Athores qca953x pin control driver" 178 depends on DM && SOC_QCA953X 179 help 180 Support pin multiplexing control on QCA/Athores qca953x SoCs. 181 182 The driver is controlled by a device tree node which contains both 183 the GPIO definitions and pin control functions for each available 184 multiplex function. 185 186config PINCTRL_ROCKCHIP_RV1108 187 bool "Rockchip rv1108 pin control driver" 188 depends on DM 189 help 190 Support pin multiplexing control on Rockchip rv1108 SoC. 191 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. 195 196config PINCTRL_SANDBOX 197 bool "Sandbox pinctrl driver" 198 depends on SANDBOX 199 help 200 This enables pinctrl driver for sandbox. 201 202 Currently, this driver actually does nothing but print debug 203 messages when pinctrl operations are invoked. 204 205config PINCTRL_SINGLE 206 bool "Single register pin-control and pin-multiplex driver" 207 depends on DM 208 help 209 This enables pinctrl driver for systems using a single register for 210 pin configuration and multiplexing. TI's AM335X SoCs are examples of 211 such systems. 212 213 Depending on the platform make sure to also enable OF_TRANSLATE and 214 eventually SPL_OF_TRANSLATE to get correct address translations. 215 216config PINCTRL_STI 217 bool "STMicroelectronics STi pin-control and pin-mux driver" 218 depends on DM && ARCH_STI 219 default y 220 help 221 Support pin multiplexing control on STMicrolectronics STi SoCs. 222 223 The driver is controlled by a device tree node which contains both 224 the GPIO definitions and pin control functions for each available 225 multiplex function. 226 227config PINCTRL_STM32 228 bool "ST STM32 pin control driver" 229 depends on DM 230 help 231 Supports pin multiplexing control on stm32 SoCs. 232 233 The driver is controlled by a device tree node which contains both 234 the GPIO definitions and pin control functions for each available 235 multiplex function. 236 237config PINCTRL_STMFX 238 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver" 239 depends on DM && PINCTRL_FULL 240 help 241 I2C driver for STMicroelectronics Multi-Function eXpander (STMFX) 242 GPIO expander. 243 Supports pin multiplexing control on stm32 SoCs. 244 245 The driver is controlled by a device tree node which contains both 246 the GPIO definitions and pin control functions for each available 247 multiplex function. 248 249config SPL_PINCTRL_STMFX 250 bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver in SPL" 251 depends on SPL_PINCTRL_FULL 252 help 253 This option is an SPL-variant of the SPL_PINCTRL_STMFX option. 254 See the help of PINCTRL_STMFX for details. 255 256config ASPEED_AST2500_PINCTRL 257 bool "Aspeed AST2500 pin control driver" 258 depends on DM && PINCTRL_GENERIC && ASPEED_AST2500 259 default y 260 help 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. 264 265endif 266 267source "drivers/pinctrl/broadcom/Kconfig" 268source "drivers/pinctrl/exynos/Kconfig" 269source "drivers/pinctrl/mediatek/Kconfig" 270source "drivers/pinctrl/meson/Kconfig" 271source "drivers/pinctrl/mscc/Kconfig" 272source "drivers/pinctrl/mtmips/Kconfig" 273source "drivers/pinctrl/mvebu/Kconfig" 274source "drivers/pinctrl/nxp/Kconfig" 275source "drivers/pinctrl/renesas/Kconfig" 276source "drivers/pinctrl/rockchip/Kconfig" 277source "drivers/pinctrl/uniphier/Kconfig" 278 279endmenu 280