From: Heiko Stuebner <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, briannorris@chromium.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-rockchip@lists.infradead.org, mka@chromium.org,
ryandcase@chromium.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: rockchip: Add pin names for rk3288-veyron-minnie
Date: Wed, 22 May 2019 10:01:39 +0200 [thread overview]
Message-ID: <1983983.hLAGMFZVp3@phil> (raw)
In-Reply-To: <20190521203215.234898-1-dianders@chromium.org>
Am Dienstag, 21. Mai 2019, 22:32:14 CEST schrieb Douglas Anderson:
> We can now use the "gpio-line-names" property to provide the names for
> all the pins on a board. Let's use this to provide the names for all
> the pins on rk3288-veyron-minnie.
>
> In general the names here come straight from the schematic. That
> means even if the schematic name is weird / doesn't have consistent
> naming conventions / has typos I still haven't made any changes.
>
> The exception here is for two pins: the recovery switch and the write
> protect detection pin. These two pins need to have standardized names
> since crossystem (a Chrome OS tool) uses these names to query the
> pins. In downstream kernels crossystem used an out-of-tree driver to
> do this but it has now been moved to the gpiod API and needs the
> standardized names.
>
> It's expected that other rk3288-veyron boards will get similar patches
> shortly.
>
> NOTE: I have sorted the "gpio" section to be next to the "pinctrl"
> section since it seems to logically make the most sense there.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied both for 5.3 ... that is actually a pretty nifty feature for
boards whose schematics cannot be published :-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-22 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:32 [PATCH 1/2] ARM: dts: rockchip: Add pin names for rk3288-veyron-minnie Douglas Anderson
2019-05-21 20:32 ` [PATCH 2/2] ARM: dts: rockchip: Add pin names for rk3288-veyron-jerry Douglas Anderson
2019-05-21 22:06 ` Matthias Kaehlcke
2019-05-21 21:34 ` [PATCH 1/2] ARM: dts: rockchip: Add pin names for rk3288-veyron-minnie Matthias Kaehlcke
2019-05-22 8:01 ` Heiko Stuebner [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=1983983.hLAGMFZVp3@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=ryandcase@chromium.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;
as well as URLs for NNTP newsgroup(s).