From: nobuhiro1.iwamatsu@toshiba.co.jp (nobuhiro1.iwamatsu at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.19.y-cip 0/5] Add HopeRun RZ/G2[M] main/sub boards
Date: Mon, 2 Sep 2019 05:22:32 +0000 [thread overview]
Message-ID: <OSAPR01MB3234F017F51F5BE39407601392BE0@OSAPR01MB3234.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1567150318-36833-1-git-send-email-biju.das@bp.renesas.com>
Hi Biju,
> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Biju Das
> Sent: Friday, August 30, 2019 4:32 PM
> To: cip-dev at lists.cip-project.org
> Cc: Biju Das <biju.das@bp.renesas.com>
> Subject: [cip-dev] [PATCH 4.19.y-cip 0/5] Add HopeRun RZ/G2[M] main/sub
> boards
>
> This patch series add support for HopeRun RZ/G2[M] main/sub boards.
>
> This patch series is based on linux-4.19.y-cip and all the patches in
> this series are cherry-picked from linux rc tree.
>
> This patch series depend upon
> https://patchwork.kernel.org/project/cip-dev/list/?series=166545
>
>
> Biju Das (5):
> dt-bindings: arm: renesas: Add HopeRun RZ/G2[M] boards
> dt-bindings: Add vendor prefix for HopeRun
> arm64: dts: renesas: Add HiHope RZ/G2M main board support
> arm64: dts: renesas: hihope-common: Add pincontrol support to
> scif2/scif clock
> arm64: dts: renesas: Add HiHope RZ/G2M sub board support
Applied to my local repo on series of "Add basic RZ/G2M SoC support".
Best regards,
Nobuhiro
>
> Documentation/devicetree/bindings/arm/shmobile.txt | 5 ++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm64/boot/dts/renesas/Makefile | 2 +
> arch/arm64/boot/dts/renesas/hihope-common.dtsi | 53
> +++++++++++++++++++++
> arch/arm64/boot/dts/renesas/hihope-rzg2-ex.dtsi | 55
> ++++++++++++++++++++++
> .../boot/dts/renesas/r8a774a1-hihope-rzg2m-ex.dts | 15 ++++++
> .../boot/dts/renesas/r8a774a1-hihope-rzg2m.dts | 26 ++++++++++
> 7 files changed, 157 insertions(+)
> create mode 100644 arch/arm64/boot/dts/renesas/hihope-common.dtsi
> create mode 100644 arch/arm64/boot/dts/renesas/hihope-rzg2-ex.dtsi
> create mode 100644
> arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m-ex.dts
> create mode 100644
> arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m.dts
>
> --
> 2.7.4
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
prev parent reply other threads:[~2019-09-02 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 7:31 [cip-dev] [PATCH 4.19.y-cip 0/5] Add HopeRun RZ/G2[M] main/sub boards Biju Das
2019-08-30 7:31 ` [cip-dev] [PATCH 4.19.y-cip 1/5] dt-bindings: arm: renesas: Add HopeRun RZ/G2[M] boards Biju Das
2019-08-30 7:31 ` [cip-dev] [PATCH 4.19.y-cip 2/5] dt-bindings: Add vendor prefix for HopeRun Biju Das
2019-08-30 7:31 ` [cip-dev] [PATCH 4.19.y-cip 3/5] arm64: dts: renesas: Add HiHope RZ/G2M main board support Biju Das
2019-08-30 7:31 ` [cip-dev] [PATCH 4.19.y-cip 4/5] arm64: dts: renesas: hihope-common: Add pincontrol support to scif2/scif clock Biju Das
2019-08-30 7:31 ` [cip-dev] [PATCH 4.19.y-cip 5/5] arm64: dts: renesas: Add HiHope RZ/G2M sub board support Biju Das
2019-09-02 5:22 ` nobuhiro1.iwamatsu at toshiba.co.jp [this message]
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=OSAPR01MB3234F017F51F5BE39407601392BE0@OSAPR01MB3234.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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.