From: Grant Likely <grant.likely@secretlab.ca>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kumar Gala <kumar.gala@linaro.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Rob Herring <rob.herring@linaro.org>,
devicetree-spec@vger.kernel.org,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Andy Gross <andy.gross@linaro.org>,
Lucas Stach <l.stach@pengutronix.de>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Ksummit-discuss] Devicetree Workshop at Kernel Summit Prague (26 Oct 2017)
Date: Tue, 17 Oct 2017 14:30:00 +0100 [thread overview]
Message-ID: <CACxGe6uH0A9s+tuaS3SrUmnRfRPUsxCsGP8wT6vOd4Q3QxXc4w@mail.gmail.com> (raw)
In-Reply-To: <20171014143457.72df1f54@windsurf.home>
On Sat, Oct 14, 2017 at 1:34 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> 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
next prev parent reply other threads:[~2017-10-17 13:30 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 20:39 Grant Likely
2017-10-14 12:34 ` Thomas Petazzoni
2017-10-17 13:30 ` Grant Likely [this message]
2017-10-16 5:36 ` Michal Simek
2017-10-16 14:11 ` Rob Herring
2017-10-18 14:04 ` Michal Simek
2017-10-18 14:28 ` Andre Przywara
2017-10-18 15:32 ` Rob Herring
2017-10-18 16:05 ` Andre Przywara
2017-10-18 16:20 ` Pantelis Antoniou
2017-10-16 16:40 ` Ben Dooks
2017-10-16 18:44 ` Heiko Stübner
2017-10-16 19:45 ` Rob Herring
2017-10-17 13:38 ` Grant Likely
2017-10-17 23:45 ` Frank Rowand
2017-10-17 13:32 ` Grant Likely
2017-10-18 10:08 ` Thomas Petazzoni
2017-10-16 16:42 ` Ben Dooks
2017-10-17 13:34 ` Grant Likely
2017-10-17 9:48 ` Boris Brezillon
2017-10-17 13:21 ` Tom Rini
2017-10-17 13:48 ` Grant Likely
2017-10-17 16:21 ` Ian Lepore
2017-10-17 17:02 ` Kumar Gala
2017-10-17 17:24 ` Geert Uytterhoeven
2017-10-17 19:03 ` Bird, Timothy
2017-10-18 12:14 ` Grant Likely
2017-10-18 12:59 ` Pantelis Antoniou
2017-10-18 13:18 ` Alexandre Belloni
2017-10-18 13:21 ` Geert Uytterhoeven
2017-10-18 17:41 ` Bird, Timothy
2017-10-18 18:00 ` Rob Herring
2017-10-18 21:10 ` Alexandre Belloni
2017-10-18 16:18 ` David Woodhouse
2017-10-18 14:13 ` Rob Herring
2017-10-18 17:45 ` Bird, Timothy
2017-10-18 14:07 ` Kumar Gala
2017-10-17 17:25 ` Rob Herring
2017-10-18 10:11 ` Thomas Petazzoni
2017-10-18 10:35 ` Chen-Yu Tsai
2017-10-18 11:09 ` Mark Brown
2017-10-18 17:59 ` Tom Rini
2017-10-18 23:28 ` Andrew Turner
2017-10-18 23:53 ` Rob Herring
2017-10-19 14:00 ` Alexandre Torgue
2017-10-19 14:59 ` Rob Herring
2017-10-19 18:46 ` Frank Rowand
2017-10-20 9:55 ` Alexandre Torgue
2017-10-20 10:01 ` David Gibson
2017-10-20 13:37 ` Rob Herring
2017-10-22 8:25 ` David Gibson
2017-10-20 13:47 ` Alexandre Torgue
2017-10-19 0:04 ` Mark Brown
2017-10-19 11:10 ` Grant Likely
2017-10-24 7:37 ` Boris Brezillon
2017-10-25 14:40 ` Maxime Ripard
2017-10-26 5:47 ` Frank Rowand
2017-10-26 7:17 ` Grant Likely
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=CACxGe6uH0A9s+tuaS3SrUmnRfRPUsxCsGP8wT6vOd4Q3QxXc4w@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=andy.gross@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=kumar.gala@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=pantelis.antoniou@konsulko.com \
--cc=rob.herring@linaro.org \
--cc=thomas.petazzoni@free-electrons.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