Skip to content

RFC drivers: footprint reduction proposal

Tom Rini u-boot 1 version New

Get series with b4
b4 am 20200622142029.GG27801@bill-the-cat

Versions newest first

  1. v1 RFC Latest0 of 4 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/4] drivers: footprint reduction proposal
Quoted 31 lines · Walter Lozano

Hi Tom,

Quoted 21 lines · Tom Rini
Quoted 19 lines · Walter Lozano

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.

Quoted 7 lines
Quoted 4 lines

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!

Quoted 8 lines

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!

Signature · 8 lines
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>