[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1564766913.23457.026b1e4b-e35d-48e6-9394-7eeea0ff9add.open-xchange@email.1und1.de>
Date: Wed, 7 Sep 2016 20:09:20 +0200 (CEST)
From: Stefan Wahren <stefan.wahren@...e.com>
To: Gerd Hoffmann <kraxel@...hat.com>,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Cc: Scott Branden <sbranden@...adcom.com>, Ray Jui <rjui@...adcom.com>,
Russell King <linux@...linux.org.uk>, eric@...olt.net,
open list <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
bcm-kernel-feedback-list@...adcom.com, swarren@...dotorg.org,
Mark Rutland <mark.rutland@....com>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH 1/8] ARM: dts: bcm283x: Define standard pinctrl groups
in the gpio node.
Hi Gerd,
> Gerd Hoffmann <kraxel@...hat.com> hat am 7. September 2016 um 12:31
> geschrieben:
>
>
> From: Eric Anholt <eric@...olt.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.
Regards
Stefan
Powered by blists - more mailing lists