[RFC PATCH 0/4] PLATFORM: Support for async platform_data

[Andy Green]

The following series adds two apis which allow board definition
files to register bindings between device paths (like usb1/1-1/1-1.1)
and platform data.  It's for use in the case that there are hardwired
chips on a board that need to be configured from the board definition
file, but the creation of the device is asynchronous to the boot
action.  Beagle XM and Panda are both real-world examples where there
are hardwired chips on the PCB with fixed interconnect using USB
protocol that can benefit from platform_data for the usual reasons.

This patcheset is the platform part of a three part set which when
taken as a whole, allows the board definition file to configure
USB-wired onboard network interface assets.

---

Andy Green (4):
      PLATFORM: Add some documentation to platform docs about async platform_data
      PLATFORM: Introduce async platform_data attach api
      PLATFORM: Introduce registration function for async platform data maps
      PLATFORM: introduce structure to bind async platform data to a dev path name


 Documentation/driver-model/platform.txt |   25 +++++++++
 drivers/base/platform.c                 |   91 +++++++++++++++++++++++++++++++
 include/linux/platform_device.h         |   22 +++++++
 3 files changed, 138 insertions(+), 0 deletions(-)

-- 
Signature
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/