All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2/7] ASoC: DAPM: Pass snd_dapm_soc_update as parameter
Date: Fri, 29 Apr 2011 00:34:11 +0200	[thread overview]
Message-ID: <4DB9EB63.5020007@metafoo.de> (raw)
In-Reply-To: <20110428222315.GA19741@opensource.wolfsonmicro.com>

On 04/29/2011 12:23 AM, Mark Brown wrote:
> On Thu, Apr 28, 2011 at 11:18:00PM +0100, Mark Brown wrote:
>> On Fri, Apr 29, 2011 at 12:04:04AM +0200, Lars-Peter Clausen wrote:
>>> On 04/28/2011 11:48 PM, Mark Brown wrote:
> 
>>>> Moving to the card doesn't seem helpful, while we're currently doing one
>>>> update at once it's not immediately obvious that we want to keep doing
>>>> that indefinitely.
> 
>>> But keeping it in the dapm context would limit us to one update per context
>>> which doesn't seem very sustainable either.
> 
>> Though for global state changes like this that's pretty much irrelevant
>> as we need to walk the entire graph at once.
> 
> BTW, this means that my above comment was too hasty; I can't actually
> see a situation where we'd ever want to have multiple updates in flight.
> Though I also don't immediately see a need to move as the update gets
> applied to a specific context anyway ...

If we'd keep the update in the dapm context we'd have to iterate over all
contexts to find the one context which contains the update.
As you've said we have to walk the whole graph and it does not make a nice
interface if the function takes one specific dapm context while it works on the
whole card.

Currently we get the codec from the widget for which the update is run and not
from the dapm context anyway.

- Lars

  reply	other threads:[~2011-04-28 22:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 16:46 [PATCH 1/7] ASoC: Fix cards getting stuck in a powered state Lars-Peter Clausen
2011-04-28 16:46 ` [PATCH 2/7] ASoC: DAPM: Pass snd_dapm_soc_update as parameter Lars-Peter Clausen
2011-04-28 19:40   ` Mark Brown
2011-04-28 20:39     ` Lars-Peter Clausen
2011-04-28 20:58       ` Mark Brown
2011-04-28 21:24         ` Lars-Peter Clausen
2011-04-28 21:48           ` Mark Brown
2011-04-28 22:04             ` Lars-Peter Clausen
2011-04-28 22:18               ` Mark Brown
2011-04-28 22:23                 ` Mark Brown
2011-04-28 22:34                   ` Lars-Peter Clausen [this message]
2011-04-28 22:48                     ` Mark Brown
2011-04-28 22:58                       ` Lars-Peter Clausen
2011-04-28 22:59                         ` Mark Brown
2011-04-28 16:46 ` [PATCH 3/7] ASoC: Drop unused parameter from dapm_seq_run Lars-Peter Clausen
2011-04-28 16:46 ` [PATCH 4/7] ASoC: Pass snd_soc_card instead of snd_soc_dapm_context were appropriate Lars-Peter Clausen
2011-04-28 19:47   ` Mark Brown
2011-04-28 20:13     ` Mark Brown
2011-04-28 16:46 ` [PATCH 5/7] ASoC: Move DAPM debugfs directory creation to snd_soc_dapm_debugfs_init Lars-Peter Clausen
2011-04-28 16:46 ` [PATCH 6/7] ASoC: Move DAPM widget debugfs entry creation to snd_soc_dapm_new_widgets Lars-Peter Clausen
2011-04-28 16:46 ` [PATCH 7/7] ASoC: Instantiate all DAPM widgets at once Lars-Peter Clausen
2011-04-28 20:07   ` Mark Brown
2011-04-28 20:25     ` Lars-Peter Clausen
2011-04-28 21:18       ` Mark Brown
2011-04-28 19:15 ` [PATCH 1/7] ASoC: Fix cards getting stuck in a powered state Mark Brown
2011-04-28 19:47   ` Lars-Peter Clausen
2011-04-28 19:52     ` Mark Brown
2011-04-28 23:14       ` Lars-Peter Clausen
2011-04-28 23:17         ` Mark Brown
2011-04-28 23:40           ` Lars-Peter Clausen

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=4DB9EB63.5020007@metafoo.de \
    --to=lars@metafoo.de \
    --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 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.