From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] New Atmel PIO4 pinctrl/gpio driver
Date: Wed, 23 Sep 2015 16:46:31 +0200 [thread overview]
Message-ID: <5602BB47.4040401@atmel.com> (raw)
In-Reply-To: <CACRpkdYLbifY9VJK0FFf7xXdMJWstdGP=h5ApBMRyRXZHPDUaw@mail.gmail.com>
Le 21/09/2015 20:50, Linus Walleij a écrit :
> On Wed, Sep 16, 2015 at 8:36 AM, Ludovic Desroches
> <ludovic.desroches@atmel.com> wrote:
>
>> The Atmel PIO4 controller has been introduced with SAMA5D2 chip family. This
>> drivers manages both pinmux/pinconf and gpio stuff. It is inspired by Mediatek
>> pinctrl driver.
>>
>> Changes from v1:
>> - remove some unneeded gpio specific ops (gpio_request, gpio_free,
>> gpio_request_enable, gpio_disable_free and gpio_set_direction).
>> - code styling fixes.
>> - add sama5d2 pin description and device pin muxing.
>
> Looks Good To Me, and has Sascha's ACKs, so merged patches
> 1, 2, 3, 4 to the pinctrl tree. Please merge the AT91 DT things into
> the AT91 tree.
Great!
So patch 5 is included in at91-4.4-defconfig branch.
patches 6 and 7 queued in at91-4.4-dt branch.
They are included in at91-next that is merged in linux-next and will
both take the arm-soc path later in the cycle.
Thanks, bye,
--
Nicolas Ferre
prev parent reply other threads:[~2015-09-23 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 15:36 [PATCH v2 0/7] New Atmel PIO4 pinctrl/gpio driver Ludovic Desroches
2015-09-16 15:36 ` [PATCH v2 1/7] pinctrl: introduce driver for Atmel PIO4 controller Ludovic Desroches
2015-09-21 18:22 ` Linus Walleij
2015-09-16 15:36 ` [PATCH v2 2/7] pinctrl: dt-binding: Add DT binding documentation for Atmel PIO4 Ludovic Desroches
2015-09-16 15:36 ` [PATCH v2 3/7] MAINTAINERS: Add an entry for pinctrl-at91-pio4 Ludovic Desroches
2015-09-21 18:24 ` Linus Walleij
2015-09-16 15:37 ` [PATCH v2 4/7] ARM: at91/dt: sama5d2: add pio controller node Ludovic Desroches
2015-09-21 18:24 ` Linus Walleij
2015-11-10 0:30 ` Olof Johansson
2015-11-17 11:06 ` Linus Walleij
2015-11-17 19:15 ` Olof Johansson
2015-11-18 7:25 ` Ludovic Desroches
2015-09-16 15:37 ` [PATCH v2 5/7] ARM: at91/defconfig: sama5: add PIO4 controller support Ludovic Desroches
2015-09-21 18:25 ` Linus Walleij
2015-09-23 14:44 ` Nicolas Ferre
2015-09-16 15:37 ` [PATCH v2 6/7] ARM: at91/dt: add sama5d2 pinmux Ludovic Desroches
2015-09-21 18:27 ` Linus Walleij
2015-09-16 15:37 ` [PATCH v2 7/7] ARM: at91/dt: sama5d2 Xplained: add device pin muxing Ludovic Desroches
2015-09-21 18:29 ` Linus Walleij
2015-09-21 18:50 ` [PATCH v2 0/7] New Atmel PIO4 pinctrl/gpio driver Linus Walleij
2015-09-23 14:46 ` Nicolas Ferre [this message]
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=5602BB47.4040401@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=s.hauer@pengutronix.de \
/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