From: simon.guinot@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: convert ns2 boards to pinctrl
Date: Tue, 8 Jan 2013 16:09:07 +0100 [thread overview]
Message-ID: <20130108150907.GM1357@kw.sim.vm.gnt> (raw)
In-Reply-To: <20130108144954.GC3392@lunn.ch>
On Tue, Jan 08, 2013 at 03:49:54PM +0100, Andrew Lunn wrote:
> On Tue, Jan 08, 2013 at 03:36:18PM +0100, Simon Guinot wrote:
> > Note that the pinctrl conversion also fixes GPIO support for ns2 boards.
> > Since commit f9e75922: "ARM: Kirkwood: Make use of mvebu pincltl and
> > gpio", the mvbu_gpio driver is used for DT boards. As mvbu_gpio relies
> > on the pinctrl driver, then a pinctrl definition must be given to allow
> > the GPIO configuration.
> >
> > Signed-off-by: Simon Guinot <simon.guinot@sequanux.org>
> > ---
> > arch/arm/boot/dts/kirkwood-ns2-common.dtsi | 16 ++++++++++++
> > arch/arm/mach-kirkwood/board-ns2.c | 38 ----------------------------
> > 2 files changed, 16 insertions(+), 38 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/kirkwood-ns2-common.dtsi b/arch/arm/boot/dts/kirkwood-ns2-common.dtsi
> > index 9bc6785..77d21ab 100644
> > --- a/arch/arm/boot/dts/kirkwood-ns2-common.dtsi
> > +++ b/arch/arm/boot/dts/kirkwood-ns2-common.dtsi
> > @@ -1,4 +1,5 @@
> > /include/ "kirkwood.dtsi"
> > +/include/ "kirkwood-6281.dtsi"
> >
> > / {
> > chosen {
> > @@ -6,6 +7,21 @@
> > };
> >
> > ocp at f1000000 {
> > + pinctrl: pinctrl at 10000 {
> > + pinctrl-0 = < &pmx_spi &pmx_twsi0 &pmx_uart0
> > + &pmx_ns2_sata0 &pmx_ns2_sata1>;
> > + pinctrl-names = "default";
> > +
> > + pmx_ns2_sata0: pmx-ns2-sata0 {
> > + marvell,pins = "mpp21";
> > + marvell,function = "sata0";
> > + };
> > + pmx_ns2_sata1: pmx-ns2-sata1 {
> > + marvell,pins = "mpp20";
> > + marvell,function = "sata1";
> > + };
> > + };
>
> Hi Simon
>
> Its normal to also list all the gpio pins here as well.
I was not sure about that. As gpio_request triggers the mpp
configuration at run time, IMHO there is no point for an initial and
statical configuration, except for a documentation purpose. As GPIOs
are also referenced in their dedicated driver nodes, I think that the
informations about the pin are quite exhaustive. All the non-GPIO MPPs
are listed in the pinctrl node. The other MPPs are GPIOs if requested
by a driver. It is simple :)
Do you think that the full MPP/GPIO list is really needed ?
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130108/5c06e391/attachment-0001.sig>
next prev parent reply other threads:[~2013-01-08 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 14:36 [PATCH] ARM: Kirkwood: convert ns2 boards to pinctrl Simon Guinot
2013-01-08 14:49 ` Andrew Lunn
2013-01-08 15:09 ` Simon Guinot [this message]
2013-01-08 16:13 ` Andrew Lunn
2013-01-08 16:21 ` Thomas Petazzoni
2013-01-08 16:15 ` Andrew Lunn
2013-01-08 16:18 ` Simon Guinot
2013-01-08 16:30 ` Andrew Lunn
2013-01-08 16:39 ` Jason Cooper
2013-01-08 16:55 ` Simon Guinot
2013-01-08 17:07 ` Jason Cooper
2013-01-08 17:51 ` Simon Guinot
2013-01-10 1:32 ` Jason Cooper
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=20130108150907.GM1357@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox