u-boot.git/drivers/core/uclass.c, branch v2015.07

dm: core: Correct bug introduced in uclass_first/next_device()

2015-04-28T22:49:03+00:00

These functions now rely on uclass_find_first/next_device() and assume that
they will either return failure (-ve error code) or a device. In fact,
coming to the end of a list is not considered failure and they return 0
in that case.

The logic to deal with this was replaced in commit acb9ca2a with just using
uclass_get_device_tail(). Add back the missing logic. This bug was
caught by unit tests but since they were broken for other reasons at the
time, this was not noticed.

Signed-off-by: Simon Glass

dm: core: Remove unbind operations when not required

2015-04-23T15:05:52+00:00

The CONFIG_DM_DEVICE_REMOVE option takes out code related to removing
devices. It should also remove the 'unbind' code since if we cannot
remove we probably don't need to unbind.

Signed-off-by: Simon Glass

dm: core: Handle recursive unbinding of uclass devices

2015-04-22T17:13:17+00:00

Since a device can have children in the same uclass as itself, we need
to handle unbinding carefully: we must allow that unbinding a device in a
uclass may cause another device in the same uclass to be unbound.

Adjust the code to cope.

Signed-off-by: Simon Glass 
Reviewed-by: Joe Hershberger 
Tested-by: Joe Hershberger

dm: core: remove type 'static' of function uclass_get_device_tail()

2015-04-22T17:03:15+00:00

Uclass API provides a few functions for get/find the device.
To provide a complete function set of uclass-internal functions,
for use by the drivers, the function uclass_get_device_tail()
should be non-static.

Signed-off-by: Przemyslaw Marczak 
Cc: Simon Glass 
Acked-by: Simon Glass

dm: core: uclass: add function: uclass_get_device_by_name()

2015-04-22T17:03:15+00:00

This commit extends the driver model uclass's API by function:
- uclass_get_device_by_name()

And this function returns the device if:
- uclass with given ID, exists,
- device with exactly given name(dev->name), exists,
- device probe, doesn't return an error.

The returned device is activated and ready to use.

Note:
This function returns the first device, which name is equal
to the given one. This means, that using this function you must
assume, that the device name is unique in the given uclass's ID
device list.

Signed-off-by: Przemyslaw Marczak 
Cc: Simon Glass 
Acked-by: Simon Glass

dm: core: uclass: add function: uclass_find_device_by_name()

2015-04-22T17:03:15+00:00

This commit extends the driver model uclass's API by function:
- uclass_find_device_by_name()

And this function returns the device if:
- uclass with given ID, exists,
- device with exactly given name(dev->name), exists.

The returned device is not activated - need to be probed before use.

Note:
This function returns the first device, which name is equal
to the given one. This means, that using this function you must
assume, that the device name is unique in the given uclass's ID
device list.

uclass-internal.h: cleanup - move the uclass_find_device_by_seq()
declaration and description, near the other uclass_find*() functions.

Signed-off-by: Przemyslaw Marczak 
Cc: Simon Glass 
Acked-by: Simon Glass

dm: core: add internal functions for getting the device without probe

2015-04-22T17:03:14+00:00

This commit extends the uclass-internal functions by:
- uclass_find_first_device()
- uclass_find_next_device()
For both functions, the returned device is not probed.

After some cleanup, the above functions are called by:
- uclass_first_device()
- uclass_next_device()
for which, the returned device is probed.

Signed-off-by: Przemyslaw Marczak 
Cc: Simon Glass 
Acked-by: Simon Glass

dm: core: Add a uclass pre_probe() method for devices

2015-04-17T01:27:42+00:00

Some uclasses want to set up a device before it is probed. Add a method
for this.

An example is with PCI, where a PCI uclass wants to set up its private
data for later use. This allows the device's uclass() method to make calls
whcih use that data (for example, read PCI memory regions from device
tree, set up bus numbers).

Signed-off-by: Simon Glass

dm: core: Allow uclass to set up a device's child before it is probed

2015-01-30T00:09:56+00:00

Some buses need to set up their devices before they can be used. This setup
may well be common to all buses in a particular uclass. Support a common
pre-probe method for the uclass, called before any bus devices are probed.

Signed-off-by: Simon Glass 
Reviewed-by: Masahiro Yamada

dm: core: Allow the uclass to set up a device's child after binding

2015-01-30T00:09:56+00:00

For buses, after a child is bound, allow the uclass to perform some
processing. This can be used to figure out the address of the child (e.g.
the chip select for SPI slaves) so that it is ready to be probed.

This avoids bus drivers having to repeat the same process, which really
should be done by the uclass, since it is common.

Signed-off-by: Simon Glass 
Reviewed-by: Masahiro Yamada