From: Chris Brandt <chris.brandt@renesas.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: jacopo mondi <jacopo@jmondi.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Chris Brandt <chris.brandt@renesas.com>
Subject: [PATCH v6 0/2] pinctrl: Add RZ/A2 pin and gpio driver
Date: Thu, 15 Nov 2018 09:00:43 -0500 [thread overview]
Message-ID: <20181115140045.24733-1-chris.brandt@renesas.com> (raw)
The pin controller in the RZ/A2 is nothing like the pin controller in
the RZ/A1. That's a good thing! This pin controller is much more simple
and easier to configure.
So, this driver is faily simple (I hope).
Chris Brandt (2):
pinctrl: Add RZ/A2 pin and gpio controller
dt-bindings: pinctrl: Add RZ/A2 pinctrl and GPIO
.../bindings/pinctrl/renesas,rza2-pinctrl.txt | 87 ++++
drivers/pinctrl/Kconfig | 11 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/pinctrl-rza2.c | 518 +++++++++++++++++++++
include/dt-bindings/pinctrl/r7s9210-pinctrl.h | 47 ++
5 files changed, 664 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rza2-pinctrl.txt
create mode 100644 drivers/pinctrl/pinctrl-rza2.c
create mode 100644 include/dt-bindings/pinctrl/r7s9210-pinctrl.h
--
2.16.1
next reply other threads:[~2018-11-15 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 14:00 Chris Brandt [this message]
2018-11-15 14:00 ` [PATCH v6 1/2] pinctrl: Add RZ/A2 pin and gpio controller Chris Brandt
2018-11-15 16:28 ` jacopo mondi
2018-11-15 16:50 ` Chris Brandt
2018-11-16 9:05 ` Geert Uytterhoeven
2018-11-16 16:00 ` Chris Brandt
2018-11-15 14:00 ` [PATCH v6 2/2] dt-bindings: pinctrl: Add RZ/A2 pinctrl and GPIO Chris Brandt
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=20181115140045.24733-1-chris.brandt@renesas.com \
--to=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo@jmondi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.