linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Marvell Armada 375 and 38x pinctrl drivers
Date: Mon, 17 Feb 2014 16:44:06 +0100	[thread overview]
Message-ID: <20140217164406.17d3f59e@skate> (raw)
In-Reply-To: <1392051896-19178-1-git-send-email-thomas.petazzoni@free-electrons.com>

Linus,

Do you intend to integrate the following patches for 3.15 ? They have
been Acked-by Jason Cooper, one of the mvebu maintainer, and are just
additions of simple mvebu pinctrl drivers that follow the existing
mvebu pinctrl common logic with nothing fancy.

We have agreed with Sebastian Hesselbarth, who is doing a more serious
rework of the pinctrl mvebu stuff, that those two patches should go in
first, so that they don't miss 3.15.

Thanks a lot,

Thomas

On Mon, 10 Feb 2014 18:04:54 +0100, Thomas Petazzoni wrote:
> Linus,
> 
> Here are two patches that add the pinctrl drivers for two new Marvell
> ARM SOCs that belong to the mach-mvebu family: the Armada 375 and the
> Armada 380/385. They are based on Cortex-A9 CPU cores, and share a
> number of peripherals with their predecessors in the mach-mvebu
> family. pinctrl-wise, they have a completely similar register layout
> than Armada 370/XP, so only a list of pins and functions has to be
> introduced, and therefore the drivers are straightforward.
> 
> The core support (arch/arm/mach-mvebu) for these SOCs will be posted
> shortly, and we're aiming at having this merged for 3.15 if possible.
> 
> Thanks!
> 
> Thomas
> 
> Thomas Petazzoni (2):
>   pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 375
>   pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 380/385
> 
>  .../pinctrl/marvell,armada-375-pinctrl.txt         |  81 ++++
>  .../pinctrl/marvell,armada-38x-pinctrl.txt         |  79 ++++
>  drivers/pinctrl/mvebu/Kconfig                      |   8 +
>  drivers/pinctrl/mvebu/Makefile                     |   2 +
>  drivers/pinctrl/mvebu/pinctrl-armada-375.c         | 441 ++++++++++++++++++++
>  drivers/pinctrl/mvebu/pinctrl-armada-38x.c         | 445 +++++++++++++++++++++
>  6 files changed, 1056 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-375-pinctrl.txt
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-38x-pinctrl.txt
>  create mode 100644 drivers/pinctrl/mvebu/pinctrl-armada-375.c
>  create mode 100644 drivers/pinctrl/mvebu/pinctrl-armada-38x.c
> 



-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-02-17 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 17:04 [PATCH 0/2] Marvell Armada 375 and 38x pinctrl drivers Thomas Petazzoni
2014-02-10 17:04 ` [PATCH 1/2] pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 375 Thomas Petazzoni
2014-02-24  9:52   ` Linus Walleij
2014-02-10 17:04 ` [PATCH 2/2] pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 380/385 Thomas Petazzoni
2014-02-24  9:53   ` Linus Walleij
2014-02-11 19:04 ` [PATCH 0/2] Marvell Armada 375 and 38x pinctrl drivers Jason Cooper
2014-02-17 15:44 ` Thomas Petazzoni [this message]
2014-02-23 21:10   ` Jason Cooper
2014-02-24 10:25     ` Linus Walleij
2014-02-24 14:59       ` Jason Cooper
2014-02-23 21:17 ` 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=20140217164406.17d3f59e@skate \
    --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).