From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] pinctrl: sunxi: Merge A31s pinctrl driver with A31
Date: Thu, 2 Feb 2017 09:13:32 +0100 [thread overview]
Message-ID: <20170202081332.okjxo4ogm2kp3abh@lukather> (raw)
In-Reply-To: <20170201162547.24232-1-wens@csie.org>
On Thu, Feb 02, 2017 at 12:25:45AM +0800, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This series merges support for the A31s' pin controller into the A31
> driver, using the new sunxi variants support code. The A31s is a trimmed
> down version of the A31, with some hardware blocks removed, and some
> pin functions or pins removed. Thus it is easy to support the A31s
> using the A31 driver by marking the extra pins/functions as A31 only.
>
> Patch 1 does exactly this.
>
> Patch 2 removes the original A31s driver, which is now redundant.
>
> I opted not to rename sun6i-a31 to sun6i in various places.
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170202/b03d71bd/attachment.sig>
next prev parent reply other threads:[~2017-02-02 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 16:25 [PATCH 0/2] pinctrl: sunxi: Merge A31s pinctrl driver with A31 Chen-Yu Tsai
2017-02-01 16:25 ` [PATCH 1/2] pinctrl: sunxi: Support A31/A31s with pinctrl variants Chen-Yu Tsai
2017-02-06 9:57 ` Linus Walleij
2017-02-01 16:25 ` [PATCH 2/2] pinctrl: sunxi: Remove redundant A31s pinctrl driver Chen-Yu Tsai
2017-02-06 9:58 ` Linus Walleij
2017-02-02 8:13 ` Maxime Ripard [this message]
2017-02-06 10:07 ` [PATCH 0/2] pinctrl: sunxi: Merge A31s pinctrl driver with A31 Linus Walleij
2017-02-07 15:04 ` Maxime Ripard
2017-02-07 21:54 ` Linus Walleij
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=20170202081332.okjxo4ogm2kp3abh@lukather \
--to=maxime.ripard@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