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

dm: introduce dev_get_addr interface

2015-02-12T22:17:29+00:00

Abstracting dev_get_addr can improve drivers that want to
get device's address.

Signed-off-by: Peng Fan 
Acked-by: Igor Grinberg 
Acked-by: Simon Glass

dm: core: Add a function to get a device's uclass ID

2015-01-30T00:09:55+00:00

This is useful to check which uclass a device is in.

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

dm: core: Add a post_bind method for parents

2015-01-30T00:09:55+00:00

Allow parent drivers to be called when a new child is bound to them. This
allows a bus to set up information it needs for that child.

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

dm: core: Allow parents to have platform data for their children

2015-01-30T00:09:54+00:00

For buses it is common for parents to need to know the address of the child
on the bus, the bus speed to use for that child, and other information. This
can be provided in platform data attached to each child.

Add driver model support for this, including auto-allocation which can be
requested using a new property to specify the size of the data.

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

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