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: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Simon Horman <horms+renesas@verge.net.au>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Chris Brandt <chris.brandt@renesas.com>
Subject: [PATCH v2 0/2] pinctrl: rza1: add support for RZ/A1L
Date: Wed, 4 Oct 2017 11:31:09 -0500 [thread overview]
Message-ID: <20171004163111.54600-1-chris.brandt@renesas.com> (raw)
The RZ/A series has 3 main device: RZ/A1L, RZ/A1M, RZ/A1H.
In terms of pinctrl, RZ/A1H and RZ/A1M are exactly the same.
Aspects like the number of ports and the location where peripherals are
brought out differ between the RZ/A1H and RZ/A1L.
Basically this series adds a new set of tables for RZ/A1L and a new
compatible "renesas,r7s72102-ports"
This was tested on a Renesas Stream it board which contains an RZ/A1L and
external SDRAM.
v2:
* Added RZ/A1M to DT documentation
* Added Reviewed-by for pinctrl-rza1.c
Chris Brandt (2):
pinctrl: rza1: add support for RZ/A1L
dt-bindings: pinctrl: add support for RZ/A1M and RZ/A1L
.../bindings/pinctrl/renesas,rza1-pinctrl.txt | 4 +-
drivers/pinctrl/pinctrl-rza1.c | 134 +++++++++++++++++++++
2 files changed, 137 insertions(+), 1 deletion(-)
--
2.14.1
next reply other threads:[~2017-10-04 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:31 Chris Brandt [this message]
2017-10-04 16:31 ` [PATCH v2 1/2] pinctrl: rza1: add support for RZ/A1L Chris Brandt
2017-10-04 16:31 ` [PATCH v2 2/2] dt-bindings: pinctrl: add support for RZ/A1M and RZ/A1L Chris Brandt
[not found] ` <20171004163111.54600-3-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-10-04 16:47 ` Geert Uytterhoeven
2017-10-04 16:47 ` Geert Uytterhoeven
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=20171004163111.54600-1-chris.brandt@renesas.com \
--to=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=jacopo+renesas@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.