From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
<Steen.Hegelund@microchip.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>
Subject: [PATCH 0/4] Extend pinctrl ocelot driver to support other SoCs
Date: Fri, 6 Nov 2020 10:31:14 +0100 [thread overview]
Message-ID: <20201106093118.965152-1-gregory.clement@bootlin.com> (raw)
Hello,
Ocelot SoC belongs to a larger family of SoCs which use the same
interrupt controller with a few variation.
This series of patches add support for Luton and Serval, they are all
MIPS based.
The first patches of the series also updates the binding documentation
with the new compatible strings.
Gregory
Gregory CLEMENT (2):
dt-bindings: pinctrl: ocelot: Add Luton SoC support
dt-bindings: pinctrl: ocelot: Add Serval SoC support
Lars Povlsen (2):
pinctrl: ocelot: Add support for Luton platforms
pinctrl: ocelot: Add support for Serval platforms
.../bindings/pinctrl/mscc,ocelot-pinctrl.txt | 3 +-
drivers/pinctrl/pinctrl-ocelot.c | 184 ++++++++++++++++++
2 files changed, 186 insertions(+), 1 deletion(-)
--
2.28.0
next reply other threads:[~2020-11-06 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 9:31 Gregory CLEMENT [this message]
2020-11-06 9:31 ` [PATCH 1/4] dt-bindings: pinctrl: ocelot: Add Luton SoC support Gregory CLEMENT
2020-11-06 9:31 ` [PATCH 2/4] dt-bindings: pinctrl: ocelot: Add Serval " Gregory CLEMENT
2020-11-06 9:31 ` [PATCH 3/4] pinctrl: ocelot: Add support for Luton platforms Gregory CLEMENT
2020-11-06 9:31 ` [PATCH 4/4] pinctrl: ocelot: Add support for Serval platforms Gregory CLEMENT
2020-11-10 14:11 ` [PATCH 0/4] Extend pinctrl ocelot driver to support other SoCs 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=20201106093118.965152-1-gregory.clement@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=Steen.Hegelund@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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).