Searched hist:dac8db2ce66944828e441cccf25703b262a256cd (Results 1 – 4 of 4) sorted by relevance
| /rk3399_rockchip-uboot/drivers/core/ |
| H A D | device-remove.c | dac8db2ce66944828e441cccf25703b262a256cd Sun Jan 25 15:27:06 UTC 2015 Simon Glass <sjg@chromium.org> dm: core: Allow uclasses to specify private data for a device's children
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 <sjg@chromium.org>
Reviewed-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
|
| H A D | device.c | dac8db2ce66944828e441cccf25703b262a256cd Sun Jan 25 15:27:06 UTC 2015 Simon Glass <sjg@chromium.org> dm: core: Allow uclasses to specify private data for a device's children
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 <sjg@chromium.org>
Reviewed-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
|
| /rk3399_rockchip-uboot/test/dm/ |
| H A D | bus.c | dac8db2ce66944828e441cccf25703b262a256cd Sun Jan 25 15:27:06 UTC 2015 Simon Glass <sjg@chromium.org> dm: core: Allow uclasses to specify private data for a device's children
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 <sjg@chromium.org>
Reviewed-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
|
| /rk3399_rockchip-uboot/include/dm/ |
| H A D | uclass.h | dac8db2ce66944828e441cccf25703b262a256cd Sun Jan 25 15:27:06 UTC 2015 Simon Glass <sjg@chromium.org> dm: core: Allow uclasses to specify private data for a device's children
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 <sjg@chromium.org>
Reviewed-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
|