From: David Jander <david.jander@protonic.nl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
alsa-devel@alsa-project.org, lrg@ti.com,
devicetree-discuss@lists.ozlabs.org, torbenh <torbenh@gmx.de>
Subject: Re: ASoC audio fabric OF bindings RFC. was: Re: ASoC MPC5xxx PSC AC97 audio driver
Date: Mon, 12 Sep 2011 08:31:58 +0200 [thread overview]
Message-ID: <20110912083158.29d9e1fe@archvile> (raw)
In-Reply-To: <20110909163714.GA4302@sirena.org.uk>
On Fri, 9 Sep 2011 17:37:14 +0100
Mark Brown <broonie@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.
Sorry ;-)
> > 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?
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2011-09-12 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110908121600.267dee07@archvile>
[not found] ` <CAKON4OzsMd0T6KyDK_5P_pz8R5Pax+Bd+f5+00cO5E0OMCYQpQ@mail.gmail.com>
[not found] ` <20110908124529.520c1388@archvile>
[not found] ` <CAKON4OwvYy6Dy-MfHT90syPyAUcTVRXqXca-qAVjk-KWkak53A@mail.gmail.com>
[not found] ` <20110908163231.4b721973@archvile>
[not found] ` <20110908184441.GD16989@siel.b>
[not found] ` <20110909082844.3dbf0e72@archvile>
2011-09-09 10:02 ` ASoC audio fabric OF bindings RFC. was: Re: ASoC MPC5xxx PSC AC97 audio driver David Jander
2011-09-09 16:37 ` Mark Brown
2011-09-12 6:31 ` David Jander [this message]
2011-09-12 11:09 ` Mark Brown
2011-09-12 12:55 ` David Jander
2011-09-12 13:19 ` Mark Brown
2011-09-12 13:59 ` David Jander
2011-09-12 14:52 ` Mark Brown
2011-09-12 19:48 ` Grant Likely
2011-09-13 6:31 ` David Jander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110912083158.29d9e1fe@archvile \
--to=david.jander@protonic.nl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=lrg@ti.com \
--cc=torbenh@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).