From: Tom Rini Date: Fri, 19 Jun 2020 17:48:29 -0400 Subject: [RFC 0/4] drivers: footprint reduction proposal In-Reply-To: <20200619211140.5081-1-walter.lozano@collabora.com> References: <20200619211140.5081-1-walter.lozano@collabora.com> Message-ID: <20200619214829.GV27801@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 so is something missing? Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: