alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC: Dynamic CODEC DAI
Date: Tue, 29 Nov 2011 13:49:14 +0000	[thread overview]
Message-ID: <20111129134913.GB26800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED42C0E.2080300@codeaurora.org>

On Mon, Nov 28, 2011 at 04:49:18PM -0800, Patrick Lai wrote:

> In CODEC driver, I will declare codec dai for each port.
> Then, I will enhance ASoC framework to take a list of CODEC DAIs and
> pass list of CODEC DAIs back to callback function such as startup,
> hw_param, prepare, trigger. I believe this approach will not require
> massive amount of change to framework.

The above is really vauge so it's hard to comment in any detail.  I'm
not sure it's worth trying to be too non-invasive, anything controlling
hardware is going to have to understand what's going on at the physical
level anyway and the host side is going to have to interoperate with the
Slimbus framework.  The core is also going to need to know about the
channel groups to allocate and destroy them as required.  It seems like
being more explicit might be easier.

Also note that the work on submitting your Silmbus driver core to
mainline appears totally stalled, there was just an initial posting but
no followup.

  parent reply	other threads:[~2011-11-29 13:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  0:49 ASoC: Dynamic CODEC DAI Patrick Lai
2011-11-29  0:58 ` Patrick Lai
2011-11-29  1:19 ` Pierre-Louis Bossart
     [not found] ` <000001ccae35$0122cf60$03686e20$@bossart@linux.intel.com>
2011-11-29  6:14   ` Patrick Lai
2011-11-29 21:20     ` Pierre-Louis Bossart
2011-11-29 13:49 ` Mark Brown [this message]
2011-12-02  2:56   ` Patrick Lai
2011-12-02 10:11     ` Liam Girdwood
2011-12-05  7:22       ` Patrick Lai
2011-12-05 11:49         ` Mark Brown
2011-12-02 11:45     ` Mark Brown

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=20111129134913.GB26800@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=plai@codeaurora.org \
    /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).