dt-bindings: pinctrl: Group tuples in pin control properties
To improve human readability and enable automatic validation, the tuples in "pinctrl-*" properties should be grouped using angle brackets. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Acked-by: Krzysztof Kozlowski <krzk@kernel.org> Reviewed-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20210204125718.1646082-1-geert+renesas@glider.be Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
parent
5637f556a2
commit
74f2dd4479
@ -39,7 +39,7 @@ For example:
|
||||
<0x660009b0 0x40>;
|
||||
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&nand_sel &uart3_rx &sdio0_d4>;
|
||||
pinctrl-0 = <&nand_sel>, <&uart3_rx>, <&sdio0_d4>;
|
||||
|
||||
/* Select nand function */
|
||||
nand_sel: nand_sel {
|
||||
|
@ -30,7 +30,7 @@ For example:
|
||||
<0x1803f408 0x04>;
|
||||
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&pwm &gpio_b &nand_sel>;
|
||||
pinctrl-0 = <&pwm>, <&gpio_b>, <&nand_sel>;
|
||||
|
||||
pwm: pwm {
|
||||
function = "pwm";
|
||||
|
@ -60,7 +60,7 @@ iomuxc-lpsr controller and SDA pad from iomuxc controller as:
|
||||
|
||||
i2c1: i2c@30a20000 {
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&pinctrl_i2c1_1 &pinctrl_i2c1_2>;
|
||||
pinctrl-0 = <&pinctrl_i2c1_1>, <&pinctrl_i2c1_2>;
|
||||
};
|
||||
|
||||
iomuxc-lpsr@302c0000 {
|
||||
|
@ -77,13 +77,13 @@ For example:
|
||||
device {
|
||||
pinctrl-names = "active", "idle";
|
||||
pinctrl-0 = <&state_0_node_a>;
|
||||
pinctrl-1 = <&state_1_node_a &state_1_node_b>;
|
||||
pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
|
||||
};
|
||||
|
||||
/* For the same device if using state IDs */
|
||||
device {
|
||||
pinctrl-0 = <&state_0_node_a>;
|
||||
pinctrl-1 = <&state_1_node_a &state_1_node_b>;
|
||||
pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
|
||||
};
|
||||
|
||||
/*
|
||||
|
@ -134,7 +134,7 @@ gpio21: gpio@21 {
|
||||
#interrupt-cells = <0x2>;
|
||||
microchip,irq-mirror;
|
||||
pinctrl-names = "default";
|
||||
pinctrl-0 = <&i2cgpio0irq &gpio21pullups>;
|
||||
pinctrl-0 = <&i2cgpio0irq>, <&gpio21pullups>;
|
||||
|
||||
gpio21pullups: pinmux {
|
||||
pins = "gpio0", "gpio1", "gpio2", "gpio3",
|
||||
|
@ -91,7 +91,7 @@ Examples:
|
||||
pinctrl@1c20800 {
|
||||
compatible = "mediatek,mt8135-pinctrl";
|
||||
reg = <0 0x1000B000 0 0x1000>;
|
||||
mediatek,pctl-regmap = <&syscfg_pctl_a &syscfg_pctl_b>;
|
||||
mediatek,pctl-regmap = <&syscfg_pctl_a>, <&syscfg_pctl_b>;
|
||||
pins-are-numbered;
|
||||
gpio-controller;
|
||||
#gpio-cells = <2>;
|
||||
|
@ -80,7 +80,7 @@ Optional properties:
|
||||
property.
|
||||
|
||||
/* pin base, nr pins & gpio function */
|
||||
pinctrl-single,gpio-range = <&range 0 3 0 &range 3 9 1>;
|
||||
pinctrl-single,gpio-range = <&range 0 3 0>, <&range 3 9 1>;
|
||||
|
||||
- interrupt-controller : standard interrupt controller binding if using
|
||||
interrupts for wake-up events for example. In this case pinctrl-single
|
||||
@ -185,10 +185,10 @@ pmx_gpio: pinmux@d401e000 {
|
||||
pinctrl-single,function-mask = <7>;
|
||||
|
||||
/* sparse GPIO range could be supported */
|
||||
pinctrl-single,gpio-range = <&range 0 3 0 &range 3 9 1
|
||||
&range 12 1 0 &range 13 29 1
|
||||
&range 43 1 0 &range 44 49 1
|
||||
&range 94 1 1 &range 96 2 1>;
|
||||
pinctrl-single,gpio-range = <&range 0 3 0>, <&range 3 9 1>,
|
||||
<&range 12 1 0>, <&range 13 29 1>,
|
||||
<&range 43 1 0>, <&range 44 49 1>,
|
||||
<&range 94 1 1>, <&range 96 2 1>;
|
||||
|
||||
range: gpio-range {
|
||||
#pinctrl-single,gpio-range-cells = <3>;
|
||||
|
@ -336,7 +336,7 @@ Example 3: A uart client node that supports 'default' and 'flow-control' states.
|
||||
interrupts = <0 52 0>;
|
||||
pinctrl-names = "default", "flow-control;
|
||||
pinctrl-0 = <&uart0_data>;
|
||||
pinctrl-1 = <&uart0_data &uart0_fctl>;
|
||||
pinctrl-1 = <&uart0_data>, <&uart0_fctl>;
|
||||
};
|
||||
|
||||
Example 4: Set up the default pin state for uart controller.
|
||||
|
Loading…
Reference in New Issue
Block a user