All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:59:05 +0200	[thread overview]
Message-ID: <20110912155905.35cda85b@archvile> (raw)
In-Reply-To: <20110912131924.GB5887@opensource.wolfsonmicro.com>

On Mon, 12 Sep 2011 14:19:24 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> On Mon, Sep 12, 2011 at 02:55:07PM +0200, David Jander wrote:
> > Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> 
> > > Other OSs are actively using device tree.
> 
> > Interesting. I wasn't aware of "actively using". Sure, there's MacOS-X-ppc,
> > IBM AIX, Oracle Solaris.... and I just discovered that Free-/OpenBSD also
> > use them.
> 
> *BSD are the main ones to consider here.
> 
> > > Eliminating board specific code for audio is not a realistic goal, the
> > > configuration of modern audio subsystems is too complex and dynamic.  
> 
> > Why not? How complex could it be in order to not be able to describe it in
> > a Device-Tree in some OS-agnostic way?
> 
> 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!

> > > 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?

Best regards,

-- 
David Jander
Protonic Holland.

  reply	other threads:[~2011-09-12 13:58 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
2011-09-12 12:55                     ` David Jander
2011-09-12 13:19                       ` Mark Brown
2011-09-12 13:59                         ` David Jander [this message]
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=20110912155905.35cda85b@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 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.