From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 resend] arm: dts: sun7i-a20-bananapi: name the GPIO lines
Date: Thu, 4 May 2017 16:56:57 +0200 [thread overview]
Message-ID: <20170504145657.yzbehfov2rgeqn5g@lukather> (raw)
In-Reply-To: <1493795360-18629-1-git-send-email-linux@rempel-privat.de>
On Wed, May 03, 2017 at 09:09:20AM +0200, Oleksij Rempel wrote:
> This names the GPIO lines on the Banana Pi board in accordance with
> the A20_Banana_Pi v1.4 Specification.
>
> This will make these line names reflect through to userspace
> so that they can easily be identified and used with the new
> character device ABI.
>
> Some care has been taken to name all lines, not just those used
> by the external connectors, also lines that are muxed into some
> other function than GPIO: these are named "[FOO]" so that users
> can see with lsgpio what all lines are used for.
>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Cc: devicetree at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: Chen-Yu Tsai <wens@csie.org>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> arch/arm/boot/dts/sun7i-a20-bananapi.dts | 60 ++++++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
>
> diff --git a/arch/arm/boot/dts/sun7i-a20-bananapi.dts b/arch/arm/boot/dts/sun7i-a20-bananapi.dts
> index 91f2e5f..5b3e0ee 100644
> --- a/arch/arm/boot/dts/sun7i-a20-bananapi.dts
> +++ b/arch/arm/boot/dts/sun7i-a20-bananapi.dts
> @@ -178,6 +178,66 @@
> };
>
> &pio {
> + /*
> + * Legend: proper name = the GPIO line is used as GPIO
I'm not convinced that a legend here is helpful in any way. No end
user is going to even search for it here.
> + * NC = not connected (not routed from the SoC)
Judging from the binding documentation, this should be the same than
"".
> + * "[PER]" = pin is muxed for peripheral (not GPIO)
We don't need the brackets. You have no guarantee that it is actually
muxed, and will need to get that info from somewhere else either
way. This is also not a syntax that is in the generic binding
definition.
> + * "" = no idea, schematic doesn't say, could be
> + * unrouted (not connected to any external pin)
> + * LSEC = Low Speed External Connector
> + * HSEC = High Speed External Connector
And both of those are not used.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170504/86a6ce79/attachment.sig>
prev parent reply other threads:[~2017-05-04 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 11:47 [PATCH] arm: dts: sun7i-a20-bananapi: name the GPIO lines Oleksij Rempel
2016-07-22 14:55 ` Linus Walleij
2016-07-22 15:47 ` Chen-Yu Tsai
2016-07-25 5:27 ` fixed-term.Oleksij.Rempel
2016-07-25 13:27 ` Linus Walleij
2016-08-05 8:05 ` Oleksij Rempel
2016-08-05 8:06 ` [PATCH v2] " Oleksij Rempel
2016-08-08 17:51 ` Linus Walleij
2017-04-28 5:11 ` Oleksij Rempel
2017-04-28 8:45 ` Linus Walleij
2017-04-28 9:03 ` Oleksij Rempel
2017-05-03 7:09 ` [PATCH v2 resend] " Oleksij Rempel
2017-05-04 14:56 ` Maxime Ripard [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=20170504145657.yzbehfov2rgeqn5g@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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