From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/10] pinctrl: mvebu: add pinctrl driver for Marvell Armada 39x
Date: Wed, 4 Mar 2015 14:05:25 +0100 [thread overview]
Message-ID: <20150304140525.711d1515@free-electrons.com> (raw)
In-Reply-To: <CACRpkdZH9vUPR65Yw65LKHns8_b3vM+1ARoks2j73WV2WmAExQ@mail.gmail.com>
Dear Linus Walleij,
On Wed, 4 Mar 2015 13:54:42 +0100, Linus Walleij wrote:
> On Fri, Feb 6, 2015 at 4:57 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>
> > This commit adds a new pinctrl driver for the Marvell Armada 39x
> > family of processors, which hooks into the existing infrastructure to
> > support pin-muxing on Marvell EBU processors. Two variants of the
> > Armada 39x are supported: 88F6920 (Armada 390) and 88F6928 (Armada
> > 398), which have a few differences in the available functions for
> > certain pins.
> >
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> Patch applied.
I'm surprised you applied the driver of the first iteration of the
patches, and not the v3 I sent just yesterday. Even though if I
remember correctly there were no changes on the pinctrl driver itself.
Also, can you apply:
devicetree: bindings: add Device Tree bindings for Armada 39x pin-muxing controller
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-04 13:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 15:57 [PATCH 00/10] ARM: mvebu: add basic support for Armada 39x Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 01/10] devicetree: bindings: add DT binding for the Marvell Armada 39x SoC family Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 02/10] devicetree: bindings: update DT bindings for Marvell EBU clock support Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 03/10] devicetree: bindings: add Device Tree bindings for Armada 39x pin-muxing controller Thomas Petazzoni
2015-02-06 17:05 ` Andrew Lunn
2015-02-20 11:11 ` Thomas Petazzoni
2015-02-20 14:18 ` Andrew Lunn
2015-02-06 15:57 ` [PATCH 04/10] devicetree: bindings: add new SMP enable method for Marvell Armada 39x Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 05/10] clk: mvebu: extend common code to allow an optional refclk Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 06/10] clk: mvebu: add Marvell Armada 39x driver Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 07/10] pinctrl: mvebu: add pinctrl driver for Marvell Armada 39x Thomas Petazzoni
2015-03-04 12:54 ` Linus Walleij
2015-03-04 13:05 ` Thomas Petazzoni [this message]
2015-02-06 15:57 ` [PATCH 08/10] ARM: mvebu: add core support for " Thomas Petazzoni
2015-02-06 19:57 ` Stephen Boyd
2015-02-20 13:05 ` Thomas Petazzoni
2015-02-06 20:31 ` Maxime Ripard
2015-02-06 15:57 ` [PATCH 09/10] ARM: mvebu: add Device Tree files for Armada 39x SoC and board Thomas Petazzoni
2015-02-06 17:21 ` Andrew Lunn
2015-02-20 14:14 ` Thomas Petazzoni
2015-02-20 14:45 ` Andrew Lunn
2015-02-20 15:46 ` Thomas Petazzoni
2015-02-06 20:39 ` Maxime Ripard
2015-02-06 15:57 ` [PATCH 10/10] Documentation: arm: update supported Marvell EBU processors Thomas Petazzoni
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=20150304140525.711d1515@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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).