From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Wolfram Sang <wsa@sang-engineering.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC v2 0/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0
Date: Thu, 30 Mar 2017 12:48:18 +0200 [thread overview]
Message-ID: <1490870898.3471.3.camel@collabora.co.uk> (raw)
In-Reply-To: <1490362665-4422-1-git-send-email-geert+renesas@glider.be>
On Fri, 2017-03-24 at 14:37 +0100, Geert Uytterhoeven wrote:
> Hi all,
>
> This patch series adds preliminary support for Renesas Salvator-X
> development boards equipped with revision ES2.0 of the R-Car H3 Soc.
>
> - Patch 1 adds support for the R-Car H3 ES2.0 Soc,
> While this patch is safe as-is, as it doesn't affect any existing
> setups, it's probably a bit premature to apply it.
> - Patch 2 adds support for Salvator-X boards with R-Car H3 ES2.0.
> This patch does affect existing development setups, as it changes
> the
> name of the DTB for Salvator-X boards equipped with ES1.x SoCs.
> Given most developers have access to ES1.x only, this patch must
> not be
> applied yet.
Would it make more sense to add a new r8a7795-es2.dtsi and keep the
current dtsi for es1? Having to load different device-trees based on
which kernel is used would be rather nasty.
--
Sjoerd Simons
Collabora Ltd.
next prev parent reply other threads:[~2017-03-30 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 13:37 [PATCH/RFC v2 0/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0 Geert Uytterhoeven
2017-03-24 13:37 ` [PATCH/RFC v2 1/2] " Geert Uytterhoeven
2017-03-27 8:48 ` Laurent Pinchart
2017-03-29 8:13 ` Simon Horman
2017-03-29 8:31 ` Geert Uytterhoeven
2017-03-29 8:45 ` Simon Horman
2017-04-20 9:36 ` Geert Uytterhoeven
2017-04-20 10:42 ` Laurent Pinchart
2017-04-20 10:55 ` Geert Uytterhoeven
2017-04-20 11:24 ` Laurent Pinchart
2017-04-20 11:36 ` Geert Uytterhoeven
2017-03-24 13:37 ` [PATCH/RFC v2 2/2] arm64: dts: r8a7795: salvator-x: " Geert Uytterhoeven
2017-03-30 10:48 ` Sjoerd Simons [this message]
2017-03-30 11:13 ` [PATCH/RFC v2 0/2] arm64: dts: r8a7795: " Geert Uytterhoeven
2017-03-30 11:50 ` Sjoerd Simons
2017-03-30 12:08 ` 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=1490870898.3471.3.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--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=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@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