From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Shengjiu Wang <shengjiu.wang@nxp.com>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
allison@lohutok.net, guennadi.liakhovetski@linux.intel.com,
tglx@linutronix.de, patches@opensource.cirrus.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: wm8962: fix lambda value
Date: Thu, 12 Dec 2019 16:53:11 +0000 [thread overview]
Message-ID: <20191212165311.GK4310@sirena.org.uk> (raw)
In-Reply-To: <20191212164835.GD10451@ediswmail.ad.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Thu, Dec 12, 2019 at 04:48:35PM +0000, Charles Keepax wrote:
> On Wed, Dec 11, 2019 at 07:57:22PM +0800, Shengjiu Wang wrote:
> > According to user manual, it is required that FLL_LAMBDA > 0
> > in all cases (Integer and Franctional modes).
> How well tested is this change, and is it addressing an issue you
> have observed? I agree this does better fit the datasheet just a
> little nervous as its an older part that has seen a lot of usage.
I've got a feeling that requirement might've been added in later
versions of the datasheet...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-12 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 11:57 Shengjiu Wang
2019-12-12 16:48 ` Charles Keepax
2019-12-12 16:53 ` Mark Brown [this message]
2019-12-13 3:09 ` [alsa-devel] " Shengjiu Wang
2019-12-13 10:56 ` Charles Keepax
2019-12-13 12:05 ` Fabio Estevam
2019-12-16 12:05 ` Applied "ASoC: wm8962: fix lambda value" to the asoc tree 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=20191212165311.GK4310@sirena.org.uk \
--to=broonie@kernel.org \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=gregkh@linuxfoundation.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kstewart@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@nxp.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®