From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/4] ARM: shmobile: Document and identify RZ/G1H and RZ/G1N
Date: Fri, 10 Mar 2017 14:48:26 +0100 [thread overview]
Message-ID: <1489153710-8159-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus,
Now the part numbers of the Renesas RZ/G1H and RZ/G1N are publicly
available, this patch series documents the DT bindings for these SoCs,
and adds support for identifying them.
Thanks!
Geert Uytterhoeven (4):
ARM: shmobile: Document RZ/G1H SoC DT binding
ARM: shmobile: Document RZ/G1N SoC DT binding
soc: renesas: Identify RZ/G1H
soc: renesas: Identify RZ/G1N
Documentation/devicetree/bindings/arm/shmobile.txt | 4 ++++
drivers/soc/renesas/renesas-soc.c | 16 ++++++++++++++++
2 files changed, 20 insertions(+)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2017-03-10 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 13:48 Geert Uytterhoeven [this message]
2017-03-10 13:48 ` [PATCH 1/4] ARM: shmobile: Document RZ/G1H SoC DT binding Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 2/4] ARM: shmobile: Document RZ/G1N " Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 3/4] soc: renesas: Identify RZ/G1H Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 4/4] soc: renesas: Identify RZ/G1N Geert Uytterhoeven
[not found] ` <1489153710-8159-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-03-13 9:26 ` [PATCH 0/4] ARM: shmobile: Document and identify RZ/G1H and RZ/G1N Simon Horman
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=1489153710-8159-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).