From: Simon Horman <horms@verge.net.au>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v3 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support
Date: Fri, 22 Jul 2016 10:47:00 +0900 [thread overview]
Message-ID: <20160722014700.GE21943@verge.net.au> (raw)
In-Reply-To: <69c8673e-4f9f-9dac-42ab-2557ab62f8b2@de.bosch.com>
Hi Dirk,
On Thu, Jul 21, 2016 at 07:20:30AM +0200, Dirk Behme wrote:
> Hi Simon,
>
> On 21.07.2016 01:51, Simon Horman wrote:
> >On Wed, Jun 29, 2016 at 10:15:27AM +0200, Dirk Behme wrote:
> >>Hi Simon,
> >
> >...
> >
> >>Hmm, could you kindly help me to remember what's the recent status of your
> >>discussion above regarding a hierarchical structure of the RCar3 device
> >>trees?
> >
> >Hi Dirk,
> >
> >>From my point of view the most promising avenue at this time is work that
> >Geert has been doing to explore making things more flexible by updating the
> >DT automatically at run time. He can expand on this but the idea is to add
> >per-soc compat strings and otherwise update the DT into a per-SoC version.
> >This ought to allow significant portions of the DT to be common between
> >SoCs in the same R-Car generation for at lest Gen 2 and Gen 3.
>
>
> There are two topics:
>
> a) Hierarchical static structure of devices trees and clock definitions for
> RCar3 SoCs
> b) Detecting of RCar3 SoC type and engineering sample revisions at runtime
>
> About which topic do you talk here? I think we shouldn't mix them.
I was referring to topic a) which I would describe as consolidation of
static DT descriptions. However, I believe that the same or a similar
approach to DT fixups can also be used for problem b). I agree
we should discuss these topics separately.
> Best regards
>
> Dirk
>
> P.S.: If you like, we could have a chat in #renesas-soc, too :)
Sure. In general I am there when I am at my desk and not completely
consumed by work at hand.
next prev parent reply other threads:[~2016-07-22 1:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 1:54 [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-05-24 1:54 ` [PATCH v3 1/3] arm64: dts: r8a7796: " Simon Horman
2016-05-24 5:30 ` Dirk Behme
2016-05-25 0:48 ` Simon Horman
2016-05-25 5:10 ` Dirk Behme
2016-05-25 7:32 ` Dirk Behme
2016-05-26 7:03 ` Geert Uytterhoeven
2016-05-26 7:32 ` Dirk Behme
2016-05-26 8:05 ` Geert Uytterhoeven
2016-05-26 8:11 ` Dirk Behme
2016-05-26 2:28 ` Simon Horman
2016-05-26 7:14 ` Dirk Behme
2016-05-27 0:42 ` Simon Horman
2016-05-27 6:39 ` Geert Uytterhoeven
2016-05-27 7:32 ` Dirk Behme
2016-06-29 8:15 ` Dirk Behme
2016-07-20 23:51 ` Simon Horman
2016-07-21 5:20 ` Dirk Behme
2016-07-22 1:47 ` Simon Horman [this message]
2016-05-25 7:38 ` Dirk Behme
2016-05-26 2:31 ` Simon Horman
2016-05-24 1:54 ` [PATCH v3 2/3] arm64: dts: salvator-x: add Salvator-X board on R8A7796 SoC Simon Horman
2016-05-24 1:54 ` [PATCH v3 3/3] arm64: defconfig: enable Renesas " Simon Horman
2016-06-06 1:33 ` [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-06-06 1:52 ` Simon Horman
2016-06-24 3:05 ` Simon Horman
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=20160722014700.GE21943@verge.net.au \
--to=horms@verge.net.au \
--cc=dirk.behme@de.bosch.com \
--cc=geert@linux-m68k.org \
--cc=khiem.nguyen.xt@rvc.renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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