Re: ASoC audio fabric OF bindings RFC. was: Re: ASoC MPC5xxx PSC AC97 audio driver

[Mark Brown <broonie@opensource.wolfsonmicro.com>]

On Mon, Sep 12, 2011 at 03:59:05PM +0200, David Jander wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> > Note the "dynamic" bit - the configuration changes at runtime.
> > Describing the hardware for something like a modern smartphone isn't
> > particularly useful due to the flexibility, there are too many different
> > ways of configuring the system and we need code to acutally take those
> > decision.

> Ok, but you could still describe the hardwired part of it (Audio muxes,
> codecs, busses and physical interfaces). Isn't that what OF is all about?
> In our case, its just a simple AC97 codec connected to a simple AC97 bus.
> Sounds like total overkill having to write a "fabric driver" for this....
> while there are already quite a few that are all 99% the same!

I'm not sure I understand what you are talking about.  As I've already
said at least once having a *machine* driver which covers multiple
machines is absolutely OK.  We already have several such drivers in
kernel.

*Please* look at the existing code and read what I'm saying, and ideally
also read the prior discussions on this topic.  Please also try to avoid
inventing your own techncial terms.  It's enormously repetitive and not
terribly useful to have to go through all this stuff from square one
every single time someone looks at this stuff.

> > > > The plan is to push the device trees out of the kernel into a separate
> > > > repository.

> > > Good idea.... but where should such a repository be hosted?

> > Still an open issue.

> Seems like its hard to find a vendor- and OS-neutral entity to host this?
> OpenBIOS maybe?

More a problem of deciding which of the many available options to
choose.