From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/5] dt-bindings: arm: renesas: Add core r8a77961 support
Date: Wed, 23 Oct 2019 14:29:06 +0200 [thread overview]
Message-ID: <20191023122911.12166-1-geert+renesas@glider.be> (raw)
Hi all,
This patch series updates the Renesas DT binding documentation for core
components on the new R-Car M3-W+ (R8A77961) SoC, and for the
Salvator-XS development board equipped with this SoC.
Changes compared to v1[1]:
- Split in per-subsystem series,
- Add Reviewed-by,
- Add board part number.
I intend to queue this series in renesas-devel for v5.5.
The last patch will be put on a branch shared between driver and DTS.
Thanks for your comments!
[1] "[PATCH/RFC 00/19] arm64: dts: renesas: Initial support for R-Car M3-W+"
https://lore.kernel.org/linux-renesas-soc/20191007102332.12196-1-geert+renesas@glider.be/
Geert Uytterhoeven (5):
dt-bindings: arm: renesas: Document R-Car M3-W+ SoC DT bindings
dt-bindings: arm: renesas: Add Salvator-XS board with R-Car M3-W+
dt-bindings: reset: rcar-rst: Document r8a77961 support
dt-bindings: power: rcar-sysc: Document r8a77961 support
dt-bindings: power: Add r8a77961 SYSC power domain definitions
.../devicetree/bindings/arm/renesas.yaml | 6 ++++
.../bindings/power/renesas,rcar-sysc.txt | 1 +
.../devicetree/bindings/reset/renesas,rst.txt | 1 +
include/dt-bindings/power/r8a77961-sysc.h | 32 +++++++++++++++++++
4 files changed, 40 insertions(+)
create mode 100644 include/dt-bindings/power/r8a77961-sysc.h
--
2.17.1
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:[~2019-10-23 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 12:29 Geert Uytterhoeven [this message]
2019-10-23 12:29 ` [PATCH v2 1/5] dt-bindings: arm: renesas: Document R-Car M3-W+ SoC DT bindings Geert Uytterhoeven
2019-10-26 0:17 ` Rob Herring
2019-10-23 12:29 ` [PATCH v2 2/5] dt-bindings: arm: renesas: Add Salvator-XS board with R-Car M3-W+ Geert Uytterhoeven
2019-10-26 0:17 ` Rob Herring
2019-10-23 12:29 ` [PATCH v2 3/5] dt-bindings: reset: rcar-rst: Document r8a77961 support Geert Uytterhoeven
2019-10-24 7:59 ` Philipp Zabel
2019-10-26 0:17 ` Rob Herring
2019-10-23 12:29 ` [PATCH v2 4/5] dt-bindings: power: rcar-sysc: " Geert Uytterhoeven
2019-10-26 0:18 ` Rob Herring
2019-10-23 12:29 ` [PATCH v2 5/5] dt-bindings: power: Add r8a77961 SYSC power domain definitions Geert Uytterhoeven
2019-10-26 0:18 ` Rob Herring
2019-10-25 15:49 ` [PATCH v2 0/5] dt-bindings: arm: renesas: Add core r8a77961 support Eugeniu Rosca
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=20191023122911.12166-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--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 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).