From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Mark Brown" <broonie@kernel.org>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>, "Yixun Lan" <dlan@kernel.org>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <spacemit@lists.linux.dev>,
<jinmei.wei@spacemit.com>
Subject: Re: [PATCH v2 3/3] ASoC: spacemit: declare shared BCLK for cross-DAI rate constraint
Date: Mon, 18 May 2026 14:06:08 +0800 [thread overview]
Message-ID: <DILKRVYSWGAG.1X39KO7JLX6VF@linux.spacemit.com> (raw)
In-Reply-To: <agHl6p-JEjpsPsPX@sirena.co.uk>
Hi Mark,
On Mon May 11, 2026 at 10:21 PM CST, Mark Brown wrote:
> On Thu, May 07, 2026 at 06:31:44PM +0800, Troy Mitchell wrote:
>> On SpacemiT K3, multiple I2S controllers share the same physical BCLK
>> (c_bclk). Declare this clock via snd_soc_dai_set_bclk_clk() so the
>> ASoC core can automatically constrain hw_params when one controller is
>> already streaming.
>>
>> For K1, c_bclk is NULL (obtained via devm_clk_get_optional_enabled),
>> so this call is a no-op and behavior is unchanged.
>
> We don't appear to have a c_bclk in current code?
You're right, I forgot to note the dependency. I'll drop this patch
in v3 so the core framework patches can be merged independently.
I'll resend it as a standalone patch.
- Troy
prev parent reply other threads:[~2026-05-18 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 10:31 [PATCH v2 0/3] ASoC: add shared BCLK rate constraint for cross-DAI coordination Troy Mitchell
2026-05-07 10:31 ` [PATCH v2 1/3] ASoC: soc-dai: add shared BCLK clock for cross-DAI rate constraints Troy Mitchell
2026-05-07 10:31 ` [PATCH v2 2/3] ASoC: soc-pcm: constrain hw_params when DAIs share the same BCLK Troy Mitchell
2026-05-07 10:31 ` [PATCH v2 3/3] ASoC: spacemit: declare shared BCLK for cross-DAI rate constraint Troy Mitchell
2026-05-11 14:21 ` Mark Brown
2026-05-18 6:06 ` Troy Mitchell [this message]
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=DILKRVYSWGAG.1X39KO7JLX6VF@linux.spacemit.com \
--to=troy.mitchell@linux.spacemit.com \
--cc=broonie@kernel.org \
--cc=dlan@kernel.org \
--cc=jinmei.wei@spacemit.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=spacemit@lists.linux.dev \
--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®