From: Mark Brown <broonie@kernel.org>
To: Sune Brian <briansune@gmail.com>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/soc/codecs/wm8978: add missing BCLK divider setup
Date: Tue, 7 Oct 2025 14:48:01 +0100 [thread overview]
Message-ID: <ec917317-4240-47ff-bb9a-6f2fe9068c19@sirena.org.uk> (raw)
In-Reply-To: <CAN7C2SBDC2LrWpUTe3zZakHCrmUy1nQ-WiguLQKVK1CyOPb9zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Tue, Oct 07, 2025 at 09:39:59PM +0800, Sune Brian wrote:
> Before the below action started. I need more background, if possible.
> If my understand is correct on your ideas. Do you mean the default driver calls
> the bclkdiv on other places? But how could that bclkdiv # be correct
> from first place?
> As I had mentioned the div # ifself like this codec is a LUT rather
> than the actual divided #?
> For example /32 from LUT is a 3b101?
> For example what if MCLK is set higher than /64 could even out of the
> LUT from first place.
> The external div # passed in, how to ensure it is codec LUT compatible
> from first place?
Systems doing this are using a machine driver written for that specific
machine and will know exactly which CODEC and other components they are
dealing with.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-10-07 13:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 9:13 [PATCH] sound/soc/codecs/wm8978: add missing BCLK divider setup Brian Sune
2025-10-07 10:30 ` Charles Keepax
2025-10-07 11:22 ` Sune Brian
2025-10-07 12:11 ` Charles Keepax
2025-10-07 12:18 ` Mark Brown
2025-10-07 12:26 ` Charles Keepax
2025-10-07 12:30 ` Mark Brown
2025-10-07 12:37 ` Sune Brian
2025-10-07 12:48 ` Sune Brian
2025-10-07 13:15 ` Charles Keepax
2025-10-07 13:39 ` Sune Brian
2025-10-07 13:48 ` Mark Brown [this message]
2025-10-07 13:54 ` Sune Brian
2025-10-07 11:33 ` [PATCH v2] ASoC: wm8978: " Brian Sune
2025-10-07 11:44 ` Mark Brown
2025-10-07 11:48 ` Sune Brian
2025-10-07 11:52 ` Mark Brown
2025-10-07 11:56 ` Sune Brian
2025-10-07 12:10 ` Mark Brown
2025-10-07 13:03 ` Sune Brian
2025-10-07 13:15 ` Mark Brown
2025-10-07 13:48 ` Sune Brian
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=ec917317-4240-47ff-bb9a-6f2fe9068c19@sirena.org.uk \
--to=broonie@kernel.org \
--cc=briansune@gmail.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
/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