From: Feng Kan <fkan@apm.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>, patches <patches@apm.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] gpio: Add APM X-Gene SoC GPIO controller support
Date: Tue, 27 May 2014 09:59:02 -0700 [thread overview]
Message-ID: <CAL85gmCZD90UUZgC0-X4hui2L1V5TuH++o3fA20pRF_ZQEpDQw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdaVYXU9GN5OymuP3JRsQO3unkRGb5vZN3Jb2nWSnkh1SQ@mail.gmail.com>
On Tue, May 27, 2014 at 1:25 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, May 21, 2014 at 1:54 AM, Feng Kan <fkan@apm.com> wrote:
>
>> I see each bank as separate gpio chip. It is a simple way to
>> abstract the banks since they can operate independently.
>
> I think they should also be separate devices, and separate nodes
> in the device tree.
>
>> It also
>> provided me a way to fix the sysfs gpio base number, regardless if
>> a particular bank node is pulled out.
>
> The GPIO sysfs is unpredictable for this and many other
> reasons and should not be relied upon.
>
>> This is also done in similar way
>> in some other gpio drivers such as the dwapb gpio driver.
>
> I think the dwapb has it's registers mingled while your banks
> seem to be separate chunks.
Thanks for the comments, I will fix these problems. Just some details
in terms of the register layout. I will break out the gpio to separate
device nodes as instructed, I will have to use the reg attribute to offset
bank registers. Please let me know if it is acceptable.
gfc_gpio_fl0 GFC42'h1701c00c
gfc_gpio_fl0_mux GFC42'h1701c010
gfc_gpio_fl1 GFC42'h1701c018
gfc_gpio_fl1_mux GFC42'h1701c01c
gfc_gpio_fl2 GFC42'h1701c024
gfc_gpio_fl2_mux GFC42'h1701c028
gfc_gpio_fl0_od GFC42'h1701c030
gfc_gpio_fl1_od GFC42'h1701c034
gfc_gpio_fl2_od GFC42'h1701c038
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2014-05-27 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1400263432-922-1-git-send-email-fkan@apm.com>
[not found] ` <1400263432-922-2-git-send-email-fkan@apm.com>
2014-05-20 6:04 ` [PATCH 1/3] gpio: Add APM X-Gene SoC GPIO controller support Alexandre Courbot
2014-05-20 23:54 ` Feng Kan
2014-05-25 7:35 ` Alexandre Courbot
2014-05-27 8:25 ` Linus Walleij
2014-05-27 16:59 ` Feng Kan [this message]
2014-05-28 17:01 ` Feng Kan
2014-05-28 19:10 ` Rob Herring
2014-05-28 19:10 ` Linus Walleij
2014-05-27 7:59 ` Linus Walleij
[not found] ` <1400263432-922-4-git-send-email-fkan@apm.com>
2014-05-20 6:11 ` [PATCH 3/3] Documentation: gpio: Add APM X-Gene SoC GPIO controller DTS binding Alexandre Courbot
2014-05-27 8:30 ` Linus Walleij
[not found] ` <1400263432-922-3-git-send-email-fkan@apm.com>
2014-05-27 8:27 ` [PATCH 2/3] arm64:dts: Add APM X-Gene SoC GPIO controller DTS entries Linus Walleij
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=CAL85gmCZD90UUZgC0-X4hui2L1V5TuH++o3fA20pRF_ZQEpDQw@mail.gmail.com \
--to=fkan@apm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=patches@apm.com \
--cc=will.deacon@arm.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).