From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v2 1/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0
Date: Wed, 29 Mar 2017 10:13:52 +0200 [thread overview]
Message-ID: <20170329081352.GF6512@verge.net.au> (raw)
In-Reply-To: <1612430.SNEha5n02K@avalon>
On Mon, Mar 27, 2017 at 11:48:12AM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Friday 24 Mar 2017 14:37:44 Geert Uytterhoeven wrote:
> > Update r8a7795.dtsi so it corresponds to R-Car H3 ES2.0 or later:
> > - The following devices no longer exist on ES2.0, and are thus removed:
> > fcpf2, fcpvd3, fcpvi2, fdp1-2, usb3-if1, vspd3, vspi2.
> > - The DU <-> VSPD topology is different on ES2.0, hence remove the
> > "vsps" property from the DU node until the driver can handle this.
>
> I think I'll need a different compatible string between ES1.x and ES2 for the
> DU. It could make sense to move the whole DU node to *-es1.dtsi. We can decide
> about that later when I'll have a DU driver prototype ready.
That makes sense to me.
Geert, will you respin this?
next prev parent reply other threads:[~2017-03-29 8:13 UTC|newest]
Thread overview: 15+ 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 2/2] arm64: dts: r8a7795: salvator-x: " Geert Uytterhoeven
[not found] ` <1490362665-4422-2-git-send-email-geert+renesas@glider.be>
2017-03-27 8:48 ` [PATCH/RFC v2 1/2] arm64: dts: r8a7795: " Laurent Pinchart
2017-03-29 8:13 ` Simon Horman [this message]
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-30 10:48 ` [PATCH/RFC v2 0/2] " Sjoerd Simons
2017-03-30 11:13 ` 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=20170329081352.GF6512@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).