Searched hist:e59f458de6999b8a786da857e653db6777f675ca (Results 1 – 5 of 5) sorted by relevance
| /rk3399_rockchip-uboot/include/dm/ |
| H A D | test.h | e59f458de6999b8a786da857e653db6777f675ca Wed Jul 23 12:55:20 UTC 2014 Simon Glass <sjg@chromium.org> dm: Introduce per-child data for devices
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 <sjg@chromium.org>
|
| H A D | device.h | e59f458de6999b8a786da857e653db6777f675ca Wed Jul 23 12:55:20 UTC 2014 Simon Glass <sjg@chromium.org> dm: Introduce per-child data for devices
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 <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/test/dm/ |
| H A D | bus.c | e59f458de6999b8a786da857e653db6777f675ca Wed Jul 23 12:55:20 UTC 2014 Simon Glass <sjg@chromium.org> dm: Introduce per-child data for devices
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 <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | README.txt | e59f458de6999b8a786da857e653db6777f675ca Wed Jul 23 12:55:20 UTC 2014 Simon Glass <sjg@chromium.org> dm: Introduce per-child data for devices
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 <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/drivers/core/ |
| H A D | device.c | e59f458de6999b8a786da857e653db6777f675ca Wed Jul 23 12:55:20 UTC 2014 Simon Glass <sjg@chromium.org> dm: Introduce per-child data for devices
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 <sjg@chromium.org>
|