u-boot.git/doc/driver-model, branch v2015.01-rc2

dm: Update documentation to include CONFIG_DM... options

2014-11-21T07:14:27+00:00

Add documentation for the various driver model options that are now
available.

Signed-off-by: Simon Glass

test: dm: Add additional GPIO tests

2014-10-24T01:29:53+00:00

Add tests for gpio_requestf() and for memory leaks.

Signed-off-by: Simon Glass

dm: gpio: Add gpio_requestf() helper for printf() strings

2014-10-24T01:29:52+00:00

Add a helper which permits a printf()-style format string for the requester
string.

Signed-off-by: Simon Glass

test: dm: Update GPIO tests for new gpio_request() method

2014-10-24T01:29:52+00:00

Now that gpio_request() is handled by the uclass, updates the tests
accordingly.

Signed-off-by: Simon Glass

dm: spi: Add documentation on how to convert over SPI drivers

2014-10-22T16:36:49+00:00

This README is intended to help maintainers move their SPI drivers over to
driver model. It works through the required steps with an example.

Signed-off-by: Simon Glass 
Reviewed-by: Jagannadha Sutradharudu Teki

dm: core: Add a clarifying comment on struct udevice's seq member

2014-10-22T16:36:46+00:00

The sequence number is unique within the uclass, so state this clearly.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki

dm: core: Add functions for iterating through device children

2014-10-22T16:36:45+00:00

Buses need to iterate through their children in some situations. Add a few
functions to make this easy.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki

dm: Add child_pre_probe() and child_post_remove() methods

2014-07-23T13:08:37+00:00

Some devices (particularly bus devices) must track their children, knowing
when a new child is added so that it can be set up for communication on the
bus.

Add a child_pre_probe() method to provide this feature, and a corresponding
child_post_remove() method.

Signed-off-by: Simon Glass

dm: Introduce per-child data for devices

2014-07-23T13:08:37+00:00

Some device types can have child devices and want to store information
about them. For example a USB flash stick attached to a USB host
controller would likely use this space. The controller can hold
information about the USB state of each of its children.

The data is stored attached to the child device in the 'parent_priv'
member. It can be auto-allocated by dm when the child is probed. To
do this, add a per_child_auto_alloc_size value to the parent driver.

Signed-off-by: Simon Glass

dm: Add functions to access a device's children

2014-07-23T13:08:37+00:00

Devices can have childen that can be addressed by a simple index, the
sequence number or a device tree offset. Add functions to access a child
in each of these ways.

The index is typically used as a fallback when the sequence number is not
available. For example we may use a serial UART with sequence number 0 as
the console, but if no UART has sequence number 0, then we can fall back
to just using the first UART (index 0).

The device tree offset function is useful for buses, where they want to
locate one of their children. The device tree can be scanned to find the
offset of each child, and that offset can then find the device.

Signed-off-by: Simon Glass