alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC_i/iv 1/3] ASoC: Decouple DAPM from CODECs. Part core (will be squashed)
Date: Mon, 1 Nov 2010 09:13:23 -0400	[thread overview]
Message-ID: <20101101131322.GC22639@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1288461714.3286.143.camel@odin>

On Sat, Oct 30, 2010 at 07:01:54PM +0100, Liam Girdwood wrote:
> On Fri, 2010-10-29 at 13:04 -0700, Mark Brown wrote:

> > >  		run_delayed_work(&card->rtd[i].delayed_work);
> > > -		card->rtd[i].codec->suspend_bias_level = card->rtd[i].codec->bias_level;
> > > +		card->rtd[i].codec->dapm->suspend_bias_level = card->rtd[i].codec->dapm->bias_level;

> Btw, not sure what you mean by this 1 line change being run multiple
> times being different to the old line.

It's not different, a lot of the stuff here is things that we need to do
in the series that are thrown up by the series as a result of it
touching all relevant places.  I tried to mention this in the places I
noted it, but some of them I will have forgotten.

> > I'd be more inclined to just embed the struct in the objects that need
> > it rather than individually allocating them - it saves error checking
> > and deallocation, and I can't see any cases where we'd want to
> > optionally have a DAPM object.

> Yeah, the reason for this is because it was unclear at the time whether
> we will need to share a context between DAI backend and frontends. So
> this can be embedded now.

Jarkko, with this change I think this first patch is good to go - I
think we should try to get the early bits in while we're iterating on
the rest.

  parent reply	other threads:[~2010-11-01 13:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 12:00 [RFC i-iv] ASoC: Add support for cross-device paths without dai and without name collision Jarkko Nikula
2010-10-29 12:00 ` [RFC_i/iv 1/3] ASoC: Decouple DAPM from CODECs. Part core (will be squashed) Jarkko Nikula
2010-10-29 20:04   ` Mark Brown
2010-10-30 18:01     ` Liam Girdwood
2010-10-31 18:13       ` Jarkko Nikula
2010-11-01 13:13       ` Mark Brown [this message]
2010-11-04 12:38         ` [PATCH] ASoC: Decouple DAPM from CODECs Jarkko Nikula
2010-11-05  3:29           ` Mark Brown
2010-11-05  7:20             ` Jarkko Nikula
2010-11-05 13:38               ` Mark Brown
2010-11-05 13:53                 ` Jarkko Nikula
2010-11-05 14:02                   ` Mark Brown
     [not found] ` <1288353618-21753-3-git-send-email-jhnikula@gmail.com>
2010-10-29 13:45   ` [RFC_i/iv 2/3] ASoC: Decouple DAPM from CODECs. Part codecs (will be squashed) Jarkko Nikula
2010-10-29 20:45   ` Mark Brown
     [not found] ` <1288353618-21753-4-git-send-email-jhnikula@gmail.com>
2010-10-29 20:47   ` [RFC_i/iv 3/3] ASoC: Decouple DAPM from CODECs. Part platforms " Mark Brown
2010-10-31 18:11     ` Jarkko Nikula
2010-11-01 13:14       ` 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=20101101131322.GC22639@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --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).