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