Linux-ARM-Kernel Archive on
 help / color / Atom feed
From: Heiko Stuebner <>
To: Douglas Anderson <>
Cc: Mark Rutland <>,,,, Rob Herring <>,,,,
Subject: Re: [PATCH 1/2] ARM: dts: rockchip: Add pin names for rk3288-veyron-minnie
Date: Wed, 22 May 2019 10:01:39 +0200
Message-ID: <1983983.hLAGMFZVp3@phil> (raw)
In-Reply-To: <>

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 <>

applied both for 5.3 ... that is actually a pretty nifty feature for
boards whose schematics cannot be published :-)

linux-arm-kernel mailing list

      parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 20:32 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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1983983.hLAGMFZVp3@phil \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-ARM-Kernel Archive on

Archives are clonable:
	git clone --mirror linux-arm-kernel/git/0.git
	git clone --mirror linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ \
	public-inbox-index linux-arm-kernel

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox