All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sangbeom Kim <sbkim73@samsung.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	'Liam Girdwood' <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Ensure we delay long enough	for	WM8994 FLL to lock when starting
Date: Mon, 04 Jul 2011 10:13:56 +0900	[thread overview]
Message-ID: <032b01cc39e7$a5888d00$f099a700$@com> (raw)
In-Reply-To: <20110704004453.GA1178@opensource.wolfsonmicro.com>

On Mon, Jul 04, 2011 at 09:45 AM +0900, Mark Brown wrote:
> > > This delay is very conservative.
> 
> > What's the meaning of conservative?
> 
> In this context it means safe.
> 
> > It means 5ms delay long enough?
> > or at least, FLL lock time should be ensured 5ms?
> 
> Yes, the 5ms should be more than enough time for the FLL to lock - in
> most situations the time taken to do the register writes surrounding
> enabling and then using the FLL are sufficient to cover the startup
> time.

OK, 
I have a one more question.
Is there any checking method for locking FLL?
(ex. Checking register bit for FLL lock)
Just using msleep looks not enough to ensure FLL lock.

Thanks,
SB Kim

  reply	other threads:[~2011-07-04  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  0:35 [PATCH] ASoC: Ensure we delay long enough for WM8994 FLL to lock when starting Mark Brown
2011-07-03 23:59 ` Sangbeom Kim
2011-07-04  0:44   ` Mark Brown
2011-07-04  1:13     ` Sangbeom Kim [this message]
2011-07-04  2:07       ` Mark Brown
2011-07-04  9:44 ` Liam Girdwood

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='032b01cc39e7$a5888d00$f099a700$@com' \
    --to=sbkim73@samsung.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    --cc=patches@opensource.wolfsonmicro.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.