linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>
Cc: Gottfried Haider <gottfried.haider@gmail.com>,
	devicetree@vger.kernel.org,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Phil Elwell <phil@raspberrypi.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Peter Robinson <pbrobinson@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH 6/6] ARM: dts: bcm283x: Add missing GPIO line names
Date: Mon, 21 Jan 2019 12:27:23 -0800	[thread overview]
Message-ID: <871s554uz8.fsf@anholt.net> (raw)
In-Reply-To: <1547297008-2740-7-git-send-email-stefan.wahren@i2se.com>


[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]

Stefan Wahren <stefan.wahren@i2se.com> writes:

> The GPIO sysfs is deprecated and disabled in the defconfig files.
> So in order to motivate the usage of the new GPIO character device API
> add the missing GPIO line names for Raspberry Pi 2 and 3. In the lack
> of full schematics i would leave all undocumented pins as unnamed.

I didn't cross-check the GPIOs against schematics this time, but I trust
your attention to detail on this.

Series is:

Reviewed-by: Eric Anholt <eric@anholt.net>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-01-21 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 12:43 [PATCH 0/6] ARM: dts: bcm283x: Several DTS improvements Stefan Wahren
2019-01-12 12:43 ` [PATCH 1/6] ARM: dts: bcm283x: Fix DTC warning for memory node Stefan Wahren
2019-01-21  4:59   ` Peter Robinson
2019-01-12 12:43 ` [PATCH 2/6] ARM: dts: bcm2835-rpi: Drop unnecessary #address-cells/#size-cells Stefan Wahren
2019-01-12 12:43 ` [PATCH 3/6] ARM: dts: bcm2835: Fix labels for GPIO 0,1 Stefan Wahren
2019-01-12 12:43 ` [PATCH 4/6] ARM: dts: bcm2837-rpi-3-b: Use consistent label for HDMI hotplug Stefan Wahren
2019-01-21  5:02   ` Peter Robinson
2019-01-12 12:43 ` [PATCH 5/6] ARM: dts: bcm2837-rpi-3-b-plus: Clarify label for STATUS_LED Stefan Wahren
2019-01-21  5:00   ` Peter Robinson
2019-01-12 12:43 ` [PATCH 6/6] ARM: dts: bcm283x: Add missing GPIO line names Stefan Wahren
2019-01-21  4:52   ` Peter Robinson
2019-01-21 20:27   ` Eric Anholt [this message]
2019-01-22  7:57 ` [PATCH 0/6] ARM: dts: bcm283x: Several DTS improvements Stefan Wahren

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=871s554uz8.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gottfried.haider@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pbrobinson@gmail.com \
    --cc=phil@raspberrypi.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.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).