<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/dtoc, branch v2022.01</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/dtoc?h=v2022.01</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/dtoc?h=v2022.01'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2021-09-25T15:46:15Z</updated>
<entry>
<title>irq: Tidy up of-platdata irq support</title>
<updated>2021-09-25T15:46:15Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-08-07T13:24:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3e57ad907caa55bab8ba52ef87ddbc5130aede2c'/>
<id>urn:sha1:3e57ad907caa55bab8ba52ef87ddbc5130aede2c</id>
<content type='text'>
This function is available but not exported. More generally it does not
really work as intended.

Reimplement it and add a sandbox test too.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Correct the intarray-widening test case</title>
<updated>2021-08-08T17:27:27Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-08-02T13:37:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e679f39f7fc3eb083b2f957d748f81bbdc28f28c'/>
<id>urn:sha1:e679f39f7fc3eb083b2f957d748f81bbdc28f28c</id>
<content type='text'>
This case was intended to check that widening an int array with an int
does nothing. Fix it.

Reported-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
</content>
</entry>
<entry>
<title>dtoc: Support widening a bool value</title>
<updated>2021-08-01T15:05:24Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-29T01:23:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=eec44c7218a3c3ce924a282cc46a59e83feb9de1'/>
<id>urn:sha1:eec44c7218a3c3ce924a282cc46a59e83feb9de1</id>
<content type='text'>
At present if we see 'ranges' property (with no value) we assume it is a
boolean, as per the devicetree spec.

But another node may define 'ranges' with a value, forcing us to widen it
to an int array. At present this is not supported and causes an error.

Fix this and add some test cases.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reported-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>dtoc: Fix widening an int array to an int</title>
<updated>2021-08-01T15:05:24Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-29T01:23:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ca04494d76bf1152cd9ab1f67af5101c86e0824f'/>
<id>urn:sha1:ca04494d76bf1152cd9ab1f67af5101c86e0824f</id>
<content type='text'>
An int array can hold a single int so we should not need to do anything
in the widening operation. However due to a quirk in the code, an int[3]
widened with an int produced an int[4]. Fix this and add a test.

Fix a comment typo while we are here.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reported-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>dtoc: Rename is_wider_than() to reduce confusion</title>
<updated>2021-08-01T15:05:24Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-29T01:23:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=df82de805172687e88dd7d72b68a9223b0a4c269'/>
<id>urn:sha1:df82de805172687e88dd7d72b68a9223b0a4c269</id>
<content type='text'>
The current name is confusing because the logic is actually backwards from
what you might expect. Rename it to needs_widening() and update the
comments.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Detect drivers which do not parse correctly</title>
<updated>2021-07-21T16:27:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:49Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=43ba4926702ca0c6d896b8d318b4c596979d2f32'/>
<id>urn:sha1:43ba4926702ca0c6d896b8d318b4c596979d2f32</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
Reviewed-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
</content>
</entry>
<entry>
<title>dtoc: Detect unexpected suffix on .of_match</title>
<updated>2021-07-21T16:27:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=86ff01e890a72fb2b8cefab542d4b9123fe83036'/>
<id>urn:sha1:86ff01e890a72fb2b8cefab542d4b9123fe83036</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Add a stdout check in test_normalized_name()</title>
<updated>2021-07-21T16:27:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4f1727a7e31c192d294280b0379b522f57b54d31'/>
<id>urn:sha1:4f1727a7e31c192d294280b0379b522f57b54d31</id>
<content type='text'>
This test captures output but does not always check it. Add the missing
code and drop the old comment.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Correct the re_compat regular expression</title>
<updated>2021-07-21T16:27:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=893142aa3bce28155905594bb054b0f434cafdfd'/>
<id>urn:sha1:893142aa3bce28155905594bb054b0f434cafdfd</id>
<content type='text'>
This expects a . before the field name (.e.g '.compatible = ...) but
presently accepts anything at all. Fix it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
</content>
</entry>
<entry>
<title>dtoc: Allow multiple warnings for a driver</title>
<updated>2021-07-21T16:27:34Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1b5fe11d957491a2f53a409b32b1a281c708e2fd'/>
<id>urn:sha1:1b5fe11d957491a2f53a409b32b1a281c708e2fd</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
Reviewed-by: Walter Lozano &lt;walter.lozano@collabora.com&gt;
</content>
</entry>
</feed>
