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

dm: core: Extend struct udevice by '.uclass_platdata' field.

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

This commit adds 'uclass_platdata' field to 'struct udevice', which
can be automatically allocated at bind. The allocation size is defined
in 'struct uclass_driver' as 'per_device_platdata_auto_alloc_size'.

New device's flag is added: DM_FLAG_ALLOC_UCLASS_PDATA, which is used
for memory freeing at device unbind method.

As for other udevice's fields, a complementary function is added:
- dev_get_uclass_platdata()

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

dm: core: Convert driver_bind() to use const

2015-04-18T17:11:19+00:00

The driver is not modified by driver model, so update driver_bind() to
recognise that.

Signed-off-by: Simon Glass 
Reviewed-by: Marek Vasut

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: Allow parents to have platform data for their children

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

For buses it is common for parents to need to know the address of the child
on the bus, the bus speed to use for that child, and other information. This
can be provided in platform data attached to each child.

Add driver model support for this, including auto-allocation which can be
requested using a new property to specify the size of the data.

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

dm: core: Allocate platform data when binding a device

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

When using allocated platform data, allocate it when we bind the device.
This makes it possible to fill in this information before the device is
probed.

This fits with the platform data model (when not using device tree),
since platform data exists at bind-time.

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

dm: Allow device removal features to be dropped

2014-11-21T07:13:02+00:00

For SPL we don't expect to need to remove a device. Save some code space
by dropping this feature. The board config can define
CONFIG_DM_DEVICE_REMOVE if this is in fact needed.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini