From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: git@apitzsch.eu
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: wm8998: Add Kconfig prompt
Date: Wed, 23 Apr 2025 12:09:22 +0100 [thread overview]
Message-ID: <8c49fe8d-460e-4587-8d37-1208aa7dad7c@opensource.cirrus.com> (raw)
In-Reply-To: <aAZS8XVHtw5zxD2d@opensource.cirrus.com>
On 21/4/25 15:15, Charles Keepax wrote:
> On Fri, Apr 18, 2025 at 10:22:04PM +0200, André Apitzsch via B4 Relay wrote:
>> From: André Apitzsch <git@apitzsch.eu>
>>
>> Add tristate prompt to allow codec selection.
>>
>> Signed-off-by: André Apitzsch <git@apitzsch.eu>
>> ---
>
> Generally its good to say why one wants to make the symbol
> selectable, usually its to use it with simple card, although at
> least historically I think simple card struggled to handle the
> required set_sysclk calls for these codecs.
>
> But I have no objection to this being exported:
>
> Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
>
> Thanks,
> Charles
Yeah, I just checked simple-card and friends and I see no evidence that
it has a way to make the necessary calls to enable the clocks and PLL
on the WM8998.
Of course, the intended machine driver might not be simple/audio-graph
so that might not be a problem. Though a more specific machine driver
could simply select the codec driver it uses.
This is why it helps to say why you need this change.
next prev parent reply other threads:[~2025-04-23 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 20:22 [PATCH] ASoC: wm8998: Add Kconfig prompt André Apitzsch via B4 Relay
2025-04-21 14:15 ` Charles Keepax
2025-04-23 11:09 ` Richard Fitzgerald [this message]
2025-04-23 19:37 ` André Apitzsch
2025-04-22 13:12 ` 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=8c49fe8d-460e-4587-8d37-1208aa7dad7c@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=git@apitzsch.eu \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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