From: Haojian Zhuang <haojian.zhuang@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Xu Wei <xuwei5@hisilicon.com>,
Linus Walleij <linus.walleij@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Baruch Siach <baruch@tkos.co.il>
Subject: Re: [PATCH 1/2] gpio: pl061: get gpio base from alias id
Date: Fri, 25 Apr 2014 08:28:28 +0800 [thread overview]
Message-ID: <CAD6h2NSZY5PNEmRVzVBuBnU_QoKVJ8WGyw4yxOQpcGRMEB_tMw@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKo0uV9_SX5aAfgPyRSa0Cv5O=tdp4s1oSQs=76vZC+ww@mail.gmail.com>
On 24 April 2014 02:52, Rob Herring <robherring2@gmail.com> wrote:
> On Mon, Apr 21, 2014 at 8:35 PM, Haojian Zhuang
> <haojian.zhuang@linaro.org> wrote:
>> If gpio base number isn't specified, the gpio base will be find from
>> the end of gpio number. In order to keep with schematics, use alias
>> to get the ID of gpio chip.
>
> NAK. This is an abuse aliases.
>
>> Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
>> ---
>> .../devicetree/bindings/gpio/gpio-pl061.txt | 31 ++++++++++++++++++++++
>
> Is something wrong with the binding doc already in pl061-gpio.txt?
>
Oh. I just copy my old patch to here. I didn't notice there's a new
pl061-gpio.txt. Thanks for reminder.
Regards
Haojian
prev parent reply other threads:[~2014-04-25 0:28 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 ` [PATCH 2/2] ARM: dts: add gpio alias in hi3620 dts file Haojian Zhuang
2014-04-22 3:44 ` [PATCH 1/2] gpio: pl061: get gpio base from alias id 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 [this message]
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=CAD6h2NSZY5PNEmRVzVBuBnU_QoKVJ8WGyw4yxOQpcGRMEB_tMw@mail.gmail.com \
--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=robherring2@gmail.com \
--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).