Home
last modified time | relevance | path

Searched hist:"95 ce385a" (Results 1 – 3 of 3) sorted by relevance

/openbmc/u-boot/test/dm/
H A Dtest-fdt.c95ce385a Sun Apr 23 21:10:45 CDT 2017 Simon Glass <sjg@chromium.org> dm: core: Add uclass_first/next_device_check()

Sometimes it is useful to iterate through all devices in a uclass and
skip over those which do not work correctly (e.g fail to probe). Add two
new functions to provide this feature.

The caller must check the return value each time to make sure that the
device is valid. But the device pointer is always returned.

Signed-off-by: Simon Glass <sjg@chromium.org>
/openbmc/u-boot/include/dm/
H A Duclass.h95ce385a Sun Apr 23 21:10:45 CDT 2017 Simon Glass <sjg@chromium.org> dm: core: Add uclass_first/next_device_check()

Sometimes it is useful to iterate through all devices in a uclass and
skip over those which do not work correctly (e.g fail to probe). Add two
new functions to provide this feature.

The caller must check the return value each time to make sure that the
device is valid. But the device pointer is always returned.

Signed-off-by: Simon Glass <sjg@chromium.org>
/openbmc/u-boot/drivers/core/
H A Duclass.c95ce385a Sun Apr 23 21:10:45 CDT 2017 Simon Glass <sjg@chromium.org> dm: core: Add uclass_first/next_device_check()

Sometimes it is useful to iterate through all devices in a uclass and
skip over those which do not work correctly (e.g fail to probe). Add two
new functions to provide this feature.

The caller must check the return value each time to make sure that the
device is valid. But the device pointer is always returned.

Signed-off-by: Simon Glass <sjg@chromium.org>