From: Tom Rini <trini@konsulko.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: u-boot@lists.denx.de, Marek Vasut <marex@denx.de>,
Praneeth Bajjuri <praneeth@ti.com>,
Maxime Ripard <maxime@cerno.tech>, Simon Glass <sjg@chromium.org>
Subject: Re: [RFC/PATCH] lib/Kconfig: Enable OF_LIBFDT_OVERLAY by default when FIT is enabled
Date: Fri, 10 Mar 2023 13:12:24 -0500 [thread overview]
Message-ID: <20230310181224.GA4089221@bill-the-cat> (raw)
In-Reply-To: <20230129163022.13221-1-laurent.pinchart@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
On Sun, Jan 29, 2023 at 06:30:22PM +0200, Laurent Pinchart wrote:
> FIT image support is commonly used to bundle a kernel image, a device
> tree, and device tree overlays. Applying overlays requires the
> OF_LIBFDT_OVERLAY config option to be set, which lots of boards fail to
> select, most likely because developers never noticed. This leads to an
> error when trying to apply overlays:
>
> "config with overlays but CONFIG_OF_LIBFDT_OVERLAY not set"
>
> TI ARM boards select the option by default. Extend this to all systems
> that select the FIT option. This only affects the default, overlay
> support can still be disabled manually in the configuration.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Reviewed-by: Marek Vasut <marex@denx.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> ---
> I'm posting this as an RFC to get feedback. If the idea is generally
> appreciated, I'll update the defconfig files accordingly.
Alright, so, I put this through a world build, and most platforms grow
by 4-5kB. I think that means what I'd really like to see as a starting
point is more SoCs doing an "imply OF_LIBFDT_OVERLAY if OF_LIBFDT && FIT"
or adding to the default y list below, or similar. If that brings us to
the point where a good number of ARM boards with FIT are enabling it, we
can default y if ARM, for example. But right now it's more like several
hundred boards growing in size, which is uncomfortable, given the size
it's growing by.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-03-10 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 16:30 [RFC/PATCH] lib/Kconfig: Enable OF_LIBFDT_OVERLAY by default when FIT is enabled Laurent Pinchart
2023-01-29 16:43 ` Marek Vasut
2023-01-30 15:50 ` Simon Glass
2023-03-10 18:12 ` Tom Rini [this message]
2023-03-12 9:46 ` Laurent Pinchart
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=20230310181224.GA4089221@bill-the-cat \
--to=trini@konsulko.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=marex@denx.de \
--cc=maxime@cerno.tech \
--cc=praneeth@ti.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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