From: Maxim Kochetkov <fido_max@inbox.ru>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Claudiu Beznea" <claudiu.beznea@microchip.com>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ASoC: codecs: max98090: Allow dsp_a mode
Date: Thu, 22 Jun 2023 09:30:10 +0300 [thread overview]
Message-ID: <45c62cab-a779-e843-9f98-a0d14d2bc97b@inbox.ru> (raw)
In-Reply-To: <b83bf5c9-5998-4683-8f28-1eff432742ed@sirena.org.uk>
On 21.06.2023 23:46, Mark Brown wrote:
>> Ok. How about that:
>> ---
>> sound/soc/codecs/max98090.c | 52 ++++++++++++++++++++-----------------
>> sound/soc/codecs/max98090.h | 2 ++
>> 2 files changed, 30 insertions(+), 24 deletions(-)
>
> That looks plausible, yes.
>
> I do note that the driver ignores tdm_width (and the entire TDM
> configuration) when configuring BCLK, I guess it only works in clock
> consumer mode for TDM? If that's the case there should really be some
> validation, and there should probably be a check for slot width being 16
> since that looks like the only thing supported. Those were already
> broken though.
Yep, tdm_width is not used in the driver and I can drop it. We already
have slot_width validation in set_tdm_slot(), so only 16 is allowed. I
didn't check/use clock provider mode. But it looks fine for me.
set_fmt() just sets frame width here: 32 - by default, 48/64 - 3/4 slots
if configured. We also check slots count in set_tdm_slots(). It will
work for I2S/TDM.
prev parent reply other threads:[~2023-06-22 6:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 11:53 Maxim Kochetkov
2023-06-21 12:26 ` Mark Brown
2023-06-21 13:02 ` Maxim Kochetkov
2023-06-21 13:18 ` Mark Brown
2023-06-21 13:55 ` Maxim Kochetkov
2023-06-21 14:01 ` Mark Brown
2023-06-21 14:28 ` Maxim Kochetkov
2023-06-21 14:35 ` Mark Brown
2023-06-21 19:57 ` Maxim Kochetkov
2023-06-21 20:46 ` Mark Brown
2023-06-22 6:30 ` Maxim Kochetkov [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=45c62cab-a779-e843-9f98-a0d14d2bc97b@inbox.ru \
--to=fido_max@inbox.ru \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=claudiu.beznea@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
/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®