All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "sakoman@gmail.com" <sakoman@gmail.com>,
	"anuj.aggarwal@ti.com" <anuj.aggarwal@ti.com>,
	alsa-devel@alsa-project.org,
	"getarunks@gmail.com" <getarunks@gmail.com>
Subject: Re: [PATCH 1/1] ASoC: TWL4030: Wait RAMP_DELAY?on	headsetl_event: POST_PMD
Date: Thu, 14 May 2009 13:53:34 +0100	[thread overview]
Message-ID: <20090514125333.GA9471@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200905141544.47934.peter.ujfalusi@nokia.com>

On Thu, May 14, 2009 at 03:44:47PM +0300, Peter Ujfalusi wrote:
> On Thursday 14 May 2009 12:56:21 ext Mark Brown wrote:

> > The event could check the current setup and do whatever's appropriate?

> I have to think about this, but at first sight it does look awfully 
> complicated thing to do (4 PGA, 7 output with mixers, 2+1 output mux)...

It might help to have the mixers and muxes maintain some state when they
change?  It's just a suggestion, I'm not familiar enough with the codec
to know if it's a sensible one for this device or if it's more trouble
than it's worth.

> I think I don't want to fixate the ramp delay to any value (meaning that the 
> delay would last around 50ms). This seams to be also board specific, so I 
> would rather leave this to the user to find the best value for the given 
> board.

Ah, right.  Possibly worth making it platform data, I suppose, but
that'd be a pain when experimenting to find the values.

  reply	other threads:[~2009-05-14 12:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 11:14 [PATCH 0/1] ASoC: TWL4030: Headset ramp down fix Peter Ujfalusi
2009-05-11 11:14 ` [PATCH 1/1] ASoC: TWL4030: Wait RAMP_DELAY on headsetl_event: POST_PMD Peter Ujfalusi
2009-05-11 12:03   ` Jarkko Nikula
2009-05-12 10:50     ` Peter Ujfalusi
2009-05-12 11:19       ` Jarkko Nikula
2009-05-12 11:31         ` Peter Ujfalusi
2009-05-12 11:52           ` Jarkko Nikula
2009-05-12 12:02             ` Jarkko Nikula
2009-05-12 12:16               ` Peter Ujfalusi
2009-05-12 12:21                 ` Jarkko Nikula
2009-05-12 13:16                   ` Peter Ujfalusi
2009-05-12 13:56                     ` Jarkko Nikula
2009-05-13 12:57                       ` Peter Ujfalusi
2009-05-13 13:05                         ` Mark Brown
2009-05-14  5:27                           ` Peter Ujfalusi
2009-05-14  6:08                             ` Jarkko Nikula
2009-05-14  6:35                               ` Peter Ujfalusi
2009-05-14  8:09                               ` Peter Ujfalusi
2009-05-14  9:05                                 ` Jarkko Nikula
2009-05-14  9:19                                   ` Peter Ujfalusi
2009-05-14  9:24                                 ` Mark Brown
2009-05-14  9:48                                   ` Peter Ujfalusi
2009-05-14  9:56                                     ` Mark Brown
2009-05-14 12:44                                       ` Peter Ujfalusi
2009-05-14 12:53                                         ` Mark Brown [this message]
2009-05-15  6:30                                           ` [PATCH 1/1] ASoC: TWL4030: Wait RAMP_DELAY?on " Peter Ujfalusi
2009-05-18  7:46                                             ` Peter Ujfalusi
2009-05-14  9:23                             ` [PATCH 1/1] ASoC: TWL4030: Wait RAMP_DELAY on " Mark Brown
2009-05-11 12:57 ` [PATCH 0/1] ASoC: TWL4030: Headset ramp down fix Arun KS
2009-05-12  3:59   ` Anuj Aggarwal
2009-05-12  5:33     ` Jarkko Nikula
2009-05-12  6:14       ` Aggarwal, Anuj
2009-05-12  6:39         ` Jarkko Nikula
2009-05-12  6:50           ` Aggarwal, Anuj
2009-05-12  6:44   ` 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=20090514125333.GA9471@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.