From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH 0/3] pinctrl: sun8i: Add support for A83T R_PIO
Date: Mon, 5 Jun 2017 15:51:28 +0200 [thread overview]
Message-ID: <20170605135128.cjease7t25kjc6lp@flea.lan> (raw)
In-Reply-To: <20170603144427.22855-1-wens@csie.org>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Sat, Jun 03, 2017 at 10:44:24PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> This series adds support for the R_PIO pin controller on the A83T.
> The pins managed this controller are mainly used for communicating
> with the PMIC and codec, and various GPIOs for enabling power switches
> for USB ports and WiFi.
>
> Patch 1 updates the sunxi pinctrl bindings.
>
> Patch 2 adds the pinctrl driver.
>
> Patch 3 adds a device node for the pin controller.
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-06-05 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 14:44 Chen-Yu Tsai
2017-06-03 14:44 ` [PATCH 1/3] dt-bindings: pinctrl: sunxi: Add compatible string " Chen-Yu Tsai
2017-06-08 22:22 ` Rob Herring
2017-06-09 9:19 ` Linus Walleij
2017-06-03 14:44 ` [PATCH 2/3] pinctrl: sunxi: Add support " Chen-Yu Tsai
2017-06-09 9:21 ` Linus Walleij
2017-06-03 14:44 ` [PATCH 3/3] ARM: sun8i: a83t: Add device node for R_PIO Chen-Yu Tsai
2017-06-09 9:22 ` Linus Walleij
2017-06-05 13:51 ` Maxime Ripard [this message]
2017-06-09 12:24 ` [PATCH 0/3] pinctrl: sun8i: Add support for A83T R_PIO Chen-Yu Tsai
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=20170605135128.cjease7t25kjc6lp@flea.lan \
--to=maxime.ripard@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=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®