From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Gerd Hoffmann <kraxel@redhat.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>, Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com, swarren@wwwdotorg.org,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups in the gpio node.
Date: Wed, 07 Sep 2016 11:50:59 -0700 [thread overview]
Message-ID: <87bmzzr1bg.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1564766913.23457.026b1e4b-e35d-48e6-9394-7eeea0ff9add.open-xchange@email.1und1.de>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Stefan Wahren <stefan.wahren@i2se.com> writes:
> Hi Gerd,
>
>> Gerd Hoffmann <kraxel@redhat.com> hat am 7. September 2016 um 12:31
>> geschrieben:
>>
>>
>> From: Eric Anholt <eric@anholt.net>
>>
>> The BCM2835-ARM-Peripherals.pdf documentation specifies what the
>> function selects do for the pins, and there are a bunch of obvious
>> groupings to be made. With these created, we'll be able to replace
>> bcm2835-rpi.dtsi's main "set all of these pins to alt0" with
>> references to specific groups we want enabled.
>
> on IMX/MXS platform it's unwanted to add all possible muxes in the dtsi file. So
> i would suggest to add only the actually used muxes. That makes it easier to
> maintain.
On the other hand, I find that having to go back to the docs for
determining the fsels is worse than just verifying and defining them
here all at once. Maintaining has also gotten harder because our DTs
are split across 32 and 64-bit ARM, so rpi3 changes that require adding
one of these pinmux definitions back to the dtsi would require painful
cross-branch merges.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-09-07 18:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1473244289-20728-1-git-send-email-kraxel@redhat.com>
2016-09-07 10:31 ` [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups in the gpio node Gerd Hoffmann
2016-09-07 18:09 ` Stefan Wahren
2016-09-07 18:50 ` Eric Anholt [this message]
2016-09-08 7:48 ` Gerd Hoffmann
2016-09-08 17:55 ` Stefan Wahren
2016-09-09 9:05 ` Gerd Hoffmann
2016-09-09 14:12 ` Stefan Wahren
2016-09-09 21:20 ` Eric Anholt
2016-09-11 21:22 ` Dave Stevenson
2016-09-13 6:09 ` Eric Anholt
2016-09-07 10:31 ` [PATCH 2/8] ARM: dts: bcm283x: Add the emmc pin group to bcm283x.dtsi Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 3/8] ARM: dts: bcm283x: Add a group for mapping pins 48-53 to sdhost Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 4/8] ARM: dts: bcm283x: Add a new EMMC pin group from the downstream tree Gerd Hoffmann
2016-09-07 18:13 ` Stefan Wahren
2016-09-08 7:44 ` Gerd Hoffmann
2016-09-08 12:06 ` Stefan Wahren
2016-09-09 8:26 ` Gerd Hoffmann
2016-09-09 8:47 ` Gerd Hoffmann
2016-09-08 19:50 ` Scott Branden
2016-09-09 6:58 ` Stefan Wahren
2016-09-09 16:37 ` Scott Branden
2016-09-09 21:22 ` Eric Anholt
2016-09-07 10:31 ` [PATCH 5/8] ARM: dts: bcm283x: add pinctrl group to &pwm, drop pins from &gpio Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 6/8] ARM: dts: bcm283x: add pinctrl group to &i2c0, " Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 7/8] ARM: dts: bcm283x: add pinctrl group to &i2c1, " Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 8/8] ARM: dts: bcm283x: add pinctrl group to &sdhci, " Gerd Hoffmann
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=87bmzzr1bg.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.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).