From mboxrd@z Thu Jan 1 00:00:00 1970 From: dirk.behme@de.bosch.com (Dirk Behme) Date: Thu, 21 Jul 2016 07:20:30 +0200 Subject: [PATCH v3 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support In-Reply-To: <20160720235154.GA21407@verge.net.au> References: <1464054880-25843-1-git-send-email-horms+renesas@verge.net.au> <1464054880-25843-2-git-send-email-horms+renesas@verge.net.au> <20160525004825.GC7292@verge.net.au> <20160526022833.GE18393@verge.net.au> <59e6225a-6dfa-8bde-dd2e-3428d6fedfe2@de.bosch.com> <20160527004256.GD14269@verge.net.au> <20160720235154.GA21407@verge.net.au> Message-ID: <69c8673e-4f9f-9dac-42ab-2557ab62f8b2@de.bosch.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. Best regards Dirk P.S.: If you like, we could have a chat in #renesas-soc, too :)