Hi Walter, On Fri, 19 Jun 2020 at 15:12, Walter Lozano <walter.loz...@collabora.com> wrote: > > Based on several reports there is an increasing concern in the impact > of adding additional features to drivers based on compatible strings. > A good example of this situation is found in [1]. > > In order to reduce this impact and as an initial step for further > reduction, propose a new way to declare compatible strings, which allows > to only include the useful ones.
What are the useful ones? > > The idea is to define compatible strings in a way to be easily parsed by > dtoc, which will be responsible to build struct udevice_id [] based on > the compatible strings present in the dtb. > > Additional features can be easily added, such as define constants > depending on the presence of compatible strings, which allows to enable > code blocks only in such cases without the need of adding additional > configuration options. > > [1] > http://patchwork.ozlabs.org/project/uboot/patch/20200525202429.2146-1-ag...@denx.de/ > > Signed-off-by: Walter Lozano <walter.loz...@collabora.com> > --- > tools/dtoc/dtb_platdata.py | 32 ++++++++++++++++++++++++++++++++ > 1 file changed, 32 insertions(+) I think dtoc should be able to parse the compatible strings as they are today - e.g. see the tiny-dm stuff. Regards, Simon
