Searched hist:daac3bfe (Results 1 – 4 of 4) sorted by relevance
| /openbmc/u-boot/include/dm/ |
| H A D | device-internal.h | daac3bfe Wed May 11 16:26:24 CDT 2016 Stephen Warren <swarren@nvidia.com> dm: allow setting driver_data before/during bind
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which instantiates child devices
for each of its GPIO ports, yet supports two different HW instances each
with a different set of ports, and identified by the udevice_id .data
field.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
|
| /openbmc/u-boot/drivers/core/ |
| H A D | lists.c | daac3bfe Wed May 11 16:26:24 CDT 2016 Stephen Warren <swarren@nvidia.com> dm: allow setting driver_data before/during bind
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which instantiates child devices
for each of its GPIO ports, yet supports two different HW instances each
with a different set of ports, and identified by the udevice_id .data
field.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
|
| H A D | device.c | daac3bfe Wed May 11 16:26:24 CDT 2016 Stephen Warren <swarren@nvidia.com> dm: allow setting driver_data before/during bind
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which instantiates child devices
for each of its GPIO ports, yet supports two different HW instances each
with a different set of ports, and identified by the udevice_id .data
field.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | README.txt | daac3bfe Wed May 11 16:26:24 CDT 2016 Stephen Warren <swarren@nvidia.com> dm: allow setting driver_data before/during bind
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which instantiates child devices
for each of its GPIO ports, yet supports two different HW instances each
with a different set of ports, and identified by the udevice_id .data
field.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
|