Lines Matching +full:pin +full:- +full:compatible

10 Please refer to pinctrl-bindings.txt in this directory for details of the
12 phrase "pin configuration node".
14 Atmel AT91 pin configuration node is a node of a group of pins which can be
16 of the pins in that group. The 'pins' selects the function mode(also named pin
17 mode) this pin can work on and the 'config' configures various pad settings
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 		or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 		or "microchip,sam9x7-pinctrl", "microchip,sam9x60-pinctrl"
24 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
42 For each peripheral/bank we will describe in a u32 if a pin can be
43 configured in it by putting 1 to the pin bit (1 << pin)
46 From the datasheet Table 10-2.
83 Required properties for pin configuration node:
84 - atmel,pins: 4 integers array, represents a group of pins mux and config
90 PULL_UP		(1 << 0): indicate this pin needs a pull up.
91 MULTIDRIVE	(1 << 1): indicate this pin needs to be configured as multi-drive.
92 			Multi-drive is equivalent to open-drain type output.
93 DEGLITCH	(1 << 2): indicate this pin needs deglitch.
94 PULL_DOWN	(1 << 3): indicate this pin needs a pull down.
95 DIS_SCHMIT	(1 << 4): indicate this pin needs to the disable schmitt trigger.
96 DRIVE_STRENGTH (3 << 5): indicate the drive strength of the pin using the
98 				00 - No change (reset state value kept)
99 				01 - Low
100 				10 - Medium
101 				11 - High
102 OUTPUT		(1 << 7): indicate this pin need to be configured as an output.
104 SLEWRATE	(1 << 9): slew rate of the pin: 0 = disable, 1 = enable
105 DEBOUNCE	(1 << 16): indicate this pin needs debounce.
109 Some requirements for using atmel,at91rm9200-pinctrl binding:
110 1. We have pin function node defined under at91 controller node to represent
112 2. The driver can use the function node's name and pin configuration node's
113    name describe the pin function and group hierarchy.
115    as the function name and pin configuration node's name as group name to
117 3. Each pin configuration node should have a phandle, devices can set pins
118    configurations by referring to the phandle of that pin configuration node.
119 4. The gpio controller must be describe in the pinctrl simple-bus.
122 - compatible: "atmel,at91sam9x5-gpio" or "atmel,at91rm9200-gpio" or
123   "microchip,sam9x60-gpio"
124   or "microchip,sam9x7-gpio", "microchip,sam9x60-gpio", "atmel,at91rm9200-gpio"
125 - reg: physical base address and length of the controller's registers
126 - interrupts: interrupt outputs from the controller
127 - interrupt-controller: marks the device node as an interrupt controller
128 - #interrupt-cells: should be 2; refer to ../interrupt-controller/interrupts.txt
130 - gpio-controller
131 - #gpio-cells: should be 2; the first cell is the GPIO number and the second
132   cell specifies GPIO flags as defined in <dt-bindings/gpio/gpio.h>.
133 - clocks: bank clock
138 	#address-cells = <1>;
139 	#size-cells = <1>;
141 	compatible = "atmel,at91rm9200-pinctrl", "simple-bus";
145 		compatible = "atmel,at91sam9x5-gpio";
148 		#gpio-cells = <2>;
149 		gpio-controller;
150 		interrupt-controller;
151 		#interrupt-cells = <2>;
155 	atmel,mux-mask = <
164 		pinctrl_dbgu: dbgu-0 {
173 	compatible = "atmel,at91sam9260-usart";
176 	pinctrl-names = "default";
177 	pinctrl-0 = <&pinctrl_dbgu>;