[people/ms/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 AR933X_PINCTRL
	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 QCA953X_PINCTRL
	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 ROCKCHIP_RK3036_PINCTRL
	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 ROCKCHIP_RK3288_PINCTRL
	bool "Rockchip 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_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 ROCKCHIP_RK3399_PINCTRL
	bool "Rockchip 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_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 PIC32_PINCTRL
	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.

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
a79d0643 WW	108	config AR933X_PINCTRL
	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
c102453a WW	117	config QCA953X_PINCTRL
	118	bool "QCA/Athores qca953x pin control driver"
	119	depends on DM && SOC_QCA953X
	120	help
	121	Support pin multiplexing control on QCA/Athores qca953x SoCs.
	122	The driver is controlled by a device tree node which contains
	123	both the GPIO definitions and pin control functions for each
	124	available multiplex function.
	125
041cdb5f HS	126	config ROCKCHIP_RK3036_PINCTRL
041cdb5f HS	127	bool "Rockchip rk3036 pin control driver"
bb4e4a5d SG	128	depends on DM
bb4e4a5d SG	129	help
041cdb5f HS	130	Support pin multiplexing control on Rockchip rk3036 SoCs. The driver is
041cdb5f HS	131	controlled by a device tree node which contains both the GPIO
bb4e4a5d SG	132	definitions and pin control functions for each available multiplex
	133	function.
	134
041cdb5f HS	135	config ROCKCHIP_RK3288_PINCTRL
041cdb5f HS	136	bool "Rockchip pin control driver"
49ecaa92	137	depends on DM
49ecaa92	138	help
041cdb5f HS	139	Support pin multiplexing control on Rockchip rk3288 SoCs. The driver
041cdb5f HS	140	is controlled by a device tree node which contains both the GPIO
49ecaa92	141	definitions and pin control functions for each available multiplex
	142	function.
	143
ac72e174 WY	144	config PINCTRL_AT91PIO4
	145	bool "AT91 PIO4 pinctrl driver"
	146	depends on DM
	147	help
	148	This option is to enable the AT91 pinctrl driver for AT91 PIO4
	149	controller which is available on SAMA5D2 SoC.
	150
a2c08df3 KY	151	config ROCKCHIP_RK3399_PINCTRL
	152	bool "Rockchip pin control driver"
	153	depends on DM
	154	help
	155	Support pin multiplexing control on Rockchip rk3399 SoCs. The driver
	156	is controlled by a device tree node which contains both the GPIO
	157	definitions and pin control functions for each available multiplex
	158	function.
	159
9c6a3c67 MY	160	config PINCTRL_SANDBOX
	161	bool "Sandbox pinctrl driver"
	162	depends on SANDBOX
	163	help
	164	This enables pinctrl driver for sandbox. Currently, this driver
	165	actually does nothing but print debug messages when pinctrl
	166	operations are invoked.
	167
5f266c60 PCM	168	config PIC32_PINCTRL
	169	bool "Microchip PIC32 pin-control and pin-mux driver"
	170	depends on DM && MACH_PIC32
	171	default y
	172	help
	173	Supports individual pin selection and configuration for each remappable
	174	peripheral available on Microchip PIC32 SoCs. This driver is controlled
	175	by a device tree node which contains both GPIO defintion and pin control
	176	functions.
	177
d90a5a30 MY	178	endif
d90a5a30 MY	179
677b5358	180	source "drivers/pinctrl/meson/Kconfig"
745df68d	181	source "drivers/pinctrl/nxp/Kconfig"
5dc626f8	182	source "drivers/pinctrl/uniphier/Kconfig"
16ca80ad	183	source "drivers/pinctrl/exynos/Kconfig"
656e6cc8	184	source "drivers/pinctrl/mvebu/Kconfig"
5dc626f8	185
d90a5a30	186	endmenu