[PATCH v4 04/14] dtoc: add support to scan drivers

Walter Lozano walter.lozano at collabora.com
Fri Jul 3 13:08:46 CEST 2020

On 2/7/20 16:47, Simon Glass wrote:
> Hi Walter,
> On Thu, 25 Jun 2020 at 19:43, Simon Glass <sjg at chromium.org> wrote:
>> On Wed, 24 Jun 2020 at 22:10, Walter Lozano <walter.lozano at collabora.com> wrote:
>>> Currently dtoc scans dtbs to convert them to struct platdata and
>>> to generate U_BOOT_DEVICE entries. These entries need to be filled
>>> with the driver name, but at this moment the information used is the
>>> compatible name present in the dtb. This causes that only nodes with
>>> a compatible name that matches a driver name generate a working
>>> entry.
>>> In order to improve this behaviour, this patch adds to dtoc the
>>> capability of scan drivers source code to generate a list of valid driver
>>> names and aliases. This allows to generate U_BOOT_DEVICE entries using
>>> valid driver names and rise a warning in the case a name is not valid.
>>> Signed-off-by: Walter Lozano <walter.lozano at collabora.com>
>>> ---
>>>   tools/dtoc/dtb_platdata.py | 91 ++++++++++++++++++++++++++++++++++++--
>>>   tools/dtoc/test_dtoc.py    | 33 ++++++++++++++
>>>   2 files changed, 120 insertions(+), 4 deletions(-)
>> Reviewed-by: Simon Glass <sjg at chromium.org>
> Unfortunately this patch seems to be missing a file
> dtoc_test_driver_alias.dts without which the tests fail. Can you
> please resend just this patch?

Sorry for the mistake. I've just sent the patch.

Thanks for your time and deep review.



More information about the U-Boot mailing list