Commit a1fb73d7 authored by Linus Walleij's avatar Linus Walleij Committed by Wei Xu

arm64: dts: hisilicon: Standardize Poplar GPIO line names

The hi6220-HiKey board started to name GPIO lines for
96boards, using just the plain names "GPIO-A" etc from the
96boards specification.

Poplar started to use an arbitrary "LS-GPIO-A" (etc) prefix
that is not part of the 96boards specification.

As the former notation arrived first, and we need
consistency among 96board, rectify the Poplar board to use
this too. This is important for userspace that wants to
look up GPIO names from these strings.

Cc: Jiancheng Xue <xuejiancheng@hisilicon.com>
Cc: Alex Elder <elder@linaro.org>
Cc: Peter Griffin <peter.griffin@linaro.org>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
parent 63fc36cd
...@@ -78,17 +78,17 @@ eth_phy1: phy@3 { ...@@ -78,17 +78,17 @@ eth_phy1: phy@3 {
&gpio1 { &gpio1 {
status = "okay"; status = "okay";
gpio-line-names = "LS-GPIO-E", "", gpio-line-names = "GPIO-E", "",
"", "", "", "",
"", "LS-GPIO-F", "", "GPIO-F",
"", "LS-GPIO-J"; "", "GPIO-J";
}; };
&gpio2 { &gpio2 {
status = "okay"; status = "okay";
gpio-line-names = "LS-GPIO-H", "LS-GPIO-I", gpio-line-names = "GPIO-H", "GPIO-I",
"LS-GPIO-L", "LS-GPIO-G", "GPIO-L", "GPIO-G",
"LS-GPIO-K", "", "GPIO-K", "",
"", ""; "", "";
}; };
...@@ -96,15 +96,15 @@ &gpio3 { ...@@ -96,15 +96,15 @@ &gpio3 {
status = "okay"; status = "okay";
gpio-line-names = "", "", gpio-line-names = "", "",
"", "", "", "",
"LS-GPIO-C", "", "GPIO-C", "",
"", "LS-GPIO-B"; "", "GPIO-B";
}; };
&gpio4 { &gpio4 {
status = "okay"; status = "okay";
gpio-line-names = "", "", gpio-line-names = "", "",
"", "", "", "",
"", "LS-GPIO-D", "", "GPIO-D",
"", ""; "", "";
}; };
...@@ -112,7 +112,7 @@ &gpio5 { ...@@ -112,7 +112,7 @@ &gpio5 {
status = "okay"; status = "okay";
gpio-line-names = "", "USER-LED-1", gpio-line-names = "", "USER-LED-1",
"USER-LED-2", "", "USER-LED-2", "",
"", "LS-GPIO-A", "", "GPIO-A",
"", ""; "", "";
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment