Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318
  1. #
  2. # PINCTRL infrastructure and drivers
  3. #
  4. menu "Pin controllers"
  5. config PINCTRL
  6. bool "Support pin controllers"
  7. depends on DM
  8. help
  9. This enables the basic support for pinctrl framework. You may want
  10. to enable some more options depending on what you want to do.
  11. config PINCTRL_FULL
  12. bool "Support full pin controllers"
  13. depends on PINCTRL && OF_CONTROL
  14. default y
  15. help
  16. This provides Linux-compatible device tree interface for the pinctrl
  17. subsystem. This feature depends on device tree configuration because
  18. it parses a device tree to look for the pinctrl device which the
  19. peripheral device is associated with.
  20. If this option is disabled (it is the only possible choice for non-DT
  21. boards), the pinctrl core provides no systematic mechanism for
  22. identifying peripheral devices, applying needed pinctrl settings.
  23. It is totally up to the implementation of each low-level driver.
  24. You can save memory footprint in return for some limitations.
  25. config PINCTRL_GENERIC
  26. bool "Support generic pin controllers"
  27. depends on PINCTRL_FULL
  28. default y
  29. help
  30. Say Y here if you want to use the pinctrl subsystem through the
  31. generic DT interface. If enabled, some functions become available
  32. to parse common properties such as "pins", "groups", "functions" and
  33. some pin configuration parameters. It would be easier if you only
  34. need the generic DT interface for pin muxing and pin configuration.
  35. If you need to handle vendor-specific DT properties, you can disable
  36. this option and implement your own set_state callback in the pinctrl
  37. operations.
  38. config PINMUX
  39. bool "Support pin multiplexing controllers"
  40. depends on PINCTRL_GENERIC
  41. default y
  42. help
  43. This option enables pin multiplexing through the generic pinctrl
  44. framework. Most SoCs have their own multiplexing arrangement where
  45. a single pin can be used for several functions. An SoC pinctrl driver
  46. allows the required function to be selected for each pin.
  47. The driver is typically controlled by the device tree.
  48. config PINCONF
  49. bool "Support pin configuration controllers"
  50. depends on PINCTRL_GENERIC
  51. help
  52. This option enables pin configuration through the generic pinctrl
  53. framework.
  54. config PINCONF_RECURSIVE
  55. bool "Support recursive binding for pin configuration nodes"
  56. depends on PINCTRL_FULL
  57. default n if ARCH_STM32MP
  58. default y
  59. help
  60. In the Linux pinctrl binding, the pin configuration nodes need not be
  61. direct children of the pin controller device (may be grandchildren for
  62. example). It is define is each individual pin controller device.
  63. Say Y here if you want to keep this behavior with the pinconfig
  64. u-class: all sub are recursively bounded.
  65. If the option is disabled, this behavior is deactivated and only
  66. the direct children of pin controller will be assumed as pin
  67. configuration; you can save memory footprint when this feature is
  68. no needed.
  69. config SPL_PINCTRL
  70. bool "Support pin controllers in SPL"
  71. depends on SPL && SPL_DM
  72. help
  73. This option is an SPL-variant of the PINCTRL option.
  74. See the help of PINCTRL for details.
  75. config TPL_PINCTRL
  76. bool "Support pin controllers in TPL"
  77. depends on TPL && TPL_DM
  78. help
  79. This option is an TPL variant of the PINCTRL option.
  80. See the help of PINCTRL for details.
  81. config SPL_PINCTRL_FULL
  82. bool "Support full pin controllers in SPL"
  83. depends on SPL_PINCTRL && SPL_OF_CONTROL
  84. default n if TARGET_STM32F746_DISCO
  85. default y
  86. help
  87. This option is an SPL-variant of the PINCTRL_FULL option.
  88. See the help of PINCTRL_FULL for details.
  89. config TPL_PINCTRL_FULL
  90. bool "Support full pin controllers in TPL"
  91. depends on TPL_PINCTRL && TPL_OF_CONTROL
  92. help
  93. This option is an TPL-variant of the PINCTRL_FULL option.
  94. See the help of PINCTRL_FULL for details.
  95. config SPL_PINCTRL_GENERIC
  96. bool "Support generic pin controllers in SPL"
  97. depends on SPL_PINCTRL_FULL
  98. default y
  99. help
  100. This option is an SPL-variant of the PINCTRL_GENERIC option.
  101. See the help of PINCTRL_GENERIC for details.
  102. config 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. config SPL_PINCONF
  116. bool "Support pin configuration controllers in SPL"
  117. depends on SPL_PINCTRL_GENERIC
  118. help
  119. This option is an SPL-variant of the PINCONF option.
  120. See the help of PINCONF for details.
  121. config SPL_PINCONF_RECURSIVE
  122. bool "Support recursive binding for pin configuration nodes in SPL"
  123. depends on SPL_PINCTRL_FULL
  124. default n if ARCH_STM32MP
  125. default y
  126. help
  127. This option is an SPL-variant of the PINCONF_RECURSIVE option.
  128. See the help of PINCONF_RECURSIVE for details.
  129. if PINCTRL || SPL_PINCTRL
  130. config PINCTRL_AR933X
  131. bool "QCA/Athores ar933x pin control driver"
  132. depends on DM && SOC_AR933X
  133. help
  134. Support pin multiplexing control on QCA/Athores ar933x SoCs.
  135. The driver is controlled by a device tree node which contains
  136. both the GPIO definitions and pin control functions for each
  137. available multiplex function.
  138. config PINCTRL_AT91
  139. bool "AT91 pinctrl driver"
  140. depends on DM
  141. help
  142. This option is to enable the AT91 pinctrl driver for AT91 PIO
  143. controller.
  144. AT91 PIO controller is a combined gpio-controller, pin-mux and
  145. pin-config module. Each I/O pin may be dedicated as a general-purpose
  146. I/O or be assigned to a function of an embedded peripheral. Each I/O
  147. pin has a glitch filter providing rejection of glitches lower than
  148. one-half of peripheral clock cycle and a debouncing filter providing
  149. rejection of unwanted pulses from key or push button operations. You
  150. can also control the multi-driver capability, pull-up and pull-down
  151. feature on each I/O pin.
  152. config PINCTRL_AT91PIO4
  153. bool "AT91 PIO4 pinctrl driver"
  154. depends on DM
  155. help
  156. This option is to enable the AT91 pinctrl driver for AT91 PIO4
  157. controller which is available on SAMA5D2 SoC.
  158. config PINCTRL_INTEL
  159. bool "Standard Intel pin-control and pin-mux driver"
  160. help
  161. Recent Intel chips such as Apollo Lake (APL) use a common pin control
  162. and GPIO scheme. The settings for this come from an SoC-specific
  163. driver which must be separately enabled. The driver supports setting
  164. pins on start-up and changing the GPIO attributes.
  165. config PINCTRL_PIC32
  166. bool "Microchip PIC32 pin-control and pin-mux driver"
  167. depends on DM && MACH_PIC32
  168. default y
  169. help
  170. Supports individual pin selection and configuration for each
  171. remappable peripheral available on Microchip PIC32
  172. SoCs. This driver is controlled by a device tree node which
  173. contains both GPIO definition and pin control functions.
  174. config PINCTRL_QCA953X
  175. bool "QCA/Athores qca953x pin control driver"
  176. depends on DM && SOC_QCA953X
  177. help
  178. Support pin multiplexing control on QCA/Athores qca953x SoCs.
  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. config PINCTRL_QE
  183. bool "QE based pinctrl driver, like on mpc83xx"
  184. depends on DM
  185. help
  186. This option is to enable the QE pinctrl driver for QE based io
  187. controller.
  188. config PINCTRL_ROCKCHIP_RV1108
  189. bool "Rockchip rv1108 pin control driver"
  190. depends on DM
  191. help
  192. Support pin multiplexing control on Rockchip rv1108 SoC.
  193. The driver is controlled by a device tree node which contains
  194. both the GPIO definitions and pin control functions for each
  195. available multiplex function.
  196. config PINCTRL_SANDBOX
  197. bool "Sandbox pinctrl driver"
  198. depends on SANDBOX
  199. help
  200. This enables pinctrl driver for sandbox.
  201. Currently, this driver actually does nothing but print debug
  202. messages when pinctrl operations are invoked.
  203. config PINCTRL_SINGLE
  204. bool "Single register pin-control and pin-multiplex driver"
  205. depends on DM
  206. help
  207. This enables pinctrl driver for systems using a single register for
  208. pin configuration and multiplexing. TI's AM335X SoCs are examples of
  209. such systems.
  210. Depending on the platform make sure to also enable OF_TRANSLATE and
  211. eventually SPL_OF_TRANSLATE to get correct address translations.
  212. config PINCTRL_STI
  213. bool "STMicroelectronics STi pin-control and pin-mux driver"
  214. depends on DM && ARCH_STI
  215. default y
  216. help
  217. Support pin multiplexing control on STMicrolectronics STi SoCs.
  218. The driver is controlled by a device tree node which contains both
  219. the GPIO definitions and pin control functions for each available
  220. multiplex function.
  221. config PINCTRL_STM32
  222. bool "ST STM32 pin control driver"
  223. depends on DM
  224. help
  225. Supports pin multiplexing control on stm32 SoCs.
  226. The driver is controlled by a device tree node which contains both
  227. the GPIO definitions and pin control functions for each available
  228. multiplex function.
  229. config PINCTRL_STMFX
  230. bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver"
  231. depends on DM && PINCTRL_FULL
  232. help
  233. I2C driver for STMicroelectronics Multi-Function eXpander (STMFX)
  234. GPIO expander.
  235. Supports pin multiplexing control on stm32 SoCs.
  236. The driver is controlled by a device tree node which contains both
  237. the GPIO definitions and pin control functions for each available
  238. multiplex function.
  239. config SPL_PINCTRL_STMFX
  240. bool "STMicroelectronics STMFX I2C GPIO expander pinctrl driver in SPL"
  241. depends on SPL_PINCTRL_FULL
  242. help
  243. This option is an SPL-variant of the SPL_PINCTRL_STMFX option.
  244. See the help of PINCTRL_STMFX for details.
  245. config ASPEED_AST2500_PINCTRL
  246. bool "Aspeed AST2500 pin control driver"
  247. depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
  248. default y
  249. help
  250. Support pin multiplexing control on Aspeed ast2500 SoC. The driver
  251. uses Generic Pinctrl framework and is compatible with the Linux
  252. driver, i.e. it uses the same device tree configuration.
  253. config PINCTRL_K210
  254. bool "Kendryte K210 Fully-Programmable Input/Output Array driver"
  255. depends on DM && PINCTRL_GENERIC
  256. help
  257. Support pin multiplexing on the K210. The "FPIOA" can remap any
  258. supported function to any multifunctional IO pin. It can also perform
  259. basic GPIO functions, such as reading the current value of a pin.
  260. endif
  261. source "drivers/pinctrl/broadcom/Kconfig"
  262. source "drivers/pinctrl/exynos/Kconfig"
  263. source "drivers/pinctrl/intel/Kconfig"
  264. source "drivers/pinctrl/mediatek/Kconfig"
  265. source "drivers/pinctrl/meson/Kconfig"
  266. source "drivers/pinctrl/mscc/Kconfig"
  267. source "drivers/pinctrl/mtmips/Kconfig"
  268. source "drivers/pinctrl/mvebu/Kconfig"
  269. source "drivers/pinctrl/nexell/Kconfig"
  270. source "drivers/pinctrl/nxp/Kconfig"
  271. source "drivers/pinctrl/renesas/Kconfig"
  272. source "drivers/pinctrl/rockchip/Kconfig"
  273. source "drivers/pinctrl/uniphier/Kconfig"
  274. source "drivers/pinctrl/starfive/Kconfig"
  275. endmenu