On Sat, Oct 14, 2017 at 1:34 PM, Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote: > Hello, > > On Mon, 9 Oct 2017 21:39:51 +0100, Grant Likely wrote: > >> Here is my current list of topics in no particular order, including >> the topic moderator: >> >> Runtime memory consumption (Rob Herring) >> Overlay maintenance plan (TBC) >> Stable ABI for devicetree (TBC) >> DT YAML encoding (Pantelis Antoniou) >> DT Schema format - option 1 (Pantelis Antoniou) >> DT Schema format - option 2 (Grant Likely) >> Sharing Generic bindings (TBC) >> devicetree.org update (Grant) >> >> Reply to this email if you want to propose another topic. > > I'd like to propose a quick discussion on how to avoid duplicating DT > description when a SoC is composed of aggregations of IP blocks that > are duplicated (in 2, 4 or 8 copies). > > As an example, we currently have > arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi and > arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi that are almost > identical, because they represent the same aggregation of IP blocks, > present two times in the same SoC (Marvell Armada 8K). As we are going > to have SoCs with more than 2 copies in the future, we want to find a > way to avoid duplicating the description of those aggregations. > > I'd like to present the problem scope, a possible solution solely based > on C preprocessor macros, and then open the discussion to see what is > the right approach to solve this problem. I'll include time for this alongside the overlay maintenance plan topic. It seems to me that they are closely related problems. g. > > I don't think that more than 10-15 minutes is needed for presenting the > problem scope and one possible solution. The following discussion may > be longer though. > > I'll be attending on both the morning and afternoon, but I'll be > leaving at ~4:30 PM. > > Best regards, > > Thomas Petazzoni > -- > Thomas Petazzoni, CTO, Free Electrons > Embedded Linux and Kernel engineering > http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
