Gitiles
Code Review Sign In
gerrit.devboardsforandroid.linaro.org / platform / external / u-boot / 161b1fe745394f34c4aa506edc964089785919f6 / . / drivers / pinctrl / Kconfig
blob: 5dd2dddb44a87479d17cfb379d6c00354f2e67d5 [file] [log] [blame]
Masahiro Yamadad90a5a32015-08-27 12:44:29 +0900[diff] [blame]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
Simon Glass458a0702015-08-30 16:55:12 -0600[diff] [blame]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.
Masahiro Yamadad90a5a32015-08-27 12:44:29 +0900[diff] [blame]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 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
69config 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
77config 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
85config 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.
Simon Glass458a0702015-08-30 16:55:12 -0600[diff] [blame]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.
Masahiro Yamadad90a5a32015-08-27 12:44:29 +0900[diff] [blame]98
99config 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
106if PINCTRL || SPL_PINCTRL
107
Simon Glassbb4e4a52015-08-30 16:55:35 -0600[diff] [blame]108config ROCKCHIP_PINCTRL
109 bool "Rockchip pin control driver"
110 depends on DM
111 help
112 Support pin multiplexing control on Rockchip SoCs. The driver is
113 controlled by a device tree node which contains both the GPIO
114 definitions and pin control functions for each available multiplex
115 function.
116
huang lin49ecaa92015-11-17 14:20:20 +0800[diff] [blame]117config ROCKCHIP_3036_PINCTRL
118 bool "Rockchip rk3036 pin control driver"
119 depends on DM
120 help
121 Support pin multiplexing control on Rockchip rk3036 SoCs. The driver is
122 controlled by a device tree node which contains both the GPIO
123 definitions and pin control functions for each available multiplex
124 function.
125
Masahiro Yamada9c6a3c62015-08-27 12:44:30 +0900[diff] [blame]126config PINCTRL_SANDBOX
127 bool "Sandbox pinctrl driver"
128 depends on SANDBOX
129 help
130 This enables pinctrl driver for sandbox. Currently, this driver
131 actually does nothing but print debug messages when pinctrl
132 operations are invoked.
133
Purna Chandra Mandal5f266c62016-01-28 15:30:12 +0530[diff] [blame]134config PIC32_PINCTRL
135 bool "Microchip PIC32 pin-control and pin-mux driver"
136 depends on DM && MACH_PIC32
137 default y
138 help
139 Supports individual pin selection and configuration for each remappable
140 peripheral available on Microchip PIC32 SoCs. This driver is controlled
141 by a device tree node which contains both GPIO defintion and pin control
142 functions.
143
Masahiro Yamadad90a5a32015-08-27 12:44:29 +0900[diff] [blame]144endif
145
Masahiro Yamada5dc626f2015-09-11 20:17:32 +0900[diff] [blame]146source "drivers/pinctrl/uniphier/Kconfig"
147
Masahiro Yamadad90a5a32015-08-27 12:44:29 +0900[diff] [blame]148endmenu