All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>,
	Jon Smirl <jonsmirl@gmail.com>,
	PowerPC dev list <Linuxppc-dev@ozlabs.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: Revisited, audio codec device tree entries.
Date: Mon, 26 Nov 2007 09:51:06 -0600	[thread overview]
Message-ID: <474AEB6A.40408@freescale.com> (raw)
In-Reply-To: <20071120005941.GC3126@localhost.localdomain>

David Gibson wrote:

> 	1) We have a "universal" device-tree-based fabric driver which
> parses all the above-described interconnection information in the
> device tree and handles any situation.  Cool, but probably a lot of
> work and fiddly to get right.

Definitely a lot of work.  I suggest we wait until there are a few PowerPC ASOC 
v2 audio drivers in the kernel before we even consider this.  And it may not 
even be possible.  I can easily imagine situations where we need board-specific 
code that belongs in a machine-specific fabric driver.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2007-11-26 15:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 18:10 Revisited, audio codec device tree entries Jon Smirl
2007-11-18 20:16 ` Segher Boessenkool
2007-11-18 21:49   ` Jon Smirl
2007-11-18 22:46     ` Matt Sealey
2007-11-18 23:31       ` Matt Sealey
2007-11-18 23:47         ` Jon Smirl
2007-11-19  0:12         ` David Gibson
2007-11-19  0:22           ` Jon Smirl
2007-11-19 12:48           ` Segher Boessenkool
2007-11-20  0:22             ` David Gibson
2007-11-19 16:31           ` Matt Sealey
2007-11-19 17:05             ` Scott Wood
2007-11-19 18:55               ` Grant Likely
2007-11-20  0:33             ` David Gibson
2007-11-19 12:07         ` Segher Boessenkool
2007-11-19 16:58           ` Matt Sealey
2007-11-20  1:42             ` David Gibson
2007-11-19 14:57       ` Timur Tabi
2007-11-19 15:33         ` Jon Smirl
2007-11-19 15:02 ` Timur Tabi
2007-11-19 15:15   ` Jon Loeliger
2007-11-19 15:33   ` Grant Likely
2007-11-19 16:00     ` Jon Smirl
2007-11-19 16:31       ` Grant Likely
2007-11-19 16:51         ` Jon Smirl
2007-11-19 17:33           ` Grant Likely
2007-11-19 19:20             ` Jon Smirl
2007-11-19 19:28               ` Grant Likely
2007-11-20  0:59                 ` David Gibson
2007-11-26 15:51                   ` Timur Tabi [this message]
2007-11-26 16:38                     ` Jon Smirl
2007-11-26 16:40                       ` Timur Tabi
2007-11-19 16:45       ` Timur Tabi
2007-11-19 22:37         ` Jon Smirl
2007-11-19 16:44     ` Timur Tabi
2007-11-19 16:53       ` Grant Likely
2007-11-19 16:55       ` Jon Smirl
2007-11-19 15:37   ` Jon Smirl
2007-11-19 15:42     ` Grant Likely

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=474AEB6A.40408@freescale.com \
    --to=timur@freescale.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jonsmirl@gmail.com \
    /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.