u-boot.git/include/dm/uclass.h, branch v2015.04

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

dm: core: Allow uclasses to specify private data for a device's children

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

In many cases the per-child private data for a device's children is defined
by the uclass rather than the individual driver. For example, a SPI bus
needs to store information about each of its children, but all SPI drivers
store the same information. It makes sense to allow the uclass to define
this data.

If the driver provides a size value for its per-child private data, then use
it. Failng that, fall back to that provided by the uclass.

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

dm: core: Add a flag to control sequence numbering

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

At present we try to use the 'reg' property and device tree aliases to give
devices a sequence number. The 'reg' property is often actually a memory
address, so the sequence numbers thus-obtained are not useful. It would be
better if the devices were just sequentially numbered in that case. In fact
neither I2C nor SPI use this feature, so drop it.

Some devices need us to look up an alias to number them within the uclass.
Add a flag to control this, so it is not done unless it is needed.

Adjust the tests to test this new behaviour.

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

dm: core: Allow uclasses to specify platdata for a device's children

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

In many cases the child platform data for a device's children is defined by
the uclass rather than the individual devices. For example, a SPI bus needs
to know the chip select and speed for each of its children. It makes sense
to allow this information to be defined the SPI uclass rather than each
individual driver.

If the device provides a size value for its child platdata, then use it.
Failng that, fall back to that provided by the uclass.

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

dm: core: Improve comments for uclass_first/next_device()

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

Mention that the devices are probed ready for use.

Signed-off-by: Simon Glass

dm: include from platdata.h and uclass.h

2014-10-22T16:32:17+00:00

The header files include/dm/platdata.h and include/dm/uclass.h
use ll_entry_declare(); therefore they depend on
include/linker_lists.h.

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

dm: Tidy up some header file comments

2014-07-23T13:07:26+00:00

Fix up the style of a few comments and add/clarify a few others.

Signed-off-by: Simon Glass

dm: Allow a device to be found by its FDT offset

2014-07-23T13:07:25+00:00

Each device that was bound from a device tree has an node that caused it to
be bound. Add functions that find and return a device based on a device tree
offset.

Signed-off-by: Simon Glass

dm: Introduce device sequence numbering

2014-07-23T13:07:25+00:00

In U-Boot it is pretty common to number devices from 0 and access them
on the command line using this numbering. While it may come to pass that
we will move away from this numbering, the possibility seems remote at
present.

Given that devices within a uclass will have an implied numbering, it
makes sense to build this into driver model as a core feature. The cost
is fairly small in terms of code and data space.

With each uclass having numbered devices we can ask for SPI port 0 or
serial port 1 and receive a single device.

Devices typically request a sequence number using aliases in the device
tree. These are resolved when the device is probed, to deal with conflicts.
Sequence numbers need not be sequential and holes are permitted.

At present there is no support for sequence numbers using static platform
data. It could easily be added to 'struct driver_info' if needed, but it
seems better to add features as we find a use for them, and the use of -1
to mean 'no sequence' makes the default value somewhat painful.

Signed-off-by: Simon Glass