From: kraxel@redhat.com (Gerd Hoffmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups in the gpio node.
Date: Thu, 08 Sep 2016 09:48:48 +0200 [thread overview]
Message-ID: <1473320928.6698.28.camel@redhat.com> (raw)
In-Reply-To: <87bmzzr1bg.fsf@eliezer.anholt.net>
On Mi, 2016-09-07 at 11:50 -0700, Eric Anholt wrote:
> 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.
Agreeing here. IMO it is nice to have them all even if unused for
documentation purposes.
> 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.
It'll also easily cause merge conflicts.
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
Cc: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Scott Branden <sbranden-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Ray Jui <rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups in the gpio node.
Date: Thu, 08 Sep 2016 09:48:48 +0200 [thread overview]
Message-ID: <1473320928.6698.28.camel@redhat.com> (raw)
In-Reply-To: <87bmzzr1bg.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
On Mi, 2016-09-07 at 11:50 -0700, Eric Anholt wrote:
> Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org> writes:
>
> > Hi Gerd,
> >
> >> Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> hat am 7. September 2016 um 12:31
> >> geschrieben:
> >>
> >>
> >> From: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
> >>
> >> 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.
Agreeing here. IMO it is nice to have them all even if unused for
documentation purposes.
> 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.
It'll also easily cause merge conflicts.
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Eric Anholt <eric@anholt.net>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
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: Thu, 08 Sep 2016 09:48:48 +0200 [thread overview]
Message-ID: <1473320928.6698.28.camel@redhat.com> (raw)
In-Reply-To: <87bmzzr1bg.fsf@eliezer.anholt.net>
On Mi, 2016-09-07 at 11:50 -0700, Eric Anholt wrote:
> 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.
Agreeing here. IMO it is nice to have them all even if unused for
documentation purposes.
> 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.
It'll also easily cause merge conflicts.
cheers,
Gerd
next prev parent reply other threads:[~2016-09-08 7:48 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 10:31 [PATCH 0/8] ARM: dts: bcm283x: add and use pinctrl groups Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups in the gpio node Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 18:09 ` Stefan Wahren
2016-09-07 18:09 ` Stefan Wahren
2016-09-07 18:09 ` Stefan Wahren
2016-09-07 18:50 ` Eric Anholt
2016-09-07 18:50 ` Eric Anholt
2016-09-08 7:48 ` Gerd Hoffmann [this message]
2016-09-08 7:48 ` Gerd Hoffmann
2016-09-08 7:48 ` Gerd Hoffmann
2016-09-08 17:55 ` Stefan Wahren
2016-09-08 17:55 ` Stefan Wahren
2016-09-08 17:55 ` Stefan Wahren
2016-09-09 9:05 ` Gerd Hoffmann
2016-09-09 9:05 ` Gerd Hoffmann
2016-09-09 9:05 ` Gerd Hoffmann
2016-09-09 14:12 ` Stefan Wahren
2016-09-09 14:12 ` Stefan Wahren
2016-09-09 14:12 ` Stefan Wahren
2016-09-09 21:20 ` Eric Anholt
2016-09-09 21:20 ` Eric Anholt
2016-09-09 21:20 ` Eric Anholt
2016-09-11 21:22 ` Dave Stevenson
2016-09-11 21:22 ` Dave Stevenson
2016-09-13 6:09 ` Eric Anholt
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 ` Gerd Hoffmann
2016-09-07 10:31 ` 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 ` Gerd Hoffmann
2016-09-07 10:31 ` 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 10:31 ` Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 18:13 ` Stefan Wahren
2016-09-07 18:13 ` Stefan Wahren
2016-09-08 7:44 ` Gerd Hoffmann
2016-09-08 7:44 ` Gerd Hoffmann
2016-09-08 12:06 ` Stefan Wahren
2016-09-08 12:06 ` Stefan Wahren
2016-09-09 8:26 ` Gerd Hoffmann
2016-09-09 8:26 ` Gerd Hoffmann
2016-09-09 8:47 ` Gerd Hoffmann
2016-09-09 8:47 ` Gerd Hoffmann
2016-09-09 8:47 ` Gerd Hoffmann
2016-09-08 19:50 ` Scott Branden
2016-09-08 19:50 ` Scott Branden
2016-09-08 19:50 ` Scott Branden
2016-09-09 6:58 ` Stefan Wahren
2016-09-09 6:58 ` Stefan Wahren
2016-09-09 6:58 ` Stefan Wahren
2016-09-09 16:37 ` Scott Branden
2016-09-09 16:37 ` Scott Branden
2016-09-09 16:37 ` Scott Branden
2016-09-09 21:22 ` Eric Anholt
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 ` Gerd Hoffmann
2016-09-07 10:31 ` 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 ` Gerd Hoffmann
2016-09-07 10:31 ` 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 ` Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 10:31 ` [PATCH 8/8] ARM: dts: bcm283x: add pinctrl group to &sdhci, " Gerd Hoffmann
2016-09-07 10:31 ` Gerd Hoffmann
2016-09-07 10:31 ` 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=1473320928.6698.28.camel@redhat.com \
--to=kraxel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.