From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC
Date: Thu, 22 Dec 2016 16:48:35 -0600 [thread overview]
Message-ID: <20161222224835.xoillysatrjvdspr@rob-hp-laptop> (raw)
In-Reply-To: <20161222041328.3303-4-chris.packham@alliedtelesis.co.nz>
On Thu, Dec 22, 2016 at 05:13:26PM +1300, Chris Packham wrote:
> From: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
>
> This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs
> from Marvell.
>
> Signed-off-by: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> .../pinctrl/marvell,armada-98dx3236-pinctrl.txt | 46 +++++++
Acked-by: Rob Herring <robh@kernel.org>
> drivers/pinctrl/mvebu/pinctrl-armada-xp.c | 145 +++++++++++++++++++++
> 2 files changed, 191 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/marvell,armada-98dx3236-pinctrl.txt
next prev parent reply other threads:[~2016-12-22 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 4:13 [PATCH 0/5] Support for Marvell switches with integrated CPUs Chris Packham
2016-12-22 4:13 ` [PATCH 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-04 17:32 ` Gregory CLEMENT
2016-12-22 4:13 ` [PATCH 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2016-12-22 22:47 ` Rob Herring
2016-12-22 4:13 ` [PATCH 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2016-12-22 22:48 ` Rob Herring [this message]
2016-12-30 9:03 ` Linus Walleij
2016-12-22 4:13 ` [PATCH 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2016-12-22 22:53 ` Rob Herring
2016-12-22 4:13 ` [PATCH 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
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=20161222224835.xoillysatrjvdspr@rob-hp-laptop \
--to=robh@kernel.org \
--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