From: Mark Brown <broonie@kernel.org>
To: 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, 11 May 2026 23:21:30 +0900 [thread overview]
Message-ID: <agHl6p-JEjpsPsPX@sirena.co.uk> (raw)
In-Reply-To: <20260507-i2s-same-blk-v2-3-ede05a22f732@linux.spacemit.com>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-11 14:21 UTC|newest]
Thread overview: 5+ 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 [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=agHl6p-JEjpsPsPX@sirena.co.uk \
--to=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 \
--cc=troy.mitchell@linux.spacemit.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