u-boot.git/tools/dtoc/src_scan.py, branch master

dtoc: avoid invalid escape sequence '\s'

2024-03-01T14:53:47+00:00

\s is not a valid escape sequence in strings.
Mark regular expressions with r''.

Signed-off-by: Heinrich Schuchardt

dtoc: Detect drivers which do not parse correctly

2021-07-21T16:27:34+00:00

At present if a driver is missing a uclass or compatible stirng, this
is silently ignored. This makes sense in most cases, particularly for
the compatible string, since it is not required except when the driver
is used with of-platdata.

But it is also not very helpful. When there is some sort of problem
with a driver, the missing compatible string (for example) may be the
cause.

Add a warning in this case, showing it only for drivers which are used
by the build.

Signed-off-by: Simon Glass 
Reviewed-by: Walter Lozano

dtoc: Detect unexpected suffix on .of_match

2021-07-21T16:27:34+00:00

Some rockchip drivers use a suffix on the of_match line which is not
strictly valid. At present this causes the parsing to fail. Fix this
and offer a warning.

Signed-off-by: Simon Glass

dtoc: Correct the re_compat regular expression

2021-07-21T16:27:34+00:00

This expects a . before the field name (.e.g '.compatible = ...) but
presently accepts anything at all. Fix it.

Signed-off-by: Simon Glass 
Reviewed-by: Walter Lozano

dtoc: Allow multiple warnings for a driver

2021-07-21T16:27:34+00:00

At present we show when a driver is missing but this is not always that
useful. There are various reasons why a driver may appear to be missing,
such as a parse error in the source code or a missing field in the driver
declaration.

Update the implementation to record all warnings for each driver, showing
only those which relate to drivers that are actually used. This avoids
spamming the user with warnings related to a driver for a different board.

Signed-off-by: Simon Glass 
Reviewed-by: Walter Lozano

dtoc: Avoid using subscripts on match objects

2021-07-21T16:27:33+00:00

These are not supported before Python 3.6 so avoid them.

Signed-off-by: Simon Glass 
Reviewed-by: Walter Lozano

dtoc: Show driver warnings once at the end

2021-04-06T04:33:19+00:00

At present warnings are shown as soon as they are discovered in the
source scannner. But the function that detects them may be called multiple
times.

Collect all the warnings and show them at the end.

Signed-off-by: Simon Glass

dtoc: Support processing the root node

2021-03-22T06:23:27+00:00

The device for the root node is normally bound by driver model on init.
With devices being instantiated at build time, we must handle the root
device also.

Add support for processing the root node, which may not have a compatible
string.

Signed-off-by: Simon Glass

dtoc: Set up the uclasses that are used

2021-03-22T06:23:27+00:00

We only care about uclasses that are actually used. This is determined by
the drivers that use them. Check all the used drivers and build a list of
'valid' uclasses.

Also add references to the uclasses so we can generate C code that uses
them. Attach a uclass to each valid driver.

For the tests, now that we have uclasses we must create an explicit test
for the case where a node does not have one. This should only happen if
the source code does not build, or the source-code scanning fails to find
it.

Signed-off-by: Simon Glass

dtoc: Detect drivers only at the start of start of line

2021-03-22T06:23:27+00:00

If a driver declaration is included in a comment, dtoc currently gets
confused. Update the parser to only consider declarations that begin at
the start of a line. Since multi-line comments begin with an asterisk,
this avoids the problem.

Signed-off-by: Simon Glass