* [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 11:37 [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Krzysztof Kozlowski
@ 2022-06-09 11:40 ` Krzysztof Kozlowski
2022-06-09 13:57 ` Maya Matuszczyk
2022-06-09 11:40 ` [PATCH v2 33/48] ARM: " Krzysztof Kozlowski
` (3 subsequent siblings)
4 siblings, 1 reply; 11+ messages in thread
From: Krzysztof Kozlowski @ 2022-06-09 11:40 UTC (permalink / raw)
To: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, Heiko Stuebner, devicetree, linux-arm-kernel,
linux-rockchip, linux-kernel
Cc: Krzysztof Kozlowski
The node names should be generic and DT schema expects certain pattern
(e.g. with key/button/switch).
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
.../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
.../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
.../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
.../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
.../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
.../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
.../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
.../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
.../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
.../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
.../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
.../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
.../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
21 files changed, 38 insertions(+), 38 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
index 9b4f855ea5d4..4b5413b12bfa 100644
--- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
@@ -75,7 +75,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ power-key {
gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
index ea0695b51ecd..72328dd993ee 100644
--- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
@@ -71,82 +71,82 @@ gpio-keys {
* |------------------------------------------------|
*/
- sw1 {
+ switch-1 {
gpios = <&gpio1 RK_PB4 GPIO_ACTIVE_LOW>;
label = "DPAD-UP";
linux,code = <BTN_DPAD_UP>;
};
- sw2 {
+ switch-2 {
gpios = <&gpio1 RK_PB5 GPIO_ACTIVE_LOW>;
label = "DPAD-DOWN";
linux,code = <BTN_DPAD_DOWN>;
};
- sw3 {
+ switch-3 {
gpios = <&gpio1 RK_PB6 GPIO_ACTIVE_LOW>;
label = "DPAD-LEFT";
linux,code = <BTN_DPAD_LEFT>;
};
- sw4 {
+ switch-4 {
gpios = <&gpio1 RK_PB7 GPIO_ACTIVE_LOW>;
label = "DPAD-RIGHT";
linux,code = <BTN_DPAD_RIGHT>;
};
- sw5 {
+ switch-5 {
gpios = <&gpio1 RK_PA2 GPIO_ACTIVE_LOW>;
label = "BTN-A";
linux,code = <BTN_EAST>;
};
- sw6 {
+ switch-6 {
gpios = <&gpio1 RK_PA5 GPIO_ACTIVE_LOW>;
label = "BTN-B";
linux,code = <BTN_SOUTH>;
};
- sw7 {
+ switch-7 {
gpios = <&gpio1 RK_PA6 GPIO_ACTIVE_LOW>;
label = "BTN-Y";
linux,code = <BTN_WEST>;
};
- sw8 {
+ switch-8 {
gpios = <&gpio1 RK_PA7 GPIO_ACTIVE_LOW>;
label = "BTN-X";
linux,code = <BTN_NORTH>;
};
- sw9 {
+ switch-9 {
gpios = <&gpio2 RK_PA0 GPIO_ACTIVE_LOW>;
label = "F1";
linux,code = <BTN_TRIGGER_HAPPY1>;
};
- sw10 {
+ switch-10 {
gpios = <&gpio2 RK_PA1 GPIO_ACTIVE_LOW>;
label = "F2";
linux,code = <BTN_TRIGGER_HAPPY2>;
};
- sw11 {
+ switch-11 {
gpios = <&gpio2 RK_PA2 GPIO_ACTIVE_LOW>;
label = "F3";
linux,code = <BTN_TRIGGER_HAPPY3>;
};
- sw12 {
+ switch-12 {
gpios = <&gpio2 RK_PA3 GPIO_ACTIVE_LOW>;
label = "F4";
linux,code = <BTN_TRIGGER_HAPPY4>;
};
- sw13 {
+ switch-13 {
gpios = <&gpio2 RK_PA4 GPIO_ACTIVE_LOW>;
label = "F5";
linux,code = <BTN_TRIGGER_HAPPY5>;
};
- sw14 {
+ switch-14 {
gpios = <&gpio2 RK_PA5 GPIO_ACTIVE_LOW>;
label = "F6";
linux,code = <BTN_TRIGGER_HAPPY6>;
};
- sw15 {
+ switch-15 {
gpios = <&gpio2 RK_PA6 GPIO_ACTIVE_LOW>;
label = "TOP-LEFT";
linux,code = <BTN_TL>;
};
- sw16 {
+ switch-16 {
gpios = <&gpio2 RK_PA7 GPIO_ACTIVE_LOW>;
label = "TOP-RIGHT";
linux,code = <BTN_TR>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts b/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
index 3857d487ab84..1445b879ac7a 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
@@ -34,7 +34,7 @@ keys {
pinctrl-0 = <&reset_button_pin>;
pinctrl-names = "default";
- reset {
+ key-reset {
label = "reset";
gpios = <&gpio0 RK_PA0 GPIO_ACTIVE_LOW>;
linux,code = <KEY_RESTART>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi b/arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi
index 15d1fc541c38..083452c67711 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi
@@ -76,7 +76,7 @@ keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ key-power {
wakeup-source;
gpios = <&gpio0 RK_PA2 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts b/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
index 62aa97a0b8c9..be06e6e64d18 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3368-geekbox.dts
@@ -43,7 +43,7 @@ keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA2 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
linux,code = <KEY_POWER>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts b/arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts
index 3ebe15e03cf4..f4c60623c905 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts
@@ -44,7 +44,7 @@ keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ key-power {
wakeup-source;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_HIGH>;
label = "GPIO Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts b/arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts
index 5ccaa5f7a370..29df84b81552 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3368-px5-evb.dts
@@ -30,7 +30,7 @@ keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA2 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
linux,code = <KEY_POWER>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3368-r88.dts b/arch/arm64/boot/dts/rockchip/rk3368-r88.dts
index 959d3cc801f2..38d757c00548 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-r88.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3368-r88.dts
@@ -37,7 +37,7 @@ keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key>;
- power {
+ key-power {
wakeup-source;
gpios = <&gpio0 RK_PA2 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
index b340c9e246c4..c5db64f3e124 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
@@ -87,7 +87,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi
index 50d459ee4831..cd074641884b 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi
@@ -206,7 +206,7 @@ gpio_keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&bt_host_wake_l>;
- wake_on_bt: wake-on-bt {
+ wake_on_bt: key-wake-on-bt {
label = "Wake-on-Bluetooth";
gpios = <&gpio0 3 GPIO_ACTIVE_LOW>;
linux,code = <KEY_WAKEUP>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts b/arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts
index 6863689df06f..2cc9b3386c16 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts
@@ -92,7 +92,7 @@ &gpio_keys {
pinctrl-names = "default";
pinctrl-0 = <&bt_host_wake_l>, <&cpu1_pen_eject>;
- pen-insert {
+ switch-pen-insert {
label = "Pen Insert";
/* Insert = low, eject = high */
gpios = <&gpio0 13 GPIO_ACTIVE_LOW>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi
index 913d845eb51a..0dadac51daa6 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi
@@ -183,7 +183,7 @@ gpio_keys: gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pen_eject_odl>;
- pen-insert {
+ switch-pen-insert {
label = "Pen Insert";
/* Insert = low, eject = high */
gpios = <&gpio1 1 GPIO_ACTIVE_LOW>;
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
index 46c4581deb8d..2a332763c35c 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi
@@ -136,7 +136,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
index cef4d18b599d..fe5b52610010 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts
@@ -46,9 +46,9 @@ wan_led: led-wan {
gpio-keys {
pinctrl-0 = <&reset_button_pin>;
- /delete-node/ power;
+ /delete-node/ key-power;
- reset {
+ key-reset {
debounce-interval = <50>;
gpios = <&gpio1 RK_PC6 GPIO_ACTIVE_LOW>;
label = "reset";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
index 248ad41a976b..278123b4f911 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi
@@ -111,7 +111,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&power_key>;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts
index ed856bfcfc33..9e2e246e0bab 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-orangepi.dts
@@ -78,7 +78,7 @@ keys: gpio-keys {
compatible = "gpio-keys";
autorepeat;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
index d6b68d77d63a..194e48c755f6 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts
@@ -76,7 +76,7 @@ gpio-key-lid {
pinctrl-names = "default";
pinctrl-0 = <&lidbtn_pin>;
- lid {
+ switch-lid {
debounce-interval = <20>;
gpios = <&gpio1 RK_PA1 GPIO_ACTIVE_LOW>;
label = "Lid";
@@ -92,7 +92,7 @@ gpio-key-power {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn_pin>;
- power {
+ key-power {
debounce-interval = <20>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
index 0e45cc2d195b..acb174d3a8c5 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi
@@ -54,7 +54,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key_l>;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
index 6fdeee7d5f6d..78157521e944 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
@@ -42,7 +42,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Key Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi
index 2aa0fad8f893..e6ac292ce645 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-sapphire.dtsi
@@ -53,7 +53,7 @@ keys: gpio-keys {
compatible = "gpio-keys";
autorepeat;
- power {
+ key-power {
debounce-interval = <100>;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
index e01668e6e5f9..ea0fa627c464 100644
--- a/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi
@@ -49,7 +49,7 @@ gpio-keys {
pinctrl-0 = <&hall_int_l>;
pinctrl-names = "default";
- cover {
+ switch {
label = "cover";
gpios = <&gpio0 RK_PC7 GPIO_ACTIVE_LOW>;
linux,input-type = <EV_SW>;
--
2.34.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply related [flat|nested] 11+ messages in thread* Re: [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 11:40 ` [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema Krzysztof Kozlowski
@ 2022-06-09 13:57 ` Maya Matuszczyk
2022-06-09 14:15 ` Krzysztof Kozlowski
0 siblings, 1 reply; 11+ messages in thread
From: Maya Matuszczyk @ 2022-06-09 13:57 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, Heiko Stuebner, devicetree, arm-mail-list,
open list:ARM/Rockchip SoC..., linux-kernel
czw., 9 cze 2022 o 13:56 Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> napisał(a):
>
> The node names should be generic and DT schema expects certain pattern
> (e.g. with key/button/switch).
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
> .../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
> .../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
> arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
> .../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
> .../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
> .../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
> arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
> .../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
> .../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
> .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
> .../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
> .../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
> .../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
> 21 files changed, 38 insertions(+), 38 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> index 9b4f855ea5d4..4b5413b12bfa 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> @@ -75,7 +75,7 @@ gpio-keys {
> pinctrl-names = "default";
> pinctrl-0 = <&pwr_key>;
>
> - power {
> + power-key {
> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> linux,code = <KEY_POWER>;
> label = "GPIO Key Power";
> diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> index ea0695b51ecd..72328dd993ee 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> @@ -71,82 +71,82 @@ gpio-keys {
> * |------------------------------------------------|
> */
>
> - sw1 {
> + switch-1 {
Wouldn't it make more sense to rename this and all other
renamed nodes in this dts into "button-dpad-up" or "button-1",
as on the physical device those are buttons and the naming
scheme of "sw" + number seems to be a carryover from
downstream sources.
> gpios = <&gpio1 RK_PB4 GPIO_ACTIVE_LOW>;
> label = "DPAD-UP";
> linux,code = <BTN_DPAD_UP>;
> };
> - sw2 {
> + switch-2 {
> gpios = <&gpio1 RK_PB5 GPIO_ACTIVE_LOW>;
> label = "DPAD-DOWN";
> linux,code = <BTN_DPAD_DOWN>;
> };
> - sw3 {
> + switch-3 {
> gpios = <&gpio1 RK_PB6 GPIO_ACTIVE_LOW>;
> label = "DPAD-LEFT";
> linux,code = <BTN_DPAD_LEFT>;
> };
> - sw4 {
> + switch-4 {
> gpios = <&gpio1 RK_PB7 GPIO_ACTIVE_LOW>;
> label = "DPAD-RIGHT";
> linux,code = <BTN_DPAD_RIGHT>;
> };
> - sw5 {
> + switch-5 {
> gpios = <&gpio1 RK_PA2 GPIO_ACTIVE_LOW>;
> label = "BTN-A";
> linux,code = <BTN_EAST>;
> };
> - sw6 {
> + switch-6 {
> gpios = <&gpio1 RK_PA5 GPIO_ACTIVE_LOW>;
> label = "BTN-B";
> linux,code = <BTN_SOUTH>;
> };
> - sw7 {
> + switch-7 {
> gpios = <&gpio1 RK_PA6 GPIO_ACTIVE_LOW>;
> label = "BTN-Y";
> linux,code = <BTN_WEST>;
> };
> - sw8 {
> + switch-8 {
> gpios = <&gpio1 RK_PA7 GPIO_ACTIVE_LOW>;
> label = "BTN-X";
> linux,code = <BTN_NORTH>;
> };
> - sw9 {
> + switch-9 {
> gpios = <&gpio2 RK_PA0 GPIO_ACTIVE_LOW>;
> label = "F1";
> linux,code = <BTN_TRIGGER_HAPPY1>;
> };
> - sw10 {
> + switch-10 {
> gpios = <&gpio2 RK_PA1 GPIO_ACTIVE_LOW>;
> label = "F2";
> linux,code = <BTN_TRIGGER_HAPPY2>;
> };
> - sw11 {
> + switch-11 {
> gpios = <&gpio2 RK_PA2 GPIO_ACTIVE_LOW>;
> label = "F3";
> linux,code = <BTN_TRIGGER_HAPPY3>;
> };
> - sw12 {
> + switch-12 {
> gpios = <&gpio2 RK_PA3 GPIO_ACTIVE_LOW>;
> label = "F4";
> linux,code = <BTN_TRIGGER_HAPPY4>;
> };
> - sw13 {
> + switch-13 {
> gpios = <&gpio2 RK_PA4 GPIO_ACTIVE_LOW>;
> label = "F5";
> linux,code = <BTN_TRIGGER_HAPPY5>;
> };
> - sw14 {
> + switch-14 {
> gpios = <&gpio2 RK_PA5 GPIO_ACTIVE_LOW>;
> label = "F6";
> linux,code = <BTN_TRIGGER_HAPPY6>;
> };
> - sw15 {
> + switch-15 {
> gpios = <&gpio2 RK_PA6 GPIO_ACTIVE_LOW>;
> label = "TOP-LEFT";
> linux,code = <BTN_TL>;
> };
> - sw16 {
> + switch-16 {
> gpios = <&gpio2 RK_PA7 GPIO_ACTIVE_LOW>;
> label = "TOP-RIGHT";
> linux,code = <BTN_TR>;
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts b/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
> index 3857d487ab84..1445b879ac7a 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts
> @@ -34,7 +34,7 @@ keys {
> pinctrl-0 = <&reset_button_pin>;
> pinctrl-names = "default";
>
> - reset {
> + key-reset {
> label = "reset";
> gpios = <&gpio0 RK_PA0 GPIO_ACTIVE_LOW>;
> linux,code = <KEY_RESTART>;
[snip]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 13:57 ` Maya Matuszczyk
@ 2022-06-09 14:15 ` Krzysztof Kozlowski
2022-06-09 14:56 ` Heiko Stübner
0 siblings, 1 reply; 11+ messages in thread
From: Krzysztof Kozlowski @ 2022-06-09 14:15 UTC (permalink / raw)
To: Maya Matuszczyk
Cc: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, Heiko Stuebner, devicetree, arm-mail-list,
open list:ARM/Rockchip SoC..., linux-kernel
On 09/06/2022 15:57, Maya Matuszczyk wrote:
> czw., 9 cze 2022 o 13:56 Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> napisał(a):
>>
>> The node names should be generic and DT schema expects certain pattern
>> (e.g. with key/button/switch).
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
>> .../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
>> .../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
>> arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
>> .../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
>> .../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
>> arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
>> .../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
>> .../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
>> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
>> .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
>> .../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
>> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
>> .../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
>> 21 files changed, 38 insertions(+), 38 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>> index 9b4f855ea5d4..4b5413b12bfa 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>> @@ -75,7 +75,7 @@ gpio-keys {
>> pinctrl-names = "default";
>> pinctrl-0 = <&pwr_key>;
>>
>> - power {
>> + power-key {
>> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
>> linux,code = <KEY_POWER>;
>> label = "GPIO Key Power";
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>> index ea0695b51ecd..72328dd993ee 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>> @@ -71,82 +71,82 @@ gpio-keys {
>> * |------------------------------------------------|
>> */
>>
>> - sw1 {
>> + switch-1 {
> Wouldn't it make more sense to rename this and all other
> renamed nodes in this dts into "button-dpad-up" or "button-1",
> as on the physical device those are buttons and the naming
> scheme of "sw" + number seems to be a carryover from
> downstream sources.
Can be buttons. I assumed SW comes from some kind of switch.
I assume you mean only this Odroid Go2 DTS, because some other DTSes
(like EVB above) explicitly call it "Key Power".
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 14:15 ` Krzysztof Kozlowski
@ 2022-06-09 14:56 ` Heiko Stübner
2022-06-09 15:05 ` Krzysztof Kozlowski
0 siblings, 1 reply; 11+ messages in thread
From: Heiko Stübner @ 2022-06-09 14:56 UTC (permalink / raw)
To: Maya Matuszczyk, Krzysztof Kozlowski
Cc: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, devicetree, arm-mail-list,
open list:ARM/Rockchip SoC..., linux-kernel
Am Donnerstag, 9. Juni 2022, 16:15:25 CEST schrieb Krzysztof Kozlowski:
> On 09/06/2022 15:57, Maya Matuszczyk wrote:
> > czw., 9 cze 2022 o 13:56 Krzysztof Kozlowski
> > <krzysztof.kozlowski@linaro.org> napisał(a):
> >>
> >> The node names should be generic and DT schema expects certain pattern
> >> (e.g. with key/button/switch).
> >>
> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >> ---
> >> arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
> >> .../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
> >> .../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
> >> arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
> >> .../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
> >> .../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
> >> arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
> >> .../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
> >> .../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
> >> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
> >> .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
> >> .../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
> >> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
> >> .../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
> >> 21 files changed, 38 insertions(+), 38 deletions(-)
> >>
> >> diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >> index 9b4f855ea5d4..4b5413b12bfa 100644
> >> --- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >> +++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >> @@ -75,7 +75,7 @@ gpio-keys {
> >> pinctrl-names = "default";
> >> pinctrl-0 = <&pwr_key>;
> >>
> >> - power {
> >> + power-key {
hmm, it looks like all the others below are named key-power, while
only this uses power-key ?
> >> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> >> linux,code = <KEY_POWER>;
> >> label = "GPIO Key Power";
> >> diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >> index ea0695b51ecd..72328dd993ee 100644
> >> --- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >> +++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >> @@ -71,82 +71,82 @@ gpio-keys {
> >> * |------------------------------------------------|
> >> */
> >>
> >> - sw1 {
> >> + switch-1 {
> > Wouldn't it make more sense to rename this and all other
> > renamed nodes in this dts into "button-dpad-up" or "button-1",
> > as on the physical device those are buttons and the naming
> > scheme of "sw" + number seems to be a carryover from
> > downstream sources.
The naming actually carries over from the device itself.
In the schematics the relevant keys are also named sw1, sw2, etc.
And I do believe it is way nicer when devicetree names correspond to the
things you find in device schematics and not be named "arbitarily" to
only conform to some schema ;-)
So personally I'd actually prefer going with switch-sw1 (or button-sw1 if
you prefer) as being able to just use the search function in schematic pdfs
is a helpful tool.
Heiko
> Can be buttons. I assumed SW comes from some kind of switch.
> I assume you mean only this Odroid Go2 DTS, because some other DTSes
> (like EVB above) explicitly call it "Key Power".
>
>
> Best regards,
> Krzysztof
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 14:56 ` Heiko Stübner
@ 2022-06-09 15:05 ` Krzysztof Kozlowski
2022-06-09 15:55 ` Heiko Stübner
0 siblings, 1 reply; 11+ messages in thread
From: Krzysztof Kozlowski @ 2022-06-09 15:05 UTC (permalink / raw)
To: Heiko Stübner, Maya Matuszczyk
Cc: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, devicetree, arm-mail-list,
open list:ARM/Rockchip SoC..., linux-kernel
On 09/06/2022 16:56, Heiko Stübner wrote:
> Am Donnerstag, 9. Juni 2022, 16:15:25 CEST schrieb Krzysztof Kozlowski:
>> On 09/06/2022 15:57, Maya Matuszczyk wrote:
>>> czw., 9 cze 2022 o 13:56 Krzysztof Kozlowski
>>> <krzysztof.kozlowski@linaro.org> napisał(a):
>>>>
>>>> The node names should be generic and DT schema expects certain pattern
>>>> (e.g. with key/button/switch).
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> ---
>>>> arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
>>>> .../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
>>>> .../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
>>>> arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
>>>> .../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
>>>> .../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
>>>> arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
>>>> .../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
>>>> .../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
>>>> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
>>>> .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
>>>> .../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
>>>> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
>>>> .../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
>>>> 21 files changed, 38 insertions(+), 38 deletions(-)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>>>> index 9b4f855ea5d4..4b5413b12bfa 100644
>>>> --- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>>>> +++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
>>>> @@ -75,7 +75,7 @@ gpio-keys {
>>>> pinctrl-names = "default";
>>>> pinctrl-0 = <&pwr_key>;
>>>>
>>>> - power {
>>>> + power-key {
>
> hmm, it looks like all the others below are named key-power, while
> only this uses power-key ?
>
Because a bit earlier in DTS, there are two adc-keys nodes with "key"
suffix, so I kept that approach to be consistent within one DTS. If you
prefer, I can change it to key-power.
>
>>>> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
>>>> linux,code = <KEY_POWER>;
>>>> label = "GPIO Key Power";
>>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>>>> index ea0695b51ecd..72328dd993ee 100644
>>>> --- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>>>> +++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
>>>> @@ -71,82 +71,82 @@ gpio-keys {
>>>> * |------------------------------------------------|
>>>> */
>>>>
>>>> - sw1 {
>>>> + switch-1 {
>>> Wouldn't it make more sense to rename this and all other
>>> renamed nodes in this dts into "button-dpad-up" or "button-1",
>>> as on the physical device those are buttons and the naming
>>> scheme of "sw" + number seems to be a carryover from
>>> downstream sources.
>
> The naming actually carries over from the device itself.
> In the schematics the relevant keys are also named sw1, sw2, etc.
>
> And I do believe it is way nicer when devicetree names correspond to the
> things you find in device schematics and not be named "arbitarily" to
> only conform to some schema ;-)
Then you are entirely depending on hardware engineers which might start
calling their buttons "cute-pony-xxx" :)
>
> So personally I'd actually prefer going with switch-sw1 (or button-sw1 if
> you prefer) as being able to just use the search function in schematic pdfs
> is a helpful tool.
Both are fine with me, let's just pick one - switch-sw1 or button-sw1.
Since these are physically buttons, I propose the latter.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 15:05 ` Krzysztof Kozlowski
@ 2022-06-09 15:55 ` Heiko Stübner
0 siblings, 0 replies; 11+ messages in thread
From: Heiko Stübner @ 2022-06-09 15:55 UTC (permalink / raw)
To: Maya Matuszczyk, Krzysztof Kozlowski
Cc: Arnd Bergmann, Olof Johansson, arm, soc, Rob Herring,
Krzysztof Kozlowski, devicetree, arm-mail-list,
open list:ARM/Rockchip SoC..., linux-kernel
Am Donnerstag, 9. Juni 2022, 17:05:49 CEST schrieb Krzysztof Kozlowski:
> On 09/06/2022 16:56, Heiko Stübner wrote:
> > Am Donnerstag, 9. Juni 2022, 16:15:25 CEST schrieb Krzysztof Kozlowski:
> >> On 09/06/2022 15:57, Maya Matuszczyk wrote:
> >>> czw., 9 cze 2022 o 13:56 Krzysztof Kozlowski
> >>> <krzysztof.kozlowski@linaro.org> napisał(a):
> >>>>
> >>>> The node names should be generic and DT schema expects certain pattern
> >>>> (e.g. with key/button/switch).
> >>>>
> >>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >>>> ---
> >>>> arch/arm64/boot/dts/rockchip/rk3308-evb.dts | 2 +-
> >>>> .../boot/dts/rockchip/rk3326-odroid-go2.dts | 32 +++++++++----------
> >>>> .../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 2 +-
> >>>> arch/arm64/boot/dts/rockchip/rk3368-evb.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3368-geekbox.dts | 2 +-
> >>>> .../dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
> >>>> .../boot/dts/rockchip/rk3368-px5-evb.dts | 2 +-
> >>>> arch/arm64/boot/dts/rockchip/rk3368-r88.dts | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-firefly.dts | 2 +-
> >>>> .../dts/rockchip/rk3399-gru-chromebook.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-gru-kevin.dts | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-nanopi-r4s.dts | 4 +--
> >>>> .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-orangepi.dts | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-pinebook-pro.dts | 4 +--
> >>>> .../boot/dts/rockchip/rk3399-roc-pc.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-rockpro64.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3399-sapphire.dtsi | 2 +-
> >>>> .../boot/dts/rockchip/rk3566-pinenote.dtsi | 2 +-
> >>>> 21 files changed, 38 insertions(+), 38 deletions(-)
> >>>>
> >>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >>>> index 9b4f855ea5d4..4b5413b12bfa 100644
> >>>> --- a/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >>>> +++ b/arch/arm64/boot/dts/rockchip/rk3308-evb.dts
> >>>> @@ -75,7 +75,7 @@ gpio-keys {
> >>>> pinctrl-names = "default";
> >>>> pinctrl-0 = <&pwr_key>;
> >>>>
> >>>> - power {
> >>>> + power-key {
> >
> > hmm, it looks like all the others below are named key-power, while
> > only this uses power-key ?
> >
>
> Because a bit earlier in DTS, there are two adc-keys nodes with "key"
> suffix, so I kept that approach to be consistent within one DTS. If you
> prefer, I can change it to key-power.
I just saw that discrepancy and was not sure if that was intentional.
Although with the below, I guess it makes sense to go with
$type-$name, aka key-power, same as button-sw1 etc.
> >>>> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> >>>> linux,code = <KEY_POWER>;
> >>>> label = "GPIO Key Power";
> >>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >>>> index ea0695b51ecd..72328dd993ee 100644
> >>>> --- a/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >>>> +++ b/arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts
> >>>> @@ -71,82 +71,82 @@ gpio-keys {
> >>>> * |------------------------------------------------|
> >>>> */
> >>>>
> >>>> - sw1 {
> >>>> + switch-1 {
> >>> Wouldn't it make more sense to rename this and all other
> >>> renamed nodes in this dts into "button-dpad-up" or "button-1",
> >>> as on the physical device those are buttons and the naming
> >>> scheme of "sw" + number seems to be a carryover from
> >>> downstream sources.
> >
> > The naming actually carries over from the device itself.
> > In the schematics the relevant keys are also named sw1, sw2, etc.
> >
> > And I do believe it is way nicer when devicetree names correspond to the
> > things you find in device schematics and not be named "arbitarily" to
> > only conform to some schema ;-)
>
> Then you are entirely depending on hardware engineers which might start
> calling their buttons "cute-pony-xxx" :)
What's wrong with cute-ponies?
Though it should be button-cute-pony-xxx then ;-)
> > So personally I'd actually prefer going with switch-sw1 (or button-sw1 if
> > you prefer) as being able to just use the search function in schematic pdfs
> > is a helpful tool.
>
> Both are fine with me, let's just pick one - switch-sw1 or button-sw1.
> Since these are physically buttons, I propose the latter.
fine by me, button-sw1, etc it is then :-)
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH v2 33/48] ARM: dts: rockchip: align gpio-key node names with dtschema
2022-06-09 11:37 [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Krzysztof Kozlowski
2022-06-09 11:40 ` [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema Krzysztof Kozlowski
@ 2022-06-09 11:40 ` Krzysztof Kozlowski
2022-06-09 11:40 ` [PATCH v2 34/48] ARM: dts: rockchip: rk3288-tinker: correct gpio-keys properties Krzysztof Kozlowski
` (2 subsequent siblings)
4 siblings, 0 replies; 11+ messages in thread
From: Krzysztof Kozlowski @ 2022-06-09 11:40 UTC (permalink / raw)
To: Arnd Bergmann, Olof Johansson, arm, soc, Heiko Stuebner,
Rob Herring, Krzysztof Kozlowski, linux-arm-kernel,
linux-rockchip, devicetree, linux-kernel
Cc: Krzysztof Kozlowski
The node names should be generic and DT schema expects certain pattern
(e.g. with key/button/switch).
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
arch/arm/boot/dts/rk3066a-bqcurie2.dts | 4 ++--
arch/arm/boot/dts/rk3066a-rayeager.dts | 2 +-
arch/arm/boot/dts/rk3188-bqedison2qc.dts | 4 ++--
arch/arm/boot/dts/rk3188-px3-evb.dts | 2 +-
arch/arm/boot/dts/rk3188-radxarock.dts | 2 +-
arch/arm/boot/dts/rk3229-evb.dts | 2 +-
arch/arm/boot/dts/rk3288-evb.dtsi | 2 +-
arch/arm/boot/dts/rk3288-firefly-reload.dts | 2 +-
arch/arm/boot/dts/rk3288-firefly.dtsi | 2 +-
arch/arm/boot/dts/rk3288-phycore-rdk.dts | 4 ++--
arch/arm/boot/dts/rk3288-popmetal.dts | 2 +-
arch/arm/boot/dts/rk3288-r89.dts | 2 +-
arch/arm/boot/dts/rk3288-rock2-square.dts | 2 +-
arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi | 2 +-
arch/arm/boot/dts/rk3288-veyron-minnie.dts | 4 ++--
arch/arm/boot/dts/rk3288-veyron-pinky.dts | 2 +-
arch/arm/boot/dts/rk3288-veyron.dtsi | 2 +-
17 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/arch/arm/boot/dts/rk3066a-bqcurie2.dts b/arch/arm/boot/dts/rk3066a-bqcurie2.dts
index 390aa33cd55a..962b4d1291db 100644
--- a/arch/arm/boot/dts/rk3066a-bqcurie2.dts
+++ b/arch/arm/boot/dts/rk3066a-bqcurie2.dts
@@ -48,7 +48,7 @@ gpio-keys {
compatible = "gpio-keys";
autorepeat;
- power {
+ key-power {
gpios = <&gpio6 RK_PA2 GPIO_ACTIVE_LOW>; /* GPIO6_A2 */
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
@@ -56,7 +56,7 @@ power {
wakeup-source;
debounce-interval = <100>;
};
- volume-down {
+ key-volume-down {
gpios = <&gpio4 RK_PC5 GPIO_ACTIVE_LOW>; /* GPIO4_C5 */
linux,code = <KEY_VOLUMEDOWN>;
label = "GPIO Key Vol-";
diff --git a/arch/arm/boot/dts/rk3066a-rayeager.dts b/arch/arm/boot/dts/rk3066a-rayeager.dts
index 12b2e59aebc4..dbbc5170094e 100644
--- a/arch/arm/boot/dts/rk3066a-rayeager.dts
+++ b/arch/arm/boot/dts/rk3066a-rayeager.dts
@@ -32,7 +32,7 @@ ir: ir-receiver {
keys: gpio-keys {
compatible = "gpio-keys";
- power {
+ key-power {
wakeup-source;
gpios = <&gpio6 RK_PA2 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm/boot/dts/rk3188-bqedison2qc.dts b/arch/arm/boot/dts/rk3188-bqedison2qc.dts
index 35b7a5798eee..9312be362a7a 100644
--- a/arch/arm/boot/dts/rk3188-bqedison2qc.dts
+++ b/arch/arm/boot/dts/rk3188-bqedison2qc.dts
@@ -37,7 +37,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key &usb_int>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA4 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
@@ -46,7 +46,7 @@ power {
wakeup-source;
};
- wake_on_usb: wake-on-usb {
+ wake_on_usb: key-wake-on-usb {
label = "Wake-on-USB";
gpios = <&gpio0 RK_PA7 GPIO_ACTIVE_LOW>;
linux,code = <KEY_WAKEUP>;
diff --git a/arch/arm/boot/dts/rk3188-px3-evb.dts b/arch/arm/boot/dts/rk3188-px3-evb.dts
index fc478ac4e781..0a1ae689b162 100644
--- a/arch/arm/boot/dts/rk3188-px3-evb.dts
+++ b/arch/arm/boot/dts/rk3188-px3-evb.dts
@@ -29,7 +29,7 @@ gpio-keys {
compatible = "gpio-keys";
autorepeat;
- power {
+ key-power {
gpios = <&gpio0 RK_PA4 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm/boot/dts/rk3188-radxarock.dts b/arch/arm/boot/dts/rk3188-radxarock.dts
index 36c0945f43b2..a9ed3cd2c2da 100644
--- a/arch/arm/boot/dts/rk3188-radxarock.dts
+++ b/arch/arm/boot/dts/rk3188-radxarock.dts
@@ -24,7 +24,7 @@ gpio-keys {
compatible = "gpio-keys";
autorepeat;
- power {
+ key-power {
gpios = <&gpio0 RK_PA4 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm/boot/dts/rk3229-evb.dts b/arch/arm/boot/dts/rk3229-evb.dts
index 797476e8bef1..5c3d08e3eea3 100644
--- a/arch/arm/boot/dts/rk3229-evb.dts
+++ b/arch/arm/boot/dts/rk3229-evb.dts
@@ -107,7 +107,7 @@ vdd_log: vdd-log-regulator {
regulator-boot-on;
};
- gpio_keys {
+ gpio-keys {
compatible = "gpio-keys";
autorepeat;
pinctrl-names = "default";
diff --git a/arch/arm/boot/dts/rk3288-evb.dtsi b/arch/arm/boot/dts/rk3288-evb.dtsi
index c4ca73b40d4a..399d6b9c5fd4 100644
--- a/arch/arm/boot/dts/rk3288-evb.dtsi
+++ b/arch/arm/boot/dts/rk3288-evb.dtsi
@@ -118,7 +118,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm/boot/dts/rk3288-firefly-reload.dts b/arch/arm/boot/dts/rk3288-firefly-reload.dts
index 9a4a9749c405..a5a0826341e6 100644
--- a/arch/arm/boot/dts/rk3288-firefly-reload.dts
+++ b/arch/arm/boot/dts/rk3288-firefly-reload.dts
@@ -27,7 +27,7 @@ button-recovery {
gpio-keys {
compatible = "gpio-keys";
- power {
+ key-power {
wakeup-source;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm/boot/dts/rk3288-firefly.dtsi b/arch/arm/boot/dts/rk3288-firefly.dtsi
index 7fb582302b32..052afe5543e2 100644
--- a/arch/arm/boot/dts/rk3288-firefly.dtsi
+++ b/arch/arm/boot/dts/rk3288-firefly.dtsi
@@ -49,7 +49,7 @@ ir: ir-receiver {
keys: gpio-keys {
compatible = "gpio-keys";
- power {
+ key-power {
wakeup-source;
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
diff --git a/arch/arm/boot/dts/rk3288-phycore-rdk.dts b/arch/arm/boot/dts/rk3288-phycore-rdk.dts
index 1e33859de484..1a5156951492 100644
--- a/arch/arm/boot/dts/rk3288-phycore-rdk.dts
+++ b/arch/arm/boot/dts/rk3288-phycore-rdk.dts
@@ -20,14 +20,14 @@ user_buttons: user-buttons {
pinctrl-names = "default";
pinctrl-0 = <&user_button_pins>;
- button@0 {
+ button-0 {
label = "home";
linux,code = <KEY_HOME>;
gpios = <&gpio8 0 GPIO_ACTIVE_HIGH>;
wakeup-source;
};
- button@1 {
+ button-1 {
label = "menu";
linux,code = <KEY_MENU>;
gpios = <&gpio8 3 GPIO_ACTIVE_HIGH>;
diff --git a/arch/arm/boot/dts/rk3288-popmetal.dts b/arch/arm/boot/dts/rk3288-popmetal.dts
index 8c7376d64bc4..fd90f3b8fc32 100644
--- a/arch/arm/boot/dts/rk3288-popmetal.dts
+++ b/arch/arm/boot/dts/rk3288-popmetal.dts
@@ -30,7 +30,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm/boot/dts/rk3288-r89.dts b/arch/arm/boot/dts/rk3288-r89.dts
index 55467bc30fa6..633e5a032463 100644
--- a/arch/arm/boot/dts/rk3288-r89.dts
+++ b/arch/arm/boot/dts/rk3288-r89.dts
@@ -31,7 +31,7 @@ gpio-keys {
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
diff --git a/arch/arm/boot/dts/rk3288-rock2-square.dts b/arch/arm/boot/dts/rk3288-rock2-square.dts
index c4d1d142d8c6..80e0f07c8e87 100644
--- a/arch/arm/boot/dts/rk3288-rock2-square.dts
+++ b/arch/arm/boot/dts/rk3288-rock2-square.dts
@@ -28,7 +28,7 @@ button-recovery {
gpio-keys {
compatible = "gpio-keys";
- power {
+ key-power {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
label = "GPIO Power";
linux,code = <KEY_POWER>;
diff --git a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
index 05112c25176d..700bb548d6b2 100644
--- a/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
+++ b/arch/arm/boot/dts/rk3288-veyron-chromebook.dtsi
@@ -32,7 +32,7 @@ lid_switch: lid-switch {
pinctrl-names = "default";
pinctrl-0 = <&ap_lid_int_l>;
- lid {
+ switch-lid {
label = "Lid";
gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
wakeup-source;
diff --git a/arch/arm/boot/dts/rk3288-veyron-minnie.dts b/arch/arm/boot/dts/rk3288-veyron-minnie.dts
index 82fc6fba9999..dcdcc55c4098 100644
--- a/arch/arm/boot/dts/rk3288-veyron-minnie.dts
+++ b/arch/arm/boot/dts/rk3288-veyron-minnie.dts
@@ -21,14 +21,14 @@ volume_buttons: volume-buttons {
pinctrl-names = "default";
pinctrl-0 = <&volum_down_l &volum_up_l>;
- volum_down {
+ key-volum-down {
label = "Volum_down";
gpios = <&gpio5 RK_PB3 GPIO_ACTIVE_LOW>;
linux,code = <KEY_VOLUMEDOWN>;
debounce-interval = <100>;
};
- volum_up {
+ key-volum-up {
label = "Volum_up";
gpios = <&gpio5 RK_PB2 GPIO_ACTIVE_LOW>;
linux,code = <KEY_VOLUMEUP>;
diff --git a/arch/arm/boot/dts/rk3288-veyron-pinky.dts b/arch/arm/boot/dts/rk3288-veyron-pinky.dts
index 4e9fdb0f722d..e2a4e6232eb5 100644
--- a/arch/arm/boot/dts/rk3288-veyron-pinky.dts
+++ b/arch/arm/boot/dts/rk3288-veyron-pinky.dts
@@ -45,7 +45,7 @@ &edp {
&lid_switch {
pinctrl-0 = <&pwr_key_h &ap_lid_int_l>;
- power {
+ key-power {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_HIGH>;
};
};
diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi b/arch/arm/boot/dts/rk3288-veyron.dtsi
index 54a6838d73f5..e406c8c7c7e5 100644
--- a/arch/arm/boot/dts/rk3288-veyron.dtsi
+++ b/arch/arm/boot/dts/rk3288-veyron.dtsi
@@ -29,7 +29,7 @@ power_button: power-button {
pinctrl-names = "default";
pinctrl-0 = <&pwr_key_l>;
- power {
+ key-power {
label = "Power";
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
--
2.34.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply related [flat|nested] 11+ messages in thread* [PATCH v2 34/48] ARM: dts: rockchip: rk3288-tinker: correct gpio-keys properties
2022-06-09 11:37 [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Krzysztof Kozlowski
2022-06-09 11:40 ` [PATCH v2 32/48] arm64: dts: rockchip: align gpio-key node names with dtschema Krzysztof Kozlowski
2022-06-09 11:40 ` [PATCH v2 33/48] ARM: " Krzysztof Kozlowski
@ 2022-06-09 11:40 ` Krzysztof Kozlowski
2022-06-10 6:37 ` (subset) [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Neil Armstrong
2022-07-03 3:56 ` Bjorn Andersson
4 siblings, 0 replies; 11+ messages in thread
From: Krzysztof Kozlowski @ 2022-06-09 11:40 UTC (permalink / raw)
To: Arnd Bergmann, Olof Johansson, arm, soc, Heiko Stuebner,
Rob Herring, Krzysztof Kozlowski, linux-arm-kernel,
linux-rockchip, devicetree, linux-kernel
Cc: Krzysztof Kozlowski
gpio-keys children do not use unit addresses.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
arch/arm/boot/dts/rk3288-tinker.dtsi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/rk3288-tinker.dtsi b/arch/arm/boot/dts/rk3288-tinker.dtsi
index 9c1e38c54eae..09618bb7d872 100644
--- a/arch/arm/boot/dts/rk3288-tinker.dtsi
+++ b/arch/arm/boot/dts/rk3288-tinker.dtsi
@@ -26,14 +26,12 @@ ext_gmac: external-gmac-clock {
gpio-keys {
compatible = "gpio-keys";
- #address-cells = <1>;
- #size-cells = <0>;
autorepeat;
pinctrl-names = "default";
pinctrl-0 = <&pwrbtn>;
- button@0 {
+ button {
gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_POWER>;
label = "GPIO Key Power";
--
2.34.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply related [flat|nested] 11+ messages in thread* Re: (subset) [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children
2022-06-09 11:37 [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Krzysztof Kozlowski
` (2 preceding siblings ...)
2022-06-09 11:40 ` [PATCH v2 34/48] ARM: dts: rockchip: rk3288-tinker: correct gpio-keys properties Krzysztof Kozlowski
@ 2022-06-10 6:37 ` Neil Armstrong
2022-07-03 3:56 ` Bjorn Andersson
4 siblings, 0 replies; 11+ messages in thread
From: Neil Armstrong @ 2022-06-10 6:37 UTC (permalink / raw)
To: Krzysztof Kozlowski, soc, Arnd Bergmann, Olof Johansson, arm
Cc: Neil Armstrong, NXP Linux Team, Hauke Mehrtens, Jernej Skrabec,
linux-mediatek, Alim Akhtar, linux-tegra, Rob Herring,
Tero Kristo, Vignesh Raghavendra, Shawn Guo, Matthias Brugger,
linux-omap, Rafał Miłecki, Tony Lindgren, Scott Branden,
linux-gpio, linux-amlogic, Kevin Hilman, Pengutronix Kernel Team,
Fabio Estevam, Andrew Lunn, Nishanth Menon, devicetree,
Chen-Yu Tsai, linux-arm-msm, Linus Walleij, Samuel Holland,
Nicolas Ferre, Russell King, Jonathan Hunter, Gregory Clement,
linux-arm-kernel, Heiko Stuebner, linux-kernel, Andrew Jeffery,
linux-input, Alexandre Belloni, Benoît Cousson,
Krzysztof Kozlowski, Peter Rosin, Khuong Dinh, Claudiu Beznea,
Broadcom internal kernel review list, Andy Gross, Michal Simek,
Sebastian Hesselbarth, linux-sunxi, Bjorn Andersson,
linux-samsung-soc, Florian Fainelli, Thierry Reding, Ray Jui,
Sascha Hauer, Jonathan Neuschäfer, Li Yang, Jerome Brunet,
Wei Xu, Dmitry Torokhov, linux-aspeed, openbmc,
Martin Blumenstingl, Joel Stanley, linux-rockchip
Hi,
On Thu, 9 Jun 2022 13:37:21 +0200, Krzysztof Kozlowski wrote:
> Merging
> =======
> 1. dt-bindings: rebased on top of Rob's:
> https://lore.kernel.org/all/20220608211207.2058487-1-robh@kernel.org/
>
> 2. DTS patches are independent. They can be picked up directly by sub-arch
> maintainers, by Arnd or Olof, or eventually by me (if you wish).
>
> [...]
Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v5.20/arm64-dt)
[07/48] arm64: dts: amlogic: correct gpio-keys properties
https://git.kernel.org/amlogic/c/4956be9944d1fb23107f27bad8a2cca0fa167443
[08/48] arm64: dts: amlogic: align gpio-key node names with dtschema
https://git.kernel.org/amlogic/c/4fd9afd894ebe5831dbd737e6ca7b6de14da7fda
These changes has been applied on the intermediate git tree [1].
The v5.20/arm64-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
for inclusion in their intermediate git branches in order to be sent to Linus during
the next merge window, or sooner if it's a set of fixes.
In the cases of fixes, those will be merged in the current release candidate
kernel and as soon they appear on the Linux master branch they will be
backported to the previous Stable and Long-Stable kernels [2].
The intermediate git branches are merged daily in the linux-next tree [3],
people are encouraged testing these pre-release kernels and report issues on the
relevant mailing-lists.
If problems are discovered on those changes, please submit a signed-off-by revert
patch followed by a corrective changeset.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
--
Neil
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: (subset) [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children
2022-06-09 11:37 [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Krzysztof Kozlowski
` (3 preceding siblings ...)
2022-06-10 6:37 ` (subset) [PATCH v2 00/48] dt-bindings: input: gpio-keys: rework matching children Neil Armstrong
@ 2022-07-03 3:56 ` Bjorn Andersson
4 siblings, 0 replies; 11+ messages in thread
From: Bjorn Andersson @ 2022-07-03 3:56 UTC (permalink / raw)
To: Krzysztof Kozlowski, Olof Johansson, soc, Arnd Bergmann, arm
Cc: Li Yang, Matthias Brugger, Jernej Skrabec, Florian Fainelli,
Neil Armstrong, Tony Lindgren, Sebastian Hesselbarth,
Joel Stanley, Thierry Reding, Shawn Guo, Tero Kristo,
Rafał Miłecki, Hauke Mehrtens, Scott Branden,
linux-rockchip, Russell King, Benoît Cousson, Rob Herring,
linux-sunxi, linux-kernel, linux-arm-msm, Pengutronix Kernel Team,
Dmitry Torokhov, linux-tegra, Khuong Dinh, linux-gpio,
Kevin Hilman, linux-amlogic, Fabio Estevam, Michal Simek,
linux-samsung-soc, Vignesh Raghavendra, Linus Walleij,
NXP Linux Team, Andrew Jeffery, Heiko Stuebner, Nishanth Menon,
Jerome Brunet, Peter Rosin, linux-arm-kernel,
Broadcom internal kernel review list, Sascha Hauer, Alim Akhtar,
openbmc, Nicolas Ferre, Andy Gross, Wei Xu, linux-omap,
Krzysztof Kozlowski, devicetree, linux-mediatek, Ray Jui,
Gregory Clement, Jonathan Neuschäfer, Martin Blumenstingl,
linux-input, linux-aspeed, Chen-Yu Tsai, Alexandre Belloni,
Jonathan Hunter, Samuel Holland, Andrew Lunn, Claudiu Beznea
On Thu, 9 Jun 2022 13:37:21 +0200, Krzysztof Kozlowski wrote:
> Merging
> =======
> 1. dt-bindings: rebased on top of Rob's:
> https://lore.kernel.org/all/20220608211207.2058487-1-robh@kernel.org/
>
> 2. DTS patches are independent. They can be picked up directly by sub-arch
> maintainers, by Arnd or Olof, or eventually by me (if you wish).
>
> [...]
Applied, thanks!
[27/48] arm64: dts: qcom: align gpio-key node names with dtschema
commit: b08f5cbd69dcd25f5ab2a0798fe3836a97a9d7c6
[28/48] arm64: dts: qcom: correct gpio-keys properties
commit: 5a4b0b853a2914403746b0a1decab695202ff242
[29/48] arm64: dts: qcom: sdm630-sony-xperia-nile: drop unneeded status from gpio-keys
commit: 9d8840f6ee426b6dfcb65bdf39e2898652e2b1e5
[30/48] arm64: dts: qcom: align led node names with dtschema
commit: 3cfe94d660a8ebc19e78ea0a4781d7e9a1054c65
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
^ permalink raw reply [flat|nested] 11+ messages in thread