From: Chris Brandt <chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
To: Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Geert Uytterhoeven
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
Cc: linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Simon Horman
<horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Jacopo Mondi
<jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>,
Chris Brandt
<chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
Subject: [PATCH 0/2] pinctrl: rza1: add support for RZ/A1L
Date: Tue, 3 Oct 2017 02:33:32 -0500 [thread overview]
Message-ID: <20171003073334.18917-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.
Chris Brandt (2):
pinctrl: rza1: add support for RZ/A1L
dt-bindings: pinctrl: add support for RZ/A1L
.../bindings/pinctrl/renesas,rza1-pinctrl.txt | 3 +-
drivers/pinctrl/pinctrl-rza1.c | 134 +++++++++++++++++++++
2 files changed, 136 insertions(+), 1 deletion(-)
--
2.14.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-10-03 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 7:33 Chris Brandt [this message]
2017-10-03 7:33 ` [PATCH 1/2] pinctrl: rza1: add support for RZ/A1L Chris Brandt
2017-10-03 8:31 ` jacopo mondi
2017-10-03 13:36 ` Chris Brandt
2017-10-03 15:04 ` jacopo mondi
2017-10-03 15:40 ` Chris Brandt
2017-10-03 16:17 ` jacopo mondi
[not found] ` <20171003073334.18917-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-10-03 7:33 ` [PATCH 2/2] dt-bindings: pinctrl: " Chris Brandt
[not found] ` <20171003073334.18917-3-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-10-04 13:58 ` Geert Uytterhoeven
2017-10-04 14:16 ` Chris Brandt
2017-10-04 14:27 ` Geert Uytterhoeven
2017-10-04 14:43 ` Chris Brandt
2017-10-04 14:49 ` Geert Uytterhoeven
2017-10-04 14:57 ` 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=20171003073334.18917-1-chris.brandt@renesas.com \
--to=chris.brandt-zm6kxycvzfbbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
--cc=horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).