xref: /rk3399_rockchip-uboot/drivers/pinctrl/Kconfig (revision a3dda7f4bf6bbece2100b16d2b632d6357ff044e)
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_PIC32
157	bool "Microchip PIC32 pin-control and pin-mux driver"
158	depends on DM && MACH_PIC32
159	default y
160	help
161	  Supports individual pin selection and configuration for each
162	  remappable peripheral available on Microchip PIC32
163	  SoCs. This driver is controlled by a device tree node which
164	  contains both GPIO defintion and pin control functions.
165
166config PINCTRL_QCA953X
167	bool "QCA/Athores qca953x pin control driver"
168	depends on DM && SOC_QCA953X
169	help
170	  Support pin multiplexing control on QCA/Athores qca953x SoCs.
171
172	  The driver is controlled by a device tree node which contains both
173	  the GPIO definitions and pin control functions for each available
174	  multiplex function.
175
176config PINCTRL_ROCKCHIP
177	bool "Rockchip pin control driver"
178	depends on PINCTRL_FULL && ARCH_ROCKCHIP
179	default y
180	help
181	  Support pin multiplexing control on Rockchip SoCs.
182
183	  The driver is controlled by a device tree node which contains both
184	  the GPIO definitions and pin control functions for each available
185	  multiplex function.
186
187config SPL_PINCTRL_ROCKCHIP
188	bool "Support Rockchip pin controllers in SPL"
189	depends on SPL_PINCTRL_FULL && ARCH_ROCKCHIP
190	default y
191	help
192	  This option is an SPL-variant of the PINCTRL_ROCKCHIP option.
193	  See the help of PINCTRL_ROCKCHIP for details.
194
195config PINCTRL_SANDBOX
196	bool "Sandbox pinctrl driver"
197	depends on SANDBOX
198	help
199	  This enables pinctrl driver for sandbox.
200
201	  Currently, this driver actually does nothing but print debug
202	  messages when pinctrl operations are invoked.
203
204config PINCTRL_SINGLE
205	bool "Single register pin-control and pin-multiplex driver"
206	depends on DM
207	help
208	  This enables pinctrl driver for systems using a single register for
209	  pin configuration and multiplexing. TI's AM335X SoCs are examples of
210	  such systems.
211
212	  Depending on the platform make sure to also enable OF_TRANSLATE and
213	  eventually SPL_OF_TRANSLATE to get correct address translations.
214
215config PINCTRL_STI
216	bool "STMicroelectronics STi pin-control and pin-mux driver"
217	depends on DM && ARCH_STI
218	default y
219	help
220	  Support pin multiplexing control on STMicrolectronics STi SoCs.
221
222	  The driver is controlled by a device tree node which contains both
223	  the GPIO definitions and pin control functions for each available
224	  multiplex function.
225
226config PINCTRL_STM32
227	bool "ST STM32 pin control driver"
228	depends on DM
229	help
230	  Supports pin multiplexing control on stm32 SoCs.
231
232	  The driver is controlled by a device tree node which contains both
233	  the GPIO definitions and pin control functions for each available
234	  multiplex function.
235
236config ASPEED_AST2500_PINCTRL
237  bool "Aspeed AST2500 pin control driver"
238  depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
239  default y
240  help
241    Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses
242	Generic Pinctrl framework and is compatible with the Linux driver,
243	i.e. it uses the same device tree configuration.
244
245endif
246
247source "drivers/pinctrl/meson/Kconfig"
248source "drivers/pinctrl/nxp/Kconfig"
249source "drivers/pinctrl/uniphier/Kconfig"
250source "drivers/pinctrl/exynos/Kconfig"
251source "drivers/pinctrl/mvebu/Kconfig"
252
253endmenu
254