dac8db2ce6
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> |
||
|---|---|---|
| .. | ||
| dfu | ||
| dm | ||
| fs | ||
| image | ||
| stdint | ||
| trace | ||
| ums | ||
| vboot | ||
| cmd_repeat.sh | ||
| command_ut.c | ||
| common.sh | ||
| compression.c | ||
| Makefile | ||