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: Mon, 12 Sep 2011 12:09:50 +0100 [thread overview]
Message-ID: <20110912110950.GD2953@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110912083158.29d9e1fe@archvile>
On Mon, Sep 12, 2011 at 08:31:58AM +0200, David Jander wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > 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
This is generally considered a bug in the bindings, the bindings are for
cross-platform usage and should not be specific to any OS.
> 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.
Other OSs are actively using device tree.
> 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?
Eliminating board specific code for audio is not a realistic goal, the
configuration of modern audio subsystems is too complex and dynamic. It
is realistic to make machine drivers which cover broad classes of
devices with similar hardware.
> 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.
The plan is to push the device trees out of the kernel into a separate
repository.
> > 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?
Yes, it's a very basic part of AC'97.
next prev parent reply other threads:[~2011-09-12 11:09 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
2011-09-12 6:31 ` David Jander
2011-09-12 11:09 ` Mark Brown [this message]
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=20110912110950.GD2953@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox