From: Walker Chen <walker.chen@starfivetech.com>
To: Conor Dooley <conor@kernel.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh+dt@kernel.org>,
Daniel Bovensiepen <daniel.bovensiepen@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
<linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/1] riscv: dts: Enable device-tree overlay support for starfive devices
Date: Thu, 20 Jul 2023 14:34:03 +0800 [thread overview]
Message-ID: <d397c3ba-4ac9-bf21-5ae4-79db6c2ad16e@starfivetech.com> (raw)
In-Reply-To: <20230712-single-crestless-93bf57c09773@spud>
On 2023/7/13 0:23, Conor Dooley wrote:
> On Wed, Jul 12, 2023 at 06:17:19PM +0200, Emil Renner Berthing wrote:
>> On Mon, 10 Jul 2023 at 20:29, Conor Dooley <conor@kernel.org> wrote:
>> >
>> >
>> > Emil, Walker,
>> >
>> > On Tue, Jun 27, 2023 at 04:06:20PM +0800, Felix Moessbauer wrote:
>> > > Add the '-@' DTC option for the starfive devices. This option
>> > > populates the '__symbols__' node that contains all the necessary symbols
>> > > for supporting device-tree overlays (for instance from the firmware or
>> > > the bootloader) on these devices.
>> > >
>> > > The starfive devices allow various modules to be connected and this
>> > > enables users to create out-of-tree device-tree overlays for these modules.
>> > >
>> > > Please note that this change does increase the size of the resulting DTB
>> > > by ~20%. For example, with v6.4 increase in size is as follows:
>> >
>> > Whatcha think?
>>
>> I'm fine with it. I just wonder why it's only the Nvidia Tegra boards
>> and the VisionFive's that need this. Surely other boards have pins for
>> expansion cards.
>
> It's totally not just these two - there's been a flurry of similar
> patches recently. The RPi stuff got it - I think I Acked that one from
> the DT side while Rob and Krzysztof were out of office, partially on the
> basis that the Nvidia stuff had it (and IIRC Renesas).
> Since then there's been a couple other ones that got the same treatment,
> including 32-bit ARM Microchip stuff. I've been avoiding doing it for the
> RISC-V Microchip to see if Rob decides that what I Acked was a problem.
>
> It seems generally helpful, so I've been a little suspicious as to why
> it was not done already...
I agree to use DT overlay though this will increase a little bit size for DTB.
For users who want to use expansion card like audio daughter board, it provides a convenient way.
Best regards,
Walker
next prev parent reply other threads:[~2023-07-20 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 8:06 [PATCH 1/1] riscv: dts: Enable device-tree overlay support for starfive devices Felix Moessbauer
2023-07-06 17:27 ` Palmer Dabbelt
2023-07-10 18:28 ` Conor Dooley
2023-07-12 16:17 ` Emil Renner Berthing
2023-07-12 16:23 ` Conor Dooley
2023-07-12 18:52 ` Emil Renner Berthing
2023-07-20 6:34 ` Walker Chen [this message]
2023-07-12 16:40 ` Conor Dooley
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=d397c3ba-4ac9-bf21-5ae4-79db6c2ad16e@starfivetech.com \
--to=walker.chen@starfivetech.com \
--cc=conor@kernel.org \
--cc=daniel.bovensiepen@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@kernel.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).