All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: fsl: imx-wm8962: Grant hw_params() permission to reprogram FLL
Date: Fri, 10 Jan 2014 21:15:50 +0800	[thread overview]
Message-ID: <20140110131549.GB17392@MrMyself> (raw)
In-Reply-To: <20140110114251.GE29039@sirena.org.uk>

On Fri, Jan 10, 2014 at 11:42:51AM +0000, Mark Brown wrote:
> On Fri, Jan 10, 2014 at 06:19:08PM +0800, Nicolin Chen wrote:
> > On Thu, Jan 09, 2014 at 06:25:51PM +0000, Mark Brown wrote:
> 
> > > implement bias level changes for non-CPU paths immediately I'm not sure
> > > what that's giving you over just using the bias level (which is the way
> > > you're supposed to check if the CODEC is active)?
> 
> > Aha, I also feel myself a bit obsessed to this modification while knowing
> > so well that you're not very into it. But it might be just because, at
> > least to me and according to our SRS of Linux BSP, the flexibility and
> > capability here is more important than the extra function - bypass paths.
> > (No offense taken, just my own feeling from the angle of a common user.)
> 
> Well, the common thing here is to use a sound server like PulseAudio -
> from an end user point of view only being able to play one thing at once
> isn't great either.  It feels like what you may be trying to do here is
> tune down the delay that gets applied after playback stops.  That's
> runtime tunable with pmdown_time.

Like ignoring pmdown_time? (Just did some searching and found the patch.)
Looks like this is going to be a reasonable one to fit my obsession here :)

Thank you for the idea. I'll try it first.
Nicolin Chen

      reply	other threads:[~2014-01-10 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25 10:37 [PATCH] ASoC: fsl: imx-wm8962: Grant hw_params() permission to reprogram FLL Nicolin Chen
2014-01-07  5:57 ` Nicole Otsuka
2014-01-07 14:24   ` Mark Brown
2014-01-08  8:30     ` Nicolin Chen
2014-01-09 18:25 ` Mark Brown
2014-01-10 10:19   ` Nicolin Chen
2014-01-10 11:42     ` Mark Brown
2014-01-10 13:15       ` Nicolin Chen [this message]

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=20140110131549.GB17392@MrMyself \
    --to=guangyu.chen@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /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.