All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	broonie@opensource.wolfsonmicro.com
Subject: Re: Question about your DSP topic branch
Date: Thu, 31 Mar 2011 22:35:22 +0100	[thread overview]
Message-ID: <1301607322.3549.211.camel@odin> (raw)
In-Reply-To: <4D9421DB.4010204@codeaurora.org>

On Wed, 2011-03-30 at 23:40 -0700, Patrick Lai wrote:
> Hi Liam/Mark,
> 
> In the back-end platform driver, routing table and array of widgets are 
> defined to describe interconnection of front-end and back-end. Instead 
> of defining FE and BE as AIF pin using SND_SOC_DAPM_AIF_IN/OUT macros,
> I would like to use SND_SOC_DAPM_AIF_IN_E/OUT_E macros. Essentially, I 
> want to register event handler to jump start routing in the DSP for a 
> newly activated FE under multiple streams to single HW path scenario. At 
> this time, BE is already activated so I need other mechanism to jump 
> start routing. I could put the logic in my front-end CPU DAI driver. 
> However, I feel that path setup should be handled by DAPM/DSP framework. 
> Hence, I am looking for a good place to trigger calling of event handler 
> in soc-dapm.c/soc-dsp.c. Any suggestion?


So iiuc, your BE is active (with another FE) and you then enable a
another FE that is connected to the already active BE ?

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.

Liam   

> 
> Thanks
> Patrick
> 

  reply	other threads:[~2011-03-31 21:35 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 [this message]
2011-03-31 21:42       ` Mark Brown
2011-03-31 22:07         ` Patrick Lai
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=1301607322.3549.211.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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 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.