alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Question about your DSP topic branch
Date: Thu, 31 Mar 2011 15:07:01 -0700	[thread overview]
Message-ID: <4D94FB05.8030207@codeaurora.org> (raw)
In-Reply-To: <20110331214239.GB21726@opensource.wolfsonmicro.com>

On 3/31/2011 2:42 PM, Mark Brown wrote:
> On Thu, Mar 31, 2011 at 10:35:22PM +0100, Liam Girdwood wrote:
>
>> It should be possible to add support for the _E() macros in soc-dsp.c,
>> but I'm not sure why it's required atm since we dont need this for OMAP4
>> ABE.
>
> Not sure why Patrick might need it but some of the DSPs I've seen
> require a multiple write sequence to kick them into doing things - for
> example, set the state up then do another write to tell it to apply the
> new configuration.

The reason is that PCM stream, which is presented as front-end, is
run-time instantiated in DSP. Routing command to DSP cannot
happen until PCM stream is available. So for multiple streams to same
back-end case, activation of back-end can trigger routing of first PCM
stream. However, for 2nd stream, backend is already active. So, routing
of 2nd PCM stream would have to be triggered by activation of front-end.

As I stated before, I can have front-end CPU DAI driver trigger as 
workaround. However, it seems like DAPM framework would be the best 
place to provide the hook. It's better to keep the routing logic
localized in platform driver in my opinion

Thanks
Patrick

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-03-31 22:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D2652C8.7030701@codeaurora.org>
2011-01-25  7:01 ` Question about your DSP topic branch Patrick Lai
2011-01-25 11:51   ` Mark Brown
2011-01-26  6:22     ` Patrick Lai
2011-01-26 11:20       ` Mark Brown
2011-01-27 21:51         ` Patrick Lai
2011-01-31 13:30           ` Mark Brown
2011-03-17  7:29             ` Patrick Lai
2011-03-17 11:57               ` Mark Brown
2011-01-25 16:46   ` Liam Girdwood
2011-01-27 23:41     ` Patrick Lai
2011-03-15  7:08       ` [alsa-devel] " Patrick Lai
2011-03-15 11:25         ` Mark Brown
2011-03-17  7:21           ` Patrick Lai
2011-03-17 23:58             ` Mark Brown
2011-03-30 20:39 ` Question about your DSP topic Patrick Lai
2011-03-31  6:40   ` Question about your DSP topic branch Patrick Lai
2011-03-31 21:35     ` Liam Girdwood
2011-03-31 21:42       ` Mark Brown
2011-03-31 22:07         ` Patrick Lai [this message]
2011-03-31 18:26   ` Question about your DSP topic Liam Girdwood
2011-03-31 20:59     ` Patrick Lai
2011-03-31 21:37       ` Liam Girdwood

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=4D94FB05.8030207@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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).