From: Biju Das <biju.das@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Biju Das <biju.das@bp.renesas.com>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: [PATCH 0/4] Add HiHope RZ/G2N main board support
Date: Tue, 17 Sep 2019 14:05:26 +0100 [thread overview]
Message-ID: <1568725530-55241-1-git-send-email-biju.das@bp.renesas.com> (raw)
This patch series add basic support for the HiHope RZ/G2N main board
Biju Das (4):
arm64: dts: renesas: Initial r8a774b1 SoC device tree
arm64: defconfig: enable R8A774B1 SoC
arm64: renesas_defconfig: enable R8A774B1 SoC
arm64: dts: renesas: Add HiHope RZ/G2N main board support
arch/arm64/boot/dts/renesas/Makefile | 1 +
.../boot/dts/renesas/r8a774b1-hihope-rzg2n.dts | 26 ++
arch/arm64/boot/dts/renesas/r8a774b1.dtsi | 472 +++++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
arch/arm64/configs/renesas_defconfig | 1 +
5 files changed, 501 insertions(+)
create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1-hihope-rzg2n.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a774b1.dtsi
--
2.7.4
next reply other threads:[~2019-09-17 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:05 Biju Das [this message]
2019-09-17 13:05 ` [PATCH 1/4] arm64: dts: renesas: Initial r8a774b1 SoC device tree Biju Das
2019-09-27 12:06 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 2/4] arm64: defconfig: enable R8A774B1 SoC Biju Das
2019-09-27 11:32 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 3/4] arm64: renesas_defconfig: " Biju Das
2019-09-27 11:38 ` Geert Uytterhoeven
2019-09-17 13:05 ` [PATCH 4/4] arm64: dts: renesas: Add HiHope RZ/G2N main board support Biju Das
2019-09-27 12:38 ` Geert Uytterhoeven
2019-09-27 12:56 ` Biju Das
2019-09-27 13:41 ` 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=1568725530-55241-1-git-send-email-biju.das@bp.renesas.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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 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).