<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/sandbox, branch v2017.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/arch/sandbox?h=v2017.07</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/sandbox?h=v2017.07'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2017-06-09T02:21:59Z</updated>
<entry>
<title>sandbox: Fix comparison of unsigned enum expression warning</title>
<updated>2017-06-09T02:21:59Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2017-05-14T00:11:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e2bc87d41ce866b30721d5b8ee395efefecd9bef'/>
<id>urn:sha1:e2bc87d41ce866b30721d5b8ee395efefecd9bef</id>
<content type='text'>
In os_dirent_get_typename() we are checking that type falls within the
known values of the enum os_dirent_t.  With clang-3.8 testing this value
as being &gt;= 0 results in a warning as it will always be true.  This
assumes of course that we are only given valid data.  Given that we want
to sanity check the input, we change this to check that it falls within
the range of the first to the last entry in the given enum.

Cc: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>bootstage: Require timer_get_boot_us() to be defined</title>
<updated>2017-06-05T18:13:04Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-05-22T11:05:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c87dc38d8f860710f5f624d9dae6cefded285b8d'/>
<id>urn:sha1:c87dc38d8f860710f5f624d9dae6cefded285b8d</id>
<content type='text'>
At present we provide a default version of this function for use by
bootstage. However it uses the system timer and therefore likely requires
driver model. This makes it impossible to time driver-model init.

Drop the function and require boards to provide their own. Add a sandbox
version also. There is a default implememtation in lib/time.c for boards
which use CONFIG_SYS_TIMER_COUNTER.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Make u-boot-sandbox.h a private header</title>
<updated>2017-06-05T15:02:32Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-05-17T14:22:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=86e748d946d4c3b0cb867fba2d9367199fb0adfe'/>
<id>urn:sha1:86e748d946d4c3b0cb867fba2d9367199fb0adfe</id>
<content type='text'>
Rather than including this arch-specific header file in common.h, include
it from within sandbox's u-boot.h header.

Also drop the comment about something to be fixed.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Add a way to reset sandbox state for tests</title>
<updated>2017-06-01T13:03:09Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-05-19T02:09:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=34b744beb866c9ae660f2851f9776f80e165d421'/>
<id>urn:sha1:34b744beb866c9ae660f2851f9776f80e165d421</id>
<content type='text'>
Running a new test should reset the sandbox state to avoid tests
interferring with each other. Move the existing state-reset code into a
function so it can be used from tests.

Also update the code to reset the SPI devices and adjust the test code to
call it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dm: blk: Improve block device claiming</title>
<updated>2017-06-01T13:03:05Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-04-24T02:02:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e48eeb9ea3aed67e4bda94c65a7f13e8672a3501'/>
<id>urn:sha1:e48eeb9ea3aed67e4bda94c65a7f13e8672a3501</id>
<content type='text'>
The intention with block devices is that the device number (devnum field
in its descriptor) matches the alias of its parent device. For example,
with:

	aliases {
		mmc0 = "/sdhci@700b0600";
		mmc1 = "/sdhci@700b0400";
	}

we expect that the block devices for mmc0 and mmc1 would have device
numbers of 0 and 1 respectively.

Unfortunately this does not currently always happen. If there is another
MMC device earlier in the driver model data structures its block device
will be created first. It will therefore get device number 0 and mmc0
will therefore miss out. In this case the MMC device will have sequence
number 0 but its block device will not.

To avoid this, allow a device to request a device number and bump any
existing device number that is using it. This all happens during the
binding phase so it is safe to change these numbers around. This allows
device numbers to match the aliases in all circumstances.

Add a test to verify the behaviour.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dm: Use dm.h header when driver mode is used</title>
<updated>2017-06-01T12:57:52Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-05-17T23:18:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9d922450aa9944ecf8c249c892078cda80f40e02'/>
<id>urn:sha1:9d922450aa9944ecf8c249c892078cda80f40e02</id>
<content type='text'>
This header includes things that are needed to make driver build. Adjust
existing users to include that always, even if other dm/ includes are
present

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dm: test: Add tests for the generic PHY uclass</title>
<updated>2017-05-09T18:14:16Z</updated>
<author>
<name>Jean-Jacques Hiblot</name>
<email>jjhiblot@ti.com</email>
</author>
<published>2017-04-24T09:51:28Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=86322f5982206f431ee4678a74182859c249aac4'/>
<id>urn:sha1:86322f5982206f431ee4678a74182859c249aac4</id>
<content type='text'>
Those tests check:
- the ability for a phy-user to get a phy based on its name or its index
- the ability of a phy device (provider) to manage multiple ports
- the ability to perform operations on the phy (init,deinit,on,off)
- the behavior of the uclass when optional operations are not implemented

Signed-off-by: Jean-Jacques Hiblot &lt;jjhiblot@ti.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dm: Simple Watchdog uclass</title>
<updated>2017-05-08T15:57:30Z</updated>
<author>
<name>maxims@google.com</name>
<email>maxims@google.com</email>
</author>
<published>2017-04-17T19:00:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0753bc2d30d7ca4a0ea4ef7f97083961c3a9d0e0'/>
<id>urn:sha1:0753bc2d30d7ca4a0ea4ef7f97083961c3a9d0e0</id>
<content type='text'>
This is a simple uclass for Watchdog Timers. It has four operations:
start, restart, reset, stop. Drivers must implement start, restart and
stop operations, while implementing reset is optional: It's default
implementation expires watchdog timer in one clock tick.

Signed-off-by: Maxim Sloyko &lt;maxims@google.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dm: sandbox: pwm: Add a basic pwm test</title>
<updated>2017-04-27T20:49:02Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-04-17T03:01:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=43b41566f72c3ff1074fe686f37227ebe33e11f9'/>
<id>urn:sha1:43b41566f72c3ff1074fe686f37227ebe33e11f9</id>
<content type='text'>
Unfortunately a test for the PWM uclass was not included when it was
submitted. This was noticed when trying to add more functionality:

   http://patchwork.ozlabs.org/patch/748172/

Add a simple test to get us started.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Add some test LEDs</title>
<updated>2017-04-15T01:38:57Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2017-04-10T17:34:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a89c3a04bcb416102eaa0b7c398209dbc1c796a2'/>
<id>urn:sha1:a89c3a04bcb416102eaa0b7c398209dbc1c796a2</id>
<content type='text'>
Add some LEDs to the standard sandbox device tree.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Ziping Chen &lt;techping.chan@gmail.com&gt;
</content>
</entry>
</feed>
