From: Haojian Zhuang <haojian.zhuang@linaro.org>
To: xuwei5@hisilicon.com, linus.walleij@linaro.org,
grant.likely@linaro.org, robh+dt@kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, baruch@tkos.co.il
Cc: Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: [PATCH 2/2] ARM: dts: add gpio alias in hi3620 dts file
Date: Tue, 22 Apr 2014 09:35:43 +0800 [thread overview]
Message-ID: <1398130543-19454-2-git-send-email-haojian.zhuang@linaro.org> (raw)
In-Reply-To: <1398130543-19454-1-git-send-email-haojian.zhuang@linaro.org>
Use gpio alias to identify the index of gpio chip. Then we can keep the
same gpio number as schematics. Otherwise, gpio number is countered from
bottom to top.
Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
---
arch/arm/boot/dts/hi3620.dtsi | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/hi3620.dtsi b/arch/arm/boot/dts/hi3620.dtsi
index 6836795..2aaae09 100644
--- a/arch/arm/boot/dts/hi3620.dtsi
+++ b/arch/arm/boot/dts/hi3620.dtsi
@@ -21,6 +21,28 @@
serial2 = &uart2;
serial3 = &uart3;
serial4 = &uart4;
+ gpio0 = &gpio0;
+ gpio1 = &gpio1;
+ gpio2 = &gpio2;
+ gpio3 = &gpio3;
+ gpio4 = &gpio4;
+ gpio5 = &gpio5;
+ gpio6 = &gpio6;
+ gpio7 = &gpio7;
+ gpio8 = &gpio8;
+ gpio9 = &gpio9;
+ gpio10 = &gpio10;
+ gpio11 = &gpio11;
+ gpio12 = &gpio12;
+ gpio13 = &gpio13;
+ gpio14 = &gpio14;
+ gpio15 = &gpio15;
+ gpio16 = &gpio16;
+ gpio17 = &gpio17;
+ gpio18 = &gpio18;
+ gpio19 = &gpio19;
+ gpio20 = &gpio20;
+ gpio21 = &gpio21;
};
pclk: clk {
--
1.9.1
next prev parent reply other threads:[~2014-04-22 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 1:35 [PATCH 1/2] gpio: pl061: get gpio base from alias id Haojian Zhuang
2014-04-22 1:35 ` Haojian Zhuang [this message]
2014-04-22 3:44 ` Baruch Siach
2014-04-23 13:21 ` Linus Walleij
2014-04-25 0:27 ` Haojian Zhuang
2014-04-25 9:29 ` Linus Walleij
2014-04-23 18:52 ` Rob Herring
2014-04-25 0:28 ` Haojian Zhuang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1398130543-19454-2-git-send-email-haojian.zhuang@linaro.org \
--to=haojian.zhuang@linaro.org \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=xuwei5@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).