From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Jander <david.jander@protonic.nl>
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: Fri, 9 Sep 2011 17:37:14 +0100 [thread overview]
Message-ID: <20110909163714.GA4302@sirena.org.uk> (raw)
In-Reply-To: <20110909120216.263eeb54@archvile>
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.
> 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.
> 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.
next prev parent reply other threads:[~2011-09-09 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110908121600.267dee07@archvile>
2011-09-08 10:28 ` ASoC MPC5xxx PSC AC97 audio driver jonsmirl
[not found] ` <20110908124529.520c1388@archvile>
2011-09-08 10:55 ` jonsmirl
2011-09-08 14:32 ` David Jander
2011-09-08 17:52 ` jonsmirl
2011-09-09 6:48 ` David Jander
2011-09-08 18:44 ` torbenh
2011-09-09 6:28 ` David Jander
2011-09-09 10:02 ` ASoC audio fabric OF bindings RFC. was: " David Jander
2011-09-09 16:37 ` Mark Brown [this message]
2011-09-12 6:31 ` David Jander
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=20110909163714.GA4302@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.jander@protonic.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.