u-boot.git/include/dm/device.h, branch v2015.01

dm: core: Add functions to find parent and OF data

2014-11-22T09:16:47+00:00

Add dev_get_parent() as a convenience to obtain the parent of a device.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini 
Acked-by: Heiko Schocher

dm: core: Allow access to the device's driver_id data

2014-11-22T09:16:45+00:00

When the device is created from a device tree node, it matches a compatible
string. Allow access to that string and the associated data.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini 
Acked-by: Heiko Schocher

dm: core: Add a clarifying comment on struct udevice's seq member

2014-10-22T16:36:46+00:00

The sequence number is unique within the uclass, so state this clearly.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki

dm: core: Allow parents to pass data to children during probe

2014-10-22T16:36:46+00:00

Buses sometimes want to pass data to their children when they are probed.
For example, a SPI bus may want to tell the slave device about the chip
select it is connected to.

Add a new function to permit the parent data to be supplied to the child.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki

dm: core: Add functions for iterating through device children

2014-10-22T16:36:45+00:00

Buses need to iterate through their children in some situations. Add a few
functions to make this easy.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki

dm: add of_match_ptr() macro

2014-10-22T16:32:17+00:00

The driver model supports two ways for passing device parameters;
Device Tree and platform_data (board file).
Each driver should generally support both of them because some
popular IPs are used on various platforms.

Assume the following scenario:
  - The driver Foo is used on SoC Bar and SoC Baz
  - The SoC Bar uses Device Tree control (CONFIG_OF_CONTROL=y)
  - The SoC Baz does not support Device Tree; uses a board file

In this situation, the device driver Foo should work with/without
the device tree control.  The driver should have .of_match and
.ofdata_to_platdata members for SoC Bar, while they are meaningless
for SoC Baz; therefore those device-tree control code should go
inside #ifdef CONFIG_OF_CONTROL.

The driver code will be like this:

  #ifdef CONFIG_OF_CONTROL
  static const struct udevice_id foo_of_match = {
          { .compatible = "foo_driver" },
          {},
  }

  static int foo_ofdata_to_platdata(struct udevice *dev)
  {
          ...
  }
  #endif

  U_BOOT_DRIVER(foo_driver) = {
          ...
          .of_match = of_match_ptr(foo_of_match),
          .ofdata_to_platdata = of_match_ptr(foo_ofdata_to_platdata),
          ...
  }

This idea has been borrowed from Linux.
(In Linux, this macro is defined in include/linux/of.h)

Signed-off-by: Masahiro Yamada 
Acked-by: Simon Glass

dm: Add child_pre_probe() and child_post_remove() methods

2014-07-23T13:08:37+00:00

Some devices (particularly bus devices) must track their children, knowing
when a new child is added so that it can be set up for communication on the
bus.

Add a child_pre_probe() method to provide this feature, and a corresponding
child_post_remove() method.

Signed-off-by: Simon Glass

dm: Introduce per-child data for devices

2014-07-23T13:08:37+00:00

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

dm: Add functions to access a device's children

2014-07-23T13:08:37+00:00

Devices can have childen that can be addressed by a simple index, the
sequence number or a device tree offset. Add functions to access a child
in each of these ways.

The index is typically used as a fallback when the sequence number is not
available. For example we may use a serial UART with sequence number 0 as
the console, but if no UART has sequence number 0, then we can fall back
to just using the first UART (index 0).

The device tree offset function is useful for buses, where they want to
locate one of their children. The device tree can be scanned to find the
offset of each child, and that offset can then find the device.

Signed-off-by: Simon Glass

dm: Tidy up some header file comments

2014-07-23T13:07:26+00:00

Fix up the style of a few comments and add/clarify a few others.

Signed-off-by: Simon Glass