From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Devicetree add-on
Date: Thu, 30 Jan 2025 11:06:18 +0300 [thread overview]
Message-ID: <CAP1tNvQacfmq4oL1-ptT-XTfmoFWwAU6E-m5+cHuPgdEZ=EhOQ@mail.gmail.com> (raw)
In-Reply-To: <20250129085028.rd6xep2tjdffynna@pengutronix.de>
Hello.
Yes, I know about such an implementation.
But it seems a bit complicated to me compared to if it were possible to load
the full devicetree.
Also, the overlay is a bit limiting functionality, for example I can't use
new aliases in the overlay. There are also difficulties with writing endpoints.
Thanks!
ср, 29 янв. 2025 г. в 11:50, Marco Felsch <m.felsch@pengutronix.de>:
>
> Hi Alexander,
>
> thanks for reaching out to the ML.
>
> On 25-01-29, Alexander Shiyan wrote:
> > Hello All.
> >
> > The question arose whether it is possible to load an add-on into
> > devicetree, but NOT through an overlay,
>
> Why not dt-overlays?
>
> > i.e. as a full-fledged dtb?
> > Ideally, it should look like this: the main ENTRY_FUNCTION() loads the
> > base tree, then,
> > after initialization in device_initcall(), the board modification is
> > determined and the full devicetree
> > written for this variant is loaded.
>
> Sounds exactly like a dt-overlay use-case. As it sounds to me you do
> have common base for your platform/product family. This would be your
> base-dtb loaded for every product. Later on you need to apply the
> overlays accordingly.
>
> E.g. for the platform family I'm currently working with we do the
> following:
>
> base-dt:
> --------
> / {
> feat_a: feature-device-a {
> compatible = "xyz,feature-device-a";
> ...
> ...
> status = "disabled";
> };
>
> feat_b: feature-device-b {
> compatible = "foo,feature-device-b";
> ...
> ...
> status = "disabled";
> };
> };
>
> feat-a-dto:
> -----------
> &feat_a {
> status = "okay";
> };
>
> feat-b-dto:
> -----------
> &feat_b {
> status = "okay";
> };
>
> This way we define the whole node within the base-dt and the overlays
> only enable it. This makes the overlays very straightforwward and you
> still have the opportunity to reconfigure the device-node if you really
> have to.
>
> Regards,
> Marco
next prev parent reply other threads:[~2025-01-30 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 6:10 Alexander Shiyan
2025-01-29 8:50 ` Marco Felsch
2025-01-30 8:06 ` Alexander Shiyan [this message]
2025-01-30 13:39 ` Sascha Hauer
2025-01-30 13:45 ` Alexander Shiyan
2025-01-31 13:19 ` Sascha Hauer
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='CAP1tNvQacfmq4oL1-ptT-XTfmoFWwAU6E-m5+cHuPgdEZ=EhOQ@mail.gmail.com' \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
/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