All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [RFC 0/4] drivers: footprint reduction proposal
Date: Mon, 22 Jun 2020 10:20:29 -0400	[thread overview]
Message-ID: <20200622142029.GG27801@bill-the-cat> (raw)
In-Reply-To: <e9a8227c-b53d-0046-18df-10aca75cd45d@collabora.com>

On Mon, Jun 22, 2020 at 11:12:40AM -0300, Walter Lozano wrote:
> Hi Tom,
> 
> On 19/6/20 18:48, Tom Rini wrote:
> > On Fri, Jun 19, 2020 at 06:11:36PM -0300, Walter Lozano wrote:
> > 
> > > Based on several reports and discussions it is clear that U-Boot's
> > > footprint is always a concern, and any kind of reduction is an
> > > improvement.
> > > 
> > > This series is a proposal to  help reducing the footprint by parsing
> > > information provided in DT and drivers in different ways and adding
> > > additional intelligence to dtoc. The current version implements the basic
> > > functionality in dtoc but this is no fully integrated, however it will allow
> > > us to discuss this approach.
> > > 
> > > Firstly, based on the compatible strings found in drivers, include only DT nodes
> > > which are supported by any driver present in U-Boot.
> > > 
> > > Secondly, generate struct udevice_id entries only for nodes present in DT,
> > > which will allow to avoid including additional data.
> > > 
> > > These are the first steps for further improvements as proposed in the specific
> > > patches in this series.
> > > 
> > > This work is based on the work of Simon Glass present in [1] which adds
> > > support to dtoc for parsing compatible strings.
> > > 
> > > [1] https://gitlab.denx.de/u-boot/custodians/u-boot-dm/-/tree/dtoc-working
> > I applied this series on top of the above tree, but there's no rule for
> > <generated/compatible.h> so is something missing?  Thanks!
> > 
> Thanks for taking the time to check this RFC.
> 
> As you pointed, the Makefile needs to be tweaked in order to be able to run
> a build, that is what I meant by "not fully integrated", also some
> additional stuff are missing. However, I thought that sending this RFC
> explaining the idea will be nice in order to confirm if the approaches
> proposed make sense for the community and at least the one to handle
> compatible strings is different from the linker list suggestion.

I think I like the idea, but I need to give a build a spin and poke
things harder.  What do I need to do to manually have this build+link?
Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200622/08acb115/attachment.sig>

  reply	other threads:[~2020-06-22 14:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 21:11 [RFC 0/4] drivers: footprint reduction proposal Walter Lozano
2020-06-19 21:11 ` [RFC 1/4] dtoc: add POC for dtb shrink Walter Lozano
2020-07-06 19:21   ` Simon Glass
2020-07-07 13:57     ` Walter Lozano
2020-07-07 14:15   ` Rasmus Villemoes
2020-07-07 14:32     ` Walter Lozano
2020-07-07 14:53       ` Rasmus Villemoes
2020-07-07 16:14         ` Walter Lozano
2020-06-19 21:11 ` [RFC 2/4] dtoc: add initial support for deleting DTB nodes Walter Lozano
2020-07-06 19:21   ` Simon Glass
2020-07-07 13:44     ` Walter Lozano
2020-06-19 21:11 ` [RFC 3/4] dtoc: add support for generate stuct udevice_id Walter Lozano
2020-07-06 19:21   ` Simon Glass
2020-07-07 14:08     ` Walter Lozano
2020-07-26 14:53       ` Simon Glass
2020-07-27  2:16         ` Walter Lozano
2020-07-29  2:42           ` Simon Glass
2020-07-29 16:00             ` Walter Lozano
2020-08-07 16:23               ` Simon Glass
2020-08-07 17:23                 ` Walter Lozano
2020-09-07  1:44                   ` Simon Glass
2020-09-07 19:10                     ` Walter Lozano
2020-06-19 21:11 ` [RFC 4/4] mmc: fsl_esdhc_imx: make use of dtoc to generate struct udevice_id Walter Lozano
2020-06-19 21:48 ` [RFC 0/4] drivers: footprint reduction proposal Tom Rini
2020-06-22 14:12   ` Walter Lozano
2020-06-22 14:20     ` Tom Rini [this message]
2020-06-22 15:25       ` Walter Lozano
2020-06-26 19:17         ` Walter Lozano

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=20200622142029.GG27801@bill-the-cat \
    --to=trini@konsulko.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.