From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/3] arm64: dts: r8a7795: salvator-x: Add support for R-Car H3 ES2.0
Date: Thu, 11 May 2017 16:53:24 +0200 [thread overview]
Message-ID: <20170511145324.GC21895@verge.net.au> (raw)
In-Reply-To: <1494503934-23367-3-git-send-email-geert+renesas@glider.be>
On Thu, May 11, 2017 at 01:58:53PM +0200, Geert Uytterhoeven wrote:
> Split off support for Salvator-X boards with the ES1.x revision of the
> R-Car H3 SoC into a separate file. The main r8a7795-salvator-x.dts file
> now corresponds to Salvator-X with R-Car H3 ES2.0 or later.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v3:
> - Rebase on top of common Salvator-X board support extraction,
>
> v2:
> - Use a separate file for ES1.x instead of for ES2.0, so
> r8a7795-salvator-x.dts always corresponds to the board with the
> latest SoC revision,
> - Add a dash between SoC part number and revision, for compatibility
> with the BSP,
> - Enhance the hardware description from basic support to everything
> already supported on ES1.x.
> ---
> arch/arm64/boot/dts/renesas/Makefile | 1 +
> .../renesas/{r8a7795-salvator-x.dts => r8a7795-es1-salvator-x.dts} | 0
> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 4 ++--
> 3 files changed, 3 insertions(+), 2 deletions(-)
> copy arch/arm64/boot/dts/renesas/{r8a7795-salvator-x.dts => r8a7795-es1-salvator-x.dts} (100%)
>
> diff --git a/arch/arm64/boot/dts/renesas/Makefile b/arch/arm64/boot/dts/renesas/Makefile
> index 1618e0a3c81d48bd..b6c723d8f6875f2d 100644
> --- a/arch/arm64/boot/dts/renesas/Makefile
> +++ b/arch/arm64/boot/dts/renesas/Makefile
> @@ -1,4 +1,5 @@
> dtb-$(CONFIG_ARCH_R8A7795) += r8a7795-salvator-x.dtb r8a7795-h3ulcb.dtb
> +dtb-$(CONFIG_ARCH_R8A7795) += r8a7795-es1-salvator-x.dtb
Probably this was already discussed but I wonder if there is any value
in a CONFIG_ARCH_R8A7795_ES1 Kconfig symbol to allow more fine grained
control over what is compiled into the kernel.
> dtb-$(CONFIG_ARCH_R8A7796) += r8a7796-salvator-x.dtb r8a7796-m3ulcb.dtb
>
> always := $(dtb-y)
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts b/arch/arm64/boot/dts/renesas/r8a7795-es1-salvator-x.dts
> similarity index 100%
> copy from arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> copy to arch/arm64/boot/dts/renesas/r8a7795-es1-salvator-x.dts
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> index be5b2e966ea1700e..fc26909dfa47b61f 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> @@ -11,11 +11,11 @@
> #define CPG_AUDIO_CLK_I R8A7795_CLK_S0D4
>
> /dts-v1/;
> -#include "r8a7795-es1.dtsi"
> +#include "r8a7795.dtsi"
> #include "salvator-x.dtsi"
>
> / {
> - model = "Renesas Salvator-X board based on r8a7795 ES1.x";
> + model = "Renesas Salvator-X board based on r8a7795 ES2.0+";
> compatible = "renesas,salvator-x", "renesas,r8a7795";
>
> memory@48000000 {
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-05-11 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 11:58 [PATCH v3 0/3] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0 Geert Uytterhoeven
2017-05-11 11:58 ` [PATCH v3 1/3] " Geert Uytterhoeven
2017-05-11 14:53 ` Simon Horman
2017-05-11 15:42 ` Geert Uytterhoeven
2017-05-12 7:32 ` Simon Horman
2017-05-12 9:49 ` Geert Uytterhoeven
2017-05-15 5:37 ` Simon Horman
2017-05-11 11:58 ` [PATCH v3 2/3] arm64: dts: r8a7795: salvator-x: " Geert Uytterhoeven
2017-05-11 14:53 ` Simon Horman [this message]
2017-05-11 15:18 ` Geert Uytterhoeven
2017-05-12 7:29 ` Simon Horman
2017-05-11 11:58 ` [PATCH v3 3/3] arm64: dts: r8a7795: h3ulcb: " 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=20170511145324.GC21895@verge.net.au \
--to=horms@verge.net.au \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sjoerd.simons@collabora.co.uk \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).