Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Kevin Hilman <khilman@baylibre.com>,
	Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Bajjuri Praneeth <praneeth@ti.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Louis Chauvet <louis.chauvet@bootlin.com>
Subject: Re: [PATCH 1/5] ARM: dts: ti: Enable overlays for all DTB files
Date: Mon, 16 Feb 2026 16:11:55 +0100	[thread overview]
Message-ID: <20260216161155.09fae580@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <CAOCHtYicmeSzH5Q2_qTwAZw3s+__JRwUrXvz01+KCsJJHAznUw@mail.gmail.com>

On Thu, 12 Feb 2026 21:16:05 -0600
Robert Nelson <robertcnelson@gmail.com> wrote:

> On Thu, Feb 12, 2026 at 4:19 PM Andreas Kemnade <andreas@kemnade.info> wrote:
> >
> > On Thu, 12 Feb 2026 17:55:43 +0100
> > "H. Nikolaus Schaller" <hns@goldelico.com> wrote:
> >  
> > > > Am 12.02.2026 um 17:47 schrieb Andreas Kemnade <andreas@kemnade.info>:
> > > >
> > > > On Thu, 12 Feb 2026 16:49:43 +0100
> > > > "H. Nikolaus Schaller" <hns@goldelico.com> wrote:
> > > >  
> > > >>> Am 12.02.2026 um 16:26 schrieb Kory Maincent (TI)
> > > >>> <kory.maincent@bootlin.com>:
> > > >>>
> > > >>> Allow overlays to be applied to any DTB. This adds around ~40% to the
> > > >>> total size of the DTB files on average.  
> > > >>
> > > >> Is this unconditionally enabled or can it be turned off by some
> > > >> CONFIG? We have our own defconfig so I would not worry if if is
> > > >> enabled in omap2plus_defconfig and disabled in ours.
> > > >>
> > > >> We have several devices where the boot loader can't handle overlays
> > > >> (never touch a working boot-loader :) So this seems to only contribute
> > > >> to build and load time without benefit.
> > > >>  
> > > > As long as you do not add overlays, the bootloader does not care. I
> > > > would like to simply carry around the 1-bit mmc overlay for one broken
> > > > board. That would help me. So I think there is a benefit but nobody
> > > > forces you to use it.  
> > >
> > > Well, it does not force to use the really good feature, but it forces to
> > > add ~40% more file size and some more compile time, if I understand it
> > > correctly. 
> > Compile time, hardly measurable even if you just do make dtbs.
> >
> > Size on disk:
> > a) if it lives around in a /boot partitions with kernels and initrams in it,
> >    then we are around 1% more space needed.
> >
> > b) if it has separate partitions maybe on some mtd: Looking around: GTA04
> >    has quite some headroom left. Usage is still <50% even with symbols
> >    enabled.
> >
> > But on the other no one else seems to enable that besides for devices with
> > open expansion boards carrying "hats". So overall, should we really be the
> > exception?  
> 
> Do we want to maybe transition like TI did for k3?
> 
> Start with board specific DTC_FLAGS flags for specific boards:
> 
> and then just enabling overlays by default :
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/ti/Makefile?id=bca4146b1f66dbca07591bfd6ad695c699b5a093
> 
> If we do board-specific, all the "Beagle" related items can be auto
> enabled `-@`..

Yes, I will move on to this solution for now to avoid too many complaints about
the devicetree size increases.

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com


  reply	other threads:[~2026-02-16 15:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 15:26 [PATCH 0/5] Add support for Seeed Studio BeagleBone HDMI cape overlay Kory Maincent (TI)
2026-02-12 15:26 ` [PATCH 1/5] ARM: dts: ti: Enable overlays for all DTB files Kory Maincent (TI)
2026-02-12 15:42   ` Krzysztof Kozlowski
2026-02-12 16:55     ` Kory Maincent
2026-02-12 15:49   ` H. Nikolaus Schaller
2026-02-12 16:47     ` Andreas Kemnade
2026-02-12 16:55       ` H. Nikolaus Schaller
2026-02-12 22:19         ` Andreas Kemnade
2026-02-13  3:16           ` Robert Nelson
2026-02-16 15:11             ` Kory Maincent [this message]
2026-02-17  8:58               ` H. Nikolaus Schaller
2026-02-17  9:34                 ` Andreas Kemnade
2026-02-17  9:36                 ` Kory Maincent
2026-02-18  7:28                   ` H. Nikolaus Schaller
2026-02-13  5:33           ` H. Nikolaus Schaller
2026-02-16 16:22             ` Andreas Kemnade
2026-02-12 15:26 ` [PATCH 2/5] ARM: multi_v7_defconfig: Enable TILCDC DRM driver Kory Maincent (TI)
2026-02-12 15:26 ` [PATCH 3/5] ARM: omap2plus_defconfig: Enable ITE IT66121 driver Kory Maincent (TI)
2026-02-12 15:26 ` [PATCH 4/5] ARM: multi_v7_defconfig: " Kory Maincent (TI)
2026-02-12 15:40   ` Krzysztof Kozlowski
2026-02-12 16:58     ` Kory Maincent
2026-02-12 15:26 ` [PATCH 5/5] ARM: dts: am335x: Add Seeed Studio BeagleBone HDMI cape overlay Kory Maincent (TI)

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=20260216161155.09fae580@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hns@goldelico.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=louis.chauvet@bootlin.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tony@atomide.com \
    --cc=tzimmermann@suse.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