Searched hist:"95 ce385a4ad0bb0d0a20f68b2a1f2451584bf3ff" (Results 1 – 3 of 3) sorted by relevance
| /rk3399_rockchip-uboot/test/dm/ |
| H A D | test-fdt.c | 95ce385a4ad0bb0d0a20f68b2a1f2451584bf3ff Mon Apr 24 02:10:45 UTC 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>
|
| /rk3399_rockchip-uboot/include/dm/ |
| H A D | uclass.h | 95ce385a4ad0bb0d0a20f68b2a1f2451584bf3ff Mon Apr 24 02:10:45 UTC 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>
|
| /rk3399_rockchip-uboot/drivers/core/ |
| H A D | uclass.c | 95ce385a4ad0bb0d0a20f68b2a1f2451584bf3ff Mon Apr 24 02:10:45 UTC 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>
|