All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "sakoman@gmail.com" <sakoman@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	"getarunks@gmail.com" <getarunks@gmail.com>
Subject: Re: [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and	Headset pop-attenuation fix
Date: Wed, 20 May 2009 09:51:21 +0100	[thread overview]
Message-ID: <20090520085121.GA11459@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03057419D3@dbde02.ent.ti.com>

On Wed, May 20, 2009 at 01:51:02PM +0530, Aggarwal, Anuj wrote:
> Peter Ujfalusi [mailto:peter.ujfalusi@nokia.com]:
> > On Tuesday 19 May 2009 21:58:06 ext Mark Brown wrote:

> > > It seems like the feedback has been pretty much OK so it should be OK
> > > apply the patches - Peter?
> > I also think, that it should be OK to apply this series.

Applied - thanks for your hard work on this!  

BTW, I don't know if you noticed the DAPM changes I pushed the other
day.  One commit in particular, 452c5eaa0d5162e02ffee742ea17540887bc2904, 
might be interesting for TWL4030 - it changes things so that we're in
BIAS_ON whenever there's a bias path active, not only when there's a DAC
or ADC path.  I've got a feeling some of the pop/click stuff may mean
that's not as useful as it might've been in the past.

> [Aggarwal, Anuj] Since different platforms are using different ramp
> values, how should it be handled via the same codec source code? How
> should this be done, without modifying the code base? Or should it be
> done every time user wants to play an audio file?

Since it's just a change in one parameter the driver should be able to
arrange to get that configuration value provided to it via platform
data.  It's still the same chip and needs the same driver, all that's
changing is configuration information.

  reply	other threads:[~2009-05-20  8:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 13:02 [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and Headset pop-attenuation fix Peter Ujfalusi
2009-05-18 13:02 ` [PATCH 1/2] ASoC: TWL4030: Change DAPM routings and controls for DACs and PGAs Peter Ujfalusi
2009-05-18 13:02   ` [PATCH 2/2] ASoC: TWL4030: Move the Headset pop-attenuation code to PGA event Peter Ujfalusi
2009-05-18 13:09 ` [PATCH 0/2] ASoC: TWL4030: DAPM restructuring and Headset pop-attenuation fix Mark Brown
2009-05-18 15:28   ` Aggarwal, Anuj
2009-05-19  0:48     ` Lopez Cruz, Misael
2009-05-19  6:47       ` Aggarwal, Anuj
2009-05-19  8:00         ` Peter Ujfalusi
2009-05-19  8:30           ` Aggarwal, Anuj
2009-05-19  6:46     ` Peter Ujfalusi
2009-05-19  7:33       ` Jarkko Nikula
2009-05-19 18:58         ` Mark Brown
2009-05-20  5:56           ` Peter Ujfalusi
2009-05-20  8:21             ` Aggarwal, Anuj
2009-05-20  8:51               ` Mark Brown [this message]
2009-05-20  9:12                 ` Peter Ujfalusi
2009-05-21 10:47                   ` Aggarwal, Anuj
2009-05-21 11:06                     ` Mark Brown
2009-05-20  9:08               ` Peter Ujfalusi

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=20090520085121.GA11459@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anuj.aggarwal@ti.com \
    --cc=getarunks@gmail.com \
    --cc=peter.ujfalusi@nokia.com \
    --cc=sakoman@gmail.com \
    /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.