<feed xmlns='http://www.w3.org/2005/Atom'>
<title>starfive-tech/u-boot.git/tools/dtoc/main.py, branch rtthread_AMP</title>
<subtitle>StarFive Tech U-Boot for VisionFive (JH7110) boards (mirror)</subtitle>
<id>https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP</id>
<link rel='self' href='https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/'/>
<updated>2021-07-21T16:27:33+00:00</updated>
<entry>
<title>dtoc: Convert to use ArgumentParser</title>
<updated>2021-07-21T16:27:33+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-04T18:19:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=973fa52416d7853d1c146c8a7bc374a9a890c49c'/>
<id>urn:sha1:973fa52416d7853d1c146c8a7bc374a9a890c49c</id>
<content type='text'>
Use this parser instead of OptionParser, which is deprecated.

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: Add an option for device instantiation</title>
<updated>2021-03-22T06:23:27+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-02-03T13:01:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=4a092350d18d1aea637de6be8802a9de0cca194f'/>
<id>urn:sha1:4a092350d18d1aea637de6be8802a9de0cca194f</id>
<content type='text'>
Add an option to instantiate devices at build time. For now this just
parses the option and sets up a few parameters.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Support tracking the phase of U-Boot</title>
<updated>2021-03-22T06:23:27+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-02-03T13:01:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=b00f0066e52413e0f8fd4a84681e6e27c4270c26'/>
<id>urn:sha1:b00f0066e52413e0f8fd4a84681e6e27c4270c26</id>
<content type='text'>
U-Boot operates in several phases, typically TPL, SPL and U-Boot proper.
The latter does not use dtoc.

In some rare cases different drivers are used for two phases. For example,
in TPL it may not be necessary to use the full PCI subsystem, so a simple
driver can be used instead.

This works in the build system simply by compiling in one driver or the
other (e.g. PCI driver + uclass for SPL; simple_bus for TPL). But dtoc has
no way of knowing which code is compiled in for which phase, since it does
not inspect Makefiles or dependency graphs.

So to make this work for dtoc, we need to be able to explicitly mark
drivers with their phase. This is done by adding an empty macro to the
driver. Add support for this in dtoc.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Save scan information across test runs</title>
<updated>2021-03-22T06:23:27+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-02-03T13:00:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=a32eb7dca7c3ea8d23e1bc0ce927ad2a00d8bf45'/>
<id>urn:sha1:a32eb7dca7c3ea8d23e1bc0ce927ad2a00d8bf45</id>
<content type='text'>
At present most of the tests scan the U-Boot source tree as part of their
run. This information does not change across tests, so we can save time
by remembering it.

Add a way to set up this information and use it for each test, taking a
copy first, so as not to mess up the original.

This reduces the run time from about 1.6 seconds to 1.5 seconds on my
machine. For code coverage (which cannot run in parallel), it reduces from
33 seconds to 5.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Move src_scan tests to a separate file</title>
<updated>2021-01-05T19:26:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-12-29T03:35:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=10ea9c0b059c37e6b2026fe1334d1d57c465984d'/>
<id>urn:sha1:10ea9c0b059c37e6b2026fe1334d1d57c465984d</id>
<content type='text'>
Move the tests related to scanning into their own class, updating them
to avoid using dtb_platdata as a pass-through.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Run tests using test_util</title>
<updated>2021-01-05T19:26:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-12-29T03:34:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=5d9a3aa99cc7a1ed6502a98152bd0e13b4e05539'/>
<id>urn:sha1:5d9a3aa99cc7a1ed6502a98152bd0e13b4e05539</id>
<content type='text'>
Use the standard function for running tests and reported results. This
allows the tests to run in parallel, which is a significant speed-up on
most machines (e.g. 4.5 seconds -&gt; 1.5s on mine).

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Add an 'all' command</title>
<updated>2021-01-05T19:26:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-12-29T03:34:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=10cbd3b7da12e993c67d56182d30294661a93619'/>
<id>urn:sha1:10cbd3b7da12e993c67d56182d30294661a93619</id>
<content type='text'>
With upcoming changes, dtoc will output several files for different
of-platdata components.

Add a way to output all ava!ilable files at once ('all'), to the
appropriate directories, without needing to specify each one invidually.

This puts the commands in alphabetical order, so update the tests
accordingly.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Allow providing a directory to write files to</title>
<updated>2021-01-05T19:26:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-12-29T03:34:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=192c111cfce0684fa1cbbd4a4bd3df03720ef7a6'/>
<id>urn:sha1:192c111cfce0684fa1cbbd4a4bd3df03720ef7a6</id>
<content type='text'>
At present dtoc writes only a single file on each invocation. U-Boot
writes the two files it needs by separate invocations of dtoc. Since dtoc
now scans all U-Boot driver source, this is fairly slow (about 1 second
per file).

It would be better if dtoc could write all the files at once.

In preparation for this, add a way to specify an output directory for the
files.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Use None to mean stdout</title>
<updated>2021-01-05T19:26:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-12-29T03:34:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=f62cea0e205c905632be3aefa82b10ef36ce8a25'/>
<id>urn:sha1:f62cea0e205c905632be3aefa82b10ef36ce8a25</id>
<content type='text'>
At present dtoc uses '-' internally to mean that output should go to
stdout. This is not necessary and None is more convenient. Update it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>patman: Tidy up sys.path changes</title>
<updated>2020-04-26T20:25:21+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-18T00:09:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=b4fa94959db039c7eca4531a5b9a41baffa8b4c8'/>
<id>urn:sha1:b4fa94959db039c7eca4531a5b9a41baffa8b4c8</id>
<content type='text'>
Now that we are using absolute paths we can remove some of the sys.path
mangling that appears in the tools.

We only need to add the path to 'tools/' so that everything can find
modules relative to that directory.

The special paths for finding pylibfdt remain.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
