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 own multiplexing arrangement 51 where a single pin can be used for several functions. An SoC pinctrl 52 driver 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 SPL_PINCTRL 63 bool "Support pin controllers in SPL" 64 depends on SPL && SPL_DM 65 help 66 This option is an SPL-variant of the PINCTRL option. 67 See the help of PINCTRL for details. 68 69config SPL_PINCTRL_FULL 70 bool "Support full pin controllers in SPL" 71 depends on SPL_PINCTRL && SPL_OF_CONTROL 72 default n if TARGET_STM32F746_DISCO 73 default y 74 help 75 This option is an SPL-variant of the PINCTRL_FULL option. 76 See the help of PINCTRL_FULL for details. 77 78config SPL_PINCTRL_GENERIC 79 bool "Support generic pin controllers in SPL" 80 depends on SPL_PINCTRL_FULL 81 default y 82 help 83 This option is an SPL-variant of the PINCTRL_GENERIC option. 84 See the help of PINCTRL_GENERIC for details. 85 86config SPL_PINMUX 87 bool "Support pin multiplexing controllers in SPL" 88 depends on SPL_PINCTRL_GENERIC 89 default y 90 help 91 This option is an SPL-variant of the PINMUX option. 92 See the help of PINMUX for details. 93 The pinctrl subsystem can add a substantial overhead to the SPL 94 image since it typically requires quite a few tables either in the 95 driver or in the device tree. If this is acceptable and you need 96 to adjust pin multiplexing in SPL in order to boot into U-Boot, 97 enable this option. You will need to enable device tree in SPL 98 for this to work. 99 100config SPL_PINCONF 101 bool "Support pin configuration controllers in SPL" 102 depends on SPL_PINCTRL_GENERIC 103 help 104 This option is an SPL-variant of the PINCONF option. 105 See the help of PINCONF for details. 106 107if PINCTRL || SPL_PINCTRL 108 109config PINCTRL_AR933X 110 bool "QCA/Athores ar933x pin control driver" 111 depends on DM && SOC_AR933X 112 help 113 Support pin multiplexing control on QCA/Athores ar933x SoCs. 114 The driver is controlled by a device tree node which contains 115 both the GPIO definitions and pin control functions for each 116 available multiplex function. 117 118config PINCTRL_AT91 119 bool "AT91 pinctrl driver" 120 depends on DM 121 help 122 This option is to enable the AT91 pinctrl driver for AT91 PIO 123 controller. 124 125 AT91 PIO controller is a combined gpio-controller, pin-mux and 126 pin-config module. Each I/O pin may be dedicated as a general-purpose 127 I/O or be assigned to a function of an embedded peripheral. Each I/O 128 pin has a glitch filter providing rejection of glitches lower than 129 one-half of peripheral clock cycle and a debouncing filter providing 130 rejection of unwanted pulses from key or push button operations. You 131 can also control the multi-driver capability, pull-up and pull-down 132 feature on each I/O pin. 133 134config PINCTRL_AT91PIO4 135 bool "AT91 PIO4 pinctrl driver" 136 depends on DM 137 help 138 This option is to enable the AT91 pinctrl driver for AT91 PIO4 139 controller which is available on SAMA5D2 SoC. 140 141config PINCTRL_MAX96745 142 bool "Maxim MAX96745 pinctrl driver" 143 depends on DM && I2C_MUX_MAX96745 144 help 145 This option is to enable the pinctrl driver for Maxim 146 MAX96745. 147 148config PINCTRL_MAX96752F 149 bool "Maxim MAX96752F pinctrl driver" 150 depends on DM && I2C_MUX_MAX96752F 151 select PINCONF 152 help 153 This option is to enable the pinctrl driver for Maxim 154 MAX96752F. 155 156config PINCTRL_MAX96755F 157 bool "Maxim MAX96755F pinctrl driver" 158 depends on DM && I2C_MUX_MAX96755F 159 help 160 This option is to enable the pinctrl driver for Maxim 161 MAX96755F. 162 163config PINCTRL_PIC32 164 bool "Microchip PIC32 pin-control and pin-mux driver" 165 depends on DM && MACH_PIC32 166 default y 167 help 168 Supports individual pin selection and configuration for each 169 remappable peripheral available on Microchip PIC32 170 SoCs. This driver is controlled by a device tree node which 171 contains both GPIO defintion and pin control functions. 172 173config PINCTRL_QCA953X 174 bool "QCA/Athores qca953x pin control driver" 175 depends on DM && SOC_QCA953X 176 help 177 Support pin multiplexing control on QCA/Athores qca953x SoCs. 178 179 The driver is controlled by a device tree node which contains both 180 the GPIO definitions and pin control functions for each available 181 multiplex function. 182 183config PINCTRL_ROCKCHIP 184 bool "Rockchip pin control driver" 185 depends on PINCTRL_FULL && ARCH_ROCKCHIP 186 default y 187 help 188 Support pin multiplexing control on Rockchip SoCs. 189 190 The driver is controlled by a device tree node which contains both 191 the GPIO definitions and pin control functions for each available 192 multiplex function. 193 194config SPL_PINCTRL_ROCKCHIP 195 bool "Support Rockchip pin controllers in SPL" 196 depends on SPL_PINCTRL_FULL && ARCH_ROCKCHIP 197 default y 198 help 199 This option is an SPL-variant of the PINCTRL_ROCKCHIP option. 200 See the help of PINCTRL_ROCKCHIP for details. 201 202config PINCTRL_SANDBOX 203 bool "Sandbox pinctrl driver" 204 depends on SANDBOX 205 help 206 This enables pinctrl driver for sandbox. 207 208 Currently, this driver actually does nothing but print debug 209 messages when pinctrl operations are invoked. 210 211config PINCTRL_SINGLE 212 bool "Single register pin-control and pin-multiplex driver" 213 depends on DM 214 help 215 This enables pinctrl driver for systems using a single register for 216 pin configuration and multiplexing. TI's AM335X SoCs are examples of 217 such systems. 218 219 Depending on the platform make sure to also enable OF_TRANSLATE and 220 eventually SPL_OF_TRANSLATE to get correct address translations. 221 222config PINCTRL_STI 223 bool "STMicroelectronics STi pin-control and pin-mux driver" 224 depends on DM && ARCH_STI 225 default y 226 help 227 Support pin multiplexing control on STMicrolectronics STi SoCs. 228 229 The driver is controlled by a device tree node which contains both 230 the GPIO definitions and pin control functions for each available 231 multiplex function. 232 233config PINCTRL_STM32 234 bool "ST STM32 pin control driver" 235 depends on DM 236 help 237 Supports pin multiplexing control on stm32 SoCs. 238 239 The driver is controlled by a device tree node which contains both 240 the GPIO definitions and pin control functions for each available 241 multiplex function. 242 243config ASPEED_AST2500_PINCTRL 244 bool "Aspeed AST2500 pin control driver" 245 depends on DM && PINCTRL_GENERIC && ASPEED_AST2500 246 default y 247 help 248 Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses 249 Generic Pinctrl framework and is compatible with the Linux driver, 250 i.e. it uses the same device tree configuration. 251 252endif 253 254source "drivers/pinctrl/meson/Kconfig" 255source "drivers/pinctrl/nxp/Kconfig" 256source "drivers/pinctrl/uniphier/Kconfig" 257source "drivers/pinctrl/exynos/Kconfig" 258source "drivers/pinctrl/mvebu/Kconfig" 259 260endmenu 261