[PATCH v2] ASoC: omap: convert per-board modules to platform drivers

Mark Brown broonie at opensource.wolfsonmicro.com
Thu Sep 8 19:59:04 EDT 2011


On Fri, Sep 09, 2011 at 12:01:02AM +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 08, 2011 at 03:47:31PM -0700, Mark Brown wrote:

> > What will happen for device tree is that there will be a device in the
> > device tree for the ASoC board.

> Sounds like you just solved the machine_is_xxx() problem in ASoC land too
> there.  If you're _already_ going for separate devices to describe the
> ASoC stuff on the board, then there's no reason that couldn't have already
> been done to eliminate the machine_is_xxx() usage in ASoC - rather than
> complaining about machine_is_xxx() not being a very good solution.

The problem is that someone has to manually go and add the device to
every board that needs one and people find that tedious and slightly
inelegant (especially for device tree where not everyone is entirely
happy that it's a good idea to have the node for the board when we
already have the top level machine information saying what board we're
running on).   Jassi's suggestion was that we should have some magic to
automatically generate defaults for the relevant device registrations to
sidestep these issues.



More information about the linux-arm-kernel mailing list