From: Daniel Baluta <daniel.baluta@nxp.com>
To: <alsa-devel@alsa-project.org>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <linux-kernel@vger.kernel.org>,
<patches@opensource.wolfsonmicro.com>,
<ckeepax@opensource.wolfsonmicro.com>, <shengjiu.wang@nxp.com>,
<viorel.suman@nxp.com>, <mihai.serban@nxp.com>
Subject: [PATCH 1/2] ASoC: codec: wm8960: Stop when a matching PLL freq is found
Date: Thu, 6 Apr 2017 14:51:53 +0300 [thread overview]
Message-ID: <1491479514-24862-2-git-send-email-daniel.baluta@nxp.com> (raw)
In-Reply-To: <1491479514-24862-1-git-send-email-daniel.baluta@nxp.com>
When a matching PLL freq is found, searching continues even this is
not necessary. The problem was introduced with the following refactoring
commit 84fdc00d519ffd ("ASoC: codec: wm9860: Refactor PLL out freq search)
Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
sound/soc/codecs/wm8960.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/sound/soc/codecs/wm8960.c b/sound/soc/codecs/wm8960.c
index 36c8454..ace69da 100644
--- a/sound/soc/codecs/wm8960.c
+++ b/sound/soc/codecs/wm8960.c
@@ -724,7 +724,11 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
break;
}
}
+ if (k != ARRAY_SIZE(bclk_divs))
+ break;
}
+ if (j != ARRAY_SIZE(dac_divs))
+ break;
}
if (*bclk_idx != -1)
--
2.7.4
next prev parent reply other threads:[~2017-04-06 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 11:51 [PATCH 0/2] ASoC: codec: wm8960: Relax bit clock computation when using PLL Daniel Baluta
2017-04-06 11:51 ` Daniel Baluta [this message]
2017-04-06 18:55 ` Applied "ASoC: codec: wm8960: Stop when a matching PLL freq is found" to the asoc tree Mark Brown
2017-04-06 11:51 ` [PATCH 2/2] ASoC: codec: wm8960: Relax bit clock computation when using PLL Daniel Baluta
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=1491479514-24862-2-git-send-email-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.serban@nxp.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@nxp.com \
--cc=tiwai@suse.com \
--cc=viorel.suman@nxp.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;
as well as URLs for NNTP newsgroup(s).