[alsa-devel] ASoC audio fabric OF bindings RFC. was: Re: ASoC MPC5xxx PSC AC97 audio driver
david.jander at protonic.nl
Mon Sep 12 08:31:58 CEST 2011
On Fri, 9 Sep 2011 17:37:14 +0100
Mark Brown <broonie at opensource.wolfsonmicro.com> wrote:
> On Fri, Sep 09, 2011 at 12:02:16PM +0200, David Jander wrote:
> > Ok, I actually spent a while thinking about this. What about the following
> > idea:
> *Always* CC maintainers.
> > 1: By adding compatible = "alsa,cpu-dai", this DAI is marked for binding.
> This isn't really something that should go into device tree, ALSA is a
> Linux specific concept.
There are many Linux-specific details in Linux's implementation of Open
Firmware Device Trees. Right now, thanks to Linux, Open-Firmware device trees
are used for much more hardware platforms than just Oracle hardware that
probably isn't manufactured anymore and IBM Power servers. For embedded
systems for example, DT's have been used on all PowerPC platforms and is being
introduced in arch/arm right now. On all these platforms, its sole existence
is purely for running Linux with minimal board support code in the kernel.
So, why not add a few more Linux-specific bits to it, if it helps get rid of
the last bit of board-specific code?
The platforms that will use those bindings, will never have
Open-Firmware bioses in the first place, and their DT sources will be part of
the kernel source tree anyway.
> > 3: Many ac97 codecs are compatible with the generic codec driver
> > "ac97-codec".
> All should be. The only reason for specific drivers is to enable
> additional non-standard functionality.
I was being careful.
> > 4: Don't know if this is the right way to work the codec DAI name in. See
> > the next note:
> What we should really be doing here is to autodiscover by reading the ID
> registers in the device. That needs generic AC'97 bus work which we
> don't have right now.
Seems reasonable, but is correct autodiscovery really possible for all
configurations and all DAI-codec combinations?
More information about the Alsa-devel