From: Mark Brown <broonie@kernel.org>
To: jack.yu@realtek.com
Cc: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
lars@metafoo.de, flove@realtek.com, oder_chiou@realtek.com,
shumingf@realtek.com, derek.fang@realtek.com,
Trevor.Wu@mediatek.com
Subject: Re: [PATCH] ASoC: rt712-sdca: reconfigure PLL2 to fix calibration time-out
Date: Mon, 7 Sep 2026 22:31:44 +0100 [thread overview]
Message-ID: <9f563c50-e18f-421a-8325-e70e7d482b51@sirena.org.uk> (raw)
In-Reply-To: <20260907064114.435697-1-jack.yu@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Mon, Sep 07, 2026 at 02:41:14PM +0800, jack.yu@realtek.com wrote:
> From: Jack Yu <jack.yu@realtek.com>
>
> Add pll2 reconfiguration sequence in order to fix calibration
> time-out issue and to support 24.576MHz MCLK on specific platforms.
> +static void rt712_sdca_clk_patch2(struct rt712_sdca_priv *rt712)
> +{
> + regmap_write(rt712->regmap, RT712_SDW_SCALE_CLK0, 0x03);
> + regmap_write(rt712->regmap, RT712_SDW_SCALE_CLK1, 0x03);
This looks like it collides with sdw_slave_set_frequency()?
> + if (loop_dc == chk_cnt) {
> + if (clk_base == RT712_CLK_FREQ_24_576MHZ) {
> + rt712_sdca_clk_patch(rt712);
> + rt712_sdca_clk_patch2(rt712);
> + }
Perhaps the patching should be checking that the scaling registers are
the ones written above and only kicking in if that's the case, or have
more cases that work with other scaling setups? Or restore whatever the
core set if that's possible?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-07 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:41 [PATCH] ASoC: rt712-sdca: reconfigure PLL2 to fix calibration time-out jack.yu
2026-09-07 21:31 ` Mark Brown [this message]
2026-09-08 11:09 ` Jack Yu
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=9f563c50-e18f-421a-8325-e70e7d482b51@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Trevor.Wu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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.