From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: sebastian.krzyszkowiak@puri.sm
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
patches@opensource.cirrus.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@puri.sm
Subject: Re: [PATCH RESEND 2/4] ASoC: wm8962: Don't disable SYSCLK if it's enabled via DAPM
Date: Tue, 6 Jan 2026 14:30:43 +0000 [thread overview]
Message-ID: <aV0ck+O4ysmA25s6@opensource.cirrus.com> (raw)
In-Reply-To: <20260105-wm8962-l5-fixes-v1-2-f4f4eeacf089@puri.sm>
On Mon, Jan 05, 2026 at 04:02:09AM +0100, Sebastian Krzyszkowiak via B4 Relay wrote:
> From: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
>
> If SYSCLK pin is enabled via DAPM, wm8962_configure_bclk may turn it off
> behind DAPM's back, making it assume that the clock is still enabled even
> if it actually isn't, which can end up with it not being enabled for
> playback or capture when it's needed.
>
> Signed-off-by: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
> ---
> sound/soc/codecs/wm8962.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/sound/soc/codecs/wm8962.c b/sound/soc/codecs/wm8962.c
> index 1040740fc80f..843b8c6b40a4 100644
> --- a/sound/soc/codecs/wm8962.c
> +++ b/sound/soc/codecs/wm8962.c
> @@ -2520,7 +2520,8 @@ static void wm8962_configure_bclk(struct snd_soc_component *component)
> usleep_range(500, 1000);
> dspclk = snd_soc_component_read(component, WM8962_CLOCKING1);
>
> - if (snd_soc_dapm_get_bias_level(dapm) != SND_SOC_BIAS_ON)
> + if (snd_soc_dapm_get_bias_level(dapm) != SND_SOC_BIAS_ON
> + && !snd_soc_dapm_get_pin_status(dapm, "SYSCLK"))
Something seems a little weird here. I guess SYSCLK is a supply
widget, so it can technically be on before the card bias level is
fully on. But SYSCLK usually supplies other widgets that would
require the bias to be fully on, so what causes it to be on? Or
is this a transitional state as things are powering up?
Thanks,
Charles
next prev parent reply other threads:[~2026-01-06 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 3:02 [PATCH RESEND 0/4] sound: codecs: wm8962: Assorted fixes Sebastian Krzyszkowiak via B4 Relay
2026-01-05 3:02 ` [PATCH RESEND 1/4] ASoC: wm8962: Add WM8962_ADC_MONOMIX to "3D Coefficients" mask Sebastian Krzyszkowiak via B4 Relay
2026-01-06 13:29 ` Charles Keepax
2026-01-05 3:02 ` [PATCH RESEND 2/4] ASoC: wm8962: Don't disable SYSCLK if it's enabled via DAPM Sebastian Krzyszkowiak via B4 Relay
2026-01-06 14:30 ` Charles Keepax [this message]
2026-01-05 3:02 ` [PATCH RESEND 3/4] ASoC: wm8962: Don't report a microphone if it's shorted to ground on plug Sebastian Krzyszkowiak via B4 Relay
2026-01-06 14:02 ` Charles Keepax
2026-01-05 3:02 ` [PATCH RESEND 4/4] ASoC: wm8962: Don't mark WM8962_ADDITIONAL_CONTROL_4 as volatile Sebastian Krzyszkowiak via B4 Relay
2026-01-06 14:11 ` Charles Keepax
2026-01-05 3:09 ` [PATCH RESEND 0/4] sound: codecs: wm8962: Assorted fixes Sebastian Krzyszkowiak
2026-01-13 13:50 ` (subset) " 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=aV0ck+O4ysmA25s6@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=kernel@puri.sm \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=sebastian.krzyszkowiak@puri.sm \
--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