[J-u-boot.git] / drivers / pinctrl / Kconfig

#
# PINCTRL infrastructure and drivers
#

menu "Pin controllers"

config PINCTRL
	bool "Support pin controllers"
	depends on DM
	help
	  This enables the basic support for pinctrl framework.  You may want
	  to enable some more options depending on what you want to do.

config PINCTRL_FULL
	bool "Support full pin controllers"
	depends on PINCTRL && OF_CONTROL
	default y
	help
	  This provides Linux-compatible device tree interface for the pinctrl
	  subsystem.  This feature depends on device tree configuration because
	  it parses a device tree to look for the pinctrl device which the
	  peripheral device is associated with.

	  If this option is disabled (it is the only possible choice for non-DT
	  boards), the pinctrl core provides no systematic mechanism for
	  identifying peripheral devices, applying needed pinctrl settings.
	  It is totally up to the implementation of each low-level driver.
	  You can save memory footprint in return for some limitations.

config PINCTRL_GENERIC
	bool "Support generic pin controllers"
	depends on PINCTRL_FULL
	default y
	help
	  Say Y here if you want to use the pinctrl subsystem through the
	  generic DT interface.  If enabled, some functions become available
	  to parse common properties such as "pins", "groups", "functions" and
	  some pin configuration parameters.  It would be easier if you only
	  need the generic DT interface for pin muxing and pin configuration.
	  If you need to handle vendor-specific DT properties, you can disable
	  this option and implement your own set_state callback in the pinctrl
	  operations.

config PINMUX
	bool "Support pin multiplexing controllers"
	depends on PINCTRL_GENERIC
	default y
	help
	  This option enables pin multiplexing through the generic pinctrl
	  framework. Most SoCs have their own own multiplexing arrangement
	  where a single pin can be used for several functions. An SoC pinctrl
	  driver allows the required function to be selected for each pin.
	  The driver is typically controlled by the device tree.

config PINCONF
	bool "Support pin configuration controllers"
	depends on PINCTRL_GENERIC
	help
	  This option enables pin configuration through the generic pinctrl
	  framework.

config SPL_PINCTRL
	bool "Support pin controlloers in SPL"
	depends on SPL && SPL_DM
	help
	  This option is an SPL-variant of the PINCTRL option.
	  See the help of PINCTRL for details.

config SPL_PINCTRL_FULL
	bool "Support full pin controllers in SPL"
	depends on SPL_PINCTRL && SPL_OF_CONTROL
	default y
	help
	  This option is an SPL-variant of the PINCTRL_FULL option.
	  See the help of PINCTRL_FULL for details.

config SPL_PINCTRL_GENERIC
	bool "Support generic pin controllers in SPL"
	depends on SPL_PINCTRL_FULL
	default y
	help
	  This option is an SPL-variant of the PINCTRL_GENERIC option.
	  See the help of PINCTRL_GENERIC for details.

config SPL_PINMUX
	bool "Support pin multiplexing controllers in SPL"
	depends on SPL_PINCTRL_GENERIC
	default y
	help
	  This option is an SPL-variant of the PINMUX option.
	  See the help of PINMUX for details.
	  The pinctrl subsystem can add a substantial overhead to the SPL
	  image since it typically requires quite a few tables either in the
	  driver or in the device tree. If this is acceptable and you need
	  to adjust pin multiplexing in SPL in order to boot into U-Boot,
	  enable this option. You will need to enable device tree in SPL
	  for this to work.

config SPL_PINCONF
	bool "Support pin configuration controllers in SPL"
	depends on SPL_PINCTRL_GENERIC
	help
	  This option is an SPL-variant of the PINCONF option.
	  See the help of PINCONF for details.

if PINCTRL || SPL_PINCTRL

config PINCTRL_AR933X
	bool "QCA/Athores ar933x pin control driver"
	depends on DM && SOC_AR933X
	help
	  Support pin multiplexing control on QCA/Athores ar933x SoCs.
	  The driver is controlled by a device tree node which contains
	  both the GPIO definitions and pin control functions for each
	  available multiplex function.

config PINCTRL_AT91
	bool "AT91 pinctrl driver"
	depends on DM
	help
	  This option is to enable the AT91 pinctrl driver for AT91 PIO
	  controller.

	  AT91 PIO controller is a combined gpio-controller, pin-mux and
	  pin-config module. Each I/O pin may be dedicated as a general-purpose
	  I/O or be assigned to a function of an embedded peripheral. Each I/O
	  pin has a glitch filter providing rejection of glitches lower than
	  one-half of peripheral clock cycle and a debouncing filter providing
	  rejection of unwanted pulses from key or push button operations. You
	  can also control the multi-driver capability, pull-up and pull-down
	  feature on each I/O pin.

config PINCTRL_AT91PIO4
	bool "AT91 PIO4 pinctrl driver"
	depends on DM
	help
	  This option is to enable the AT91 pinctrl driver for AT91 PIO4
	  controller which is available on SAMA5D2 SoC.

config PINCTRL_PIC32
	bool "Microchip PIC32 pin-control and pin-mux driver"
	depends on DM && MACH_PIC32
	default y
	help
	  Supports individual pin selection and configuration for each
	  remappable peripheral available on Microchip PIC32
	  SoCs. This driver is controlled by a device tree node which
	  contains both GPIO defintion and pin control functions.

config PINCTRL_QCA953X
	bool "QCA/Athores qca953x pin control driver"
	depends on DM && SOC_QCA953X
	help
	  Support pin multiplexing control on QCA/Athores qca953x SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3036
	bool "Rockchip rk3036 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3036 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3188
	bool "Rockchip rk3188 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3188 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3288
	bool "Rockchip rk3288 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3288 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3328
	bool "Rockchip rk3328 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3328 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3368
	bool "Rockchip RK3368 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3368 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RK3399
	bool "Rockchip rk3399 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rk3399 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_ROCKCHIP_RV1108
	bool "Rockchip rv1108 pin control driver"
	depends on DM
	help
	  Support pin multiplexing control on Rockchip rv1108 SoC.

	  The driver is controlled by a device tree node which contains
	  both the GPIO definitions and pin control functions for each
	  available multiplex function.

config PINCTRL_SANDBOX
	bool "Sandbox pinctrl driver"
	depends on SANDBOX
	help
	  This enables pinctrl driver for sandbox.

	  Currently, this driver actually does nothing but print debug
	  messages when pinctrl operations are invoked.

config PINCTRL_SINGLE
	bool "Single register pin-control and pin-multiplex driver"
	depends on DM
	help
	  This enables pinctrl driver for systems using a single register for
	  pin configuration and multiplexing. TI's AM335X SoCs are examples of
	  such systems.

	  Depending on the platform make sure to also enable OF_TRANSLATE and
	  eventually SPL_OF_TRANSLATE to get correct address translations.

config PINCTRL_STI
	bool "STMicroelectronics STi pin-control and pin-mux driver"
	depends on DM && ARCH_STI
	default y
	help
	  Support pin multiplexing control on STMicrolectronics STi SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config PINCTRL_STM32
	bool "ST STM32 pin control driver"
	depends on DM
	help
	  Supports pin multiplexing control on stm32 SoCs.

	  The driver is controlled by a device tree node which contains both
	  the GPIO definitions and pin control functions for each available
	  multiplex function.

config ASPEED_AST2500_PINCTRL
  bool "Aspeed AST2500 pin control driver"
  depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
  default y
  help
    Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses
	Generic Pinctrl framework and is compatible with the Linux driver,
	i.e. it uses the same device tree configuration.

endif

source "drivers/pinctrl/meson/Kconfig"
source "drivers/pinctrl/nxp/Kconfig"
source "drivers/pinctrl/uniphier/Kconfig"
source "drivers/pinctrl/exynos/Kconfig"
source "drivers/pinctrl/mvebu/Kconfig"

endmenu
Commit	Line	Data
d90a5a30 MY	1	#
	2	# PINCTRL infrastructure and drivers
	3	#
	4
	5	menu "Pin controllers"
	6
	7	config 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
	14	config 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
	30	config 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
	44	config 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
458a0700 SG	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.
d90a5a30 MY	54
	55	config 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
	62	config SPL_PINCTRL
	63	bool "Support pin controlloers 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
	69	config SPL_PINCTRL_FULL
	70	bool "Support full pin controllers in SPL"
	71	depends on SPL_PINCTRL && SPL_OF_CONTROL
	72	default y
	73	help
	74	This option is an SPL-variant of the PINCTRL_FULL option.
	75	See the help of PINCTRL_FULL for details.
	76
	77	config SPL_PINCTRL_GENERIC
	78	bool "Support generic pin controllers in SPL"
	79	depends on SPL_PINCTRL_FULL
	80	default y
	81	help
	82	This option is an SPL-variant of the PINCTRL_GENERIC option.
	83	See the help of PINCTRL_GENERIC for details.
	84
	85	config SPL_PINMUX
	86	bool "Support pin multiplexing controllers in SPL"
	87	depends on SPL_PINCTRL_GENERIC
	88	default y
	89	help
	90	This option is an SPL-variant of the PINMUX option.
	91	See the help of PINMUX for details.
458a0700 SG	92	The pinctrl subsystem can add a substantial overhead to the SPL
	93	image since it typically requires quite a few tables either in the
	94	driver or in the device tree. If this is acceptable and you need
	95	to adjust pin multiplexing in SPL in order to boot into U-Boot,
	96	enable this option. You will need to enable device tree in SPL
	97	for this to work.
d90a5a30 MY	98
	99	config SPL_PINCONF
	100	bool "Support pin configuration controllers in SPL"
	101	depends on SPL_PINCTRL_GENERIC
	102	help
	103	This option is an SPL-variant of the PINCONF option.
	104	See the help of PINCONF for details.
	105
	106	if PINCTRL \|\| SPL_PINCTRL
	107
51c7f348	108	config PINCTRL_AR933X
a79d0643 WW	109	bool "QCA/Athores ar933x pin control driver"
	110	depends on DM && SOC_AR933X
	111	help
	112	Support pin multiplexing control on QCA/Athores ar933x SoCs.
	113	The driver is controlled by a device tree node which contains
	114	both the GPIO definitions and pin control functions for each
	115	available multiplex function.
	116
51c7f348 PT	117	config PINCTRL_AT91
	118	bool "AT91 pinctrl driver"
	119	depends on DM
	120	help
	121	This option is to enable the AT91 pinctrl driver for AT91 PIO
	122	controller.
	123
	124	AT91 PIO controller is a combined gpio-controller, pin-mux and
	125	pin-config module. Each I/O pin may be dedicated as a general-purpose
	126	I/O or be assigned to a function of an embedded peripheral. Each I/O
	127	pin has a glitch filter providing rejection of glitches lower than
	128	one-half of peripheral clock cycle and a debouncing filter providing
	129	rejection of unwanted pulses from key or push button operations. You
	130	can also control the multi-driver capability, pull-up and pull-down
	131	feature on each I/O pin.
	132
	133	config PINCTRL_AT91PIO4
	134	bool "AT91 PIO4 pinctrl driver"
	135	depends on DM
	136	help
	137	This option is to enable the AT91 pinctrl driver for AT91 PIO4
	138	controller which is available on SAMA5D2 SoC.
	139
	140	config PINCTRL_PIC32
	141	bool "Microchip PIC32 pin-control and pin-mux driver"
	142	depends on DM && MACH_PIC32
	143	default y
	144	help
	145	Supports individual pin selection and configuration for each
	146	remappable peripheral available on Microchip PIC32
	147	SoCs. This driver is controlled by a device tree node which
	148	contains both GPIO defintion and pin control functions.
	149
	150	config PINCTRL_QCA953X
c102453a WW	151	bool "QCA/Athores qca953x pin control driver"
	152	depends on DM && SOC_QCA953X
	153	help
	154	Support pin multiplexing control on QCA/Athores qca953x SoCs.
c102453a	155
51c7f348 PT	156	The driver is controlled by a device tree node which contains both
	157	the GPIO definitions and pin control functions for each available
	158	multiplex function.
	159
	160	config PINCTRL_ROCKCHIP_RK3036
041cdb5f	161	bool "Rockchip rk3036 pin control driver"
bb4e4a5d SG	162	depends on DM
bb4e4a5d SG	163	help
51c7f348 PT	164	Support pin multiplexing control on Rockchip rk3036 SoCs.
	165
	166	The driver is controlled by a device tree node which contains both
	167	the GPIO definitions and pin control functions for each available
	168	multiplex function.
bb4e4a5d	169
51c7f348	170	config PINCTRL_ROCKCHIP_RK3188
f3f1af93	171	bool "Rockchip rk3188 pin control driver"
155cd37f HS	172	depends on DM
155cd37f HS	173	help
51c7f348	174	Support pin multiplexing control on Rockchip rk3188 SoCs.
bb4e4a5d	175
51c7f348 PT	176	The driver is controlled by a device tree node which contains both
	177	the GPIO definitions and pin control functions for each available
	178	multiplex function.
49ecaa92	179
51c7f348 PT	180	config PINCTRL_ROCKCHIP_RK3288
51c7f348 PT	181	bool "Rockchip rk3288 pin control driver"
9319a756 WY	182	depends on DM
9319a756 WY	183	help
51c7f348	184	Support pin multiplexing control on Rockchip rk3288 SoCs.
9319a756	185
51c7f348 PT	186	The driver is controlled by a device tree node which contains both
	187	the GPIO definitions and pin control functions for each available
	188	multiplex function.
ac72e174	189
51c7f348	190	config PINCTRL_ROCKCHIP_RK3328
f3f1af93	191	bool "Rockchip rk3328 pin control driver"
d439a46e KY	192	depends on DM
d439a46e KY	193	help
51c7f348 PT	194	Support pin multiplexing control on Rockchip rk3328 SoCs.
	195
	196	The driver is controlled by a device tree node which contains both
	197	the GPIO definitions and pin control functions for each available
	198	multiplex function.
d439a46e	199
27600a58 AY	200	config PINCTRL_ROCKCHIP_RK3368
	201	bool "Rockchip RK3368 pin control driver"
	202	depends on DM
	203	help
	204	Support pin multiplexing control on Rockchip rk3368 SoCs.
	205
	206	The driver is controlled by a device tree node which contains both
	207	the GPIO definitions and pin control functions for each available
	208	multiplex function.
	209
51c7f348	210	config PINCTRL_ROCKCHIP_RK3399
f3f1af93	211	bool "Rockchip rk3399 pin control driver"
a2c08df3 KY	212	depends on DM
a2c08df3 KY	213	help
51c7f348 PT	214	Support pin multiplexing control on Rockchip rk3399 SoCs.
	215
	216	The driver is controlled by a device tree node which contains both
	217	the GPIO definitions and pin control functions for each available
	218	multiplex function.
a2c08df3	219
09aa7c46 AY	220	config PINCTRL_ROCKCHIP_RV1108
	221	bool "Rockchip rv1108 pin control driver"
	222	depends on DM
	223	help
	224	Support pin multiplexing control on Rockchip rv1108 SoC.
	225
	226	The driver is controlled by a device tree node which contains
	227	both the GPIO definitions and pin control functions for each
	228	available multiplex function.
	229
9c6a3c67 MY	230	config PINCTRL_SANDBOX
	231	bool "Sandbox pinctrl driver"
	232	depends on SANDBOX
	233	help
51c7f348	234	This enables pinctrl driver for sandbox.
9c6a3c67	235
51c7f348 PT	236	Currently, this driver actually does nothing but print debug
	237	messages when pinctrl operations are invoked.
	238
	239	config PINCTRL_SINGLE
	240	bool "Single register pin-control and pin-multiplex driver"
	241	depends on DM
5f266c60	242	help
51c7f348 PT	243	This enables pinctrl driver for systems using a single register for
	244	pin configuration and multiplexing. TI's AM335X SoCs are examples of
	245	such systems.
	246
	247	Depending on the platform make sure to also enable OF_TRANSLATE and
	248	eventually SPL_OF_TRANSLATE to get correct address translations.
5f266c60	249
0c563102 PC	250	config PINCTRL_STI
	251	bool "STMicroelectronics STi pin-control and pin-mux driver"
	252	depends on DM && ARCH_STI
	253	default y
	254	help
	255	Support pin multiplexing control on STMicrolectronics STi SoCs.
51c7f348	256
0c563102	257	The driver is controlled by a device tree node which contains both
51c7f348 PT	258	the GPIO definitions and pin control functions for each available
51c7f348 PT	259	multiplex function.
0c563102	260
94d53084 VM	261	config PINCTRL_STM32
	262	bool "ST STM32 pin control driver"
	263	depends on DM
	264	help
51c7f348	265	Supports pin multiplexing control on stm32 SoCs.
94d53084	266
51c7f348 PT	267	The driver is controlled by a device tree node which contains both
	268	the GPIO definitions and pin control functions for each available
	269	multiplex function.
44d5c371	270
4f0e44e4	271	config ASPEED_AST2500_PINCTRL
	272	bool "Aspeed AST2500 pin control driver"
	273	depends on DM && PINCTRL_GENERIC && ASPEED_AST2500
	274	default y
	275	help
	276	Support pin multiplexing control on Aspeed ast2500 SoC. The driver uses
	277	Generic Pinctrl framework and is compatible with the Linux driver,
	278	i.e. it uses the same device tree configuration.
	279
d90a5a30 MY	280	endif
d90a5a30 MY	281
677b5358	282	source "drivers/pinctrl/meson/Kconfig"
745df68d	283	source "drivers/pinctrl/nxp/Kconfig"
5dc626f8	284	source "drivers/pinctrl/uniphier/Kconfig"
16ca80ad	285	source "drivers/pinctrl/exynos/Kconfig"
656e6cc8	286	source "drivers/pinctrl/mvebu/Kconfig"
5dc626f8	287
d90a5a30	288	endmenu