u-boot.git/include/dm/uclass.h, branch v2018.03 Unnamed repository; edit this file 'description' to name the repository. dm: core: Add a function to look up a uclass by name 2018-02-03T17:08:40+00:00 Simon Glass sjg@chromium.org 2017-12-28T20:14:15+00:00 6e43d1b19982b1756b7c607569d1778e556d6577 Each uclass has a driver name which we can use to look up the uclass. This is useful for logging, where the uclass ID is used as the category. Add a function to handle this, as well as a test. Signed-off-by: Simon Glass <sjg@chromium.org> 
Each uclass has a driver name which we can use to look up the uclass. This
is useful for logging, where the uclass ID is used as the category.

Add a function to handle this, as well as a test.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: fix typo falback 2018-01-21T17:01:02+00:00 Heinrich Schuchardt xypron.glpk@gmx.de 2017-12-17T17:19:43+00:00 fa9335a89c61837414e3db27bb85c3c459803ff0 %s/falback/fallback/g Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org> 
%s/falback/fallback/g

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
dm: core: Add uclass_first/next_device_check() 2017-07-11T16:08:19+00:00 Simon Glass sjg@chromium.org 2017-04-24T02:10:45+00:00 95ce385a4ad0bb0d0a20f68b2a1f2451584bf3ff 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> 
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>
dm: core: Clarify uclass_first/next_device() comments 2017-07-11T16:08:19+00:00 Simon Glass sjg@chromium.org 2017-04-24T02:10:43+00:00 30a570a983c77cddda314cdb2bc5763112338746 These are not as clear as they could be. Tidy them up a bit. Also fix a tiny code-style nit. Signed-off-by: Simon Glass <sjg@chromium.org> 
These are not as clear as they could be. Tidy them up a bit. Also fix a
tiny code-style nit.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Add a way to find a device by ofnode 2017-06-01T13:03:08+00:00 Simon Glass sjg@chromium.org 2017-05-19T02:09:09+00:00 40bb637dae10abff32ca2d952fd443e0e09fd524 Add a function which looks up a device by its node (either in live tree or flat tree). Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a function which looks up a device by its node (either in live tree
or flat tree).

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Add a function to get a uclass name 2016-10-11T03:55:33+00:00 Simon Glass sjg@chromium.org 2016-10-06T02:42:13+00:00 0a5f6f869f1c2c6e9f75d83203754937014cbe47 It is useful in debug() statements to display the name of the uclass for a device. Add a simple function to provide this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> 
It is useful in debug() statements to display the name of the uclass for a
device. Add a simple function to provide this.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
dm: core: Add a way to find a device by its driver 2016-07-26T02:46:43+00:00 Simon Glass sjg@chromium.org 2016-07-17T21:23:15+00:00 c57f806bf2e745c4273dc33c9827781cff46427c Some SoCs have a single clock device. Provide a way to find it given its driver name. This is handled by the linker so will fail if the name is not found, avoiding strange errors when names change and do not match. It is also faster than a string comparison. Signed-off-by: Simon Glass <sjg@chromium.org> 
Some SoCs have a single clock device. Provide a way to find it given its
driver name. This is handled by the linker so will fail if the name is not
found, avoiding strange errors when names change and do not match. It is
also faster than a string comparison.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Add uclass_first_device_err() to return a valid device 2016-03-14T21:34:50+00:00 Simon Glass sjg@chromium.org 2016-02-11T20:23:25+00:00 b06750501f5c0eef7fef094f13d2f2e313c60b79 A common pattern is to call uclass_first_device() and then check if it actually returns a device. Add a new function which does this, returning an error if there are no devices in that uclass. Signed-off-by: Simon Glass <sjg@chromium.org> 
A common pattern is to call uclass_first_device() and then check if it
actually returns a device. Add a new function which does this, returning
an error if there are no devices in that uclass.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Add safe device iteration macros 2015-11-20T03:27:51+00:00 Simon Glass sjg@chromium.org 2015-11-09T06:47:52+00:00 7aeac5bc8c5903b8d27188a21b39f0b2c4bd13c1 Add iteration macros which support unbinding a device within the loop. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add iteration macros which support unbinding a device within the loop.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: simplify uclass_foreach_dev() implementation 2015-08-31T13:56:44+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2015-08-10T16:09:43+00:00 71f1e3f19d26c7956de5c37035478fcaa9e979e7 This can be simply written with list_for_each_entry(), maybe this macro was not necessary in the first place. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Simon Glass <sjg@chromium.org> 
This can be simply written with list_for_each_entry(), maybe
this macro was not necessary in the first place.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Simon Glass <sjg@chromium.org>