From: Mark Brown <broonie@kernel.org>
To: Maxim Kochetkov <fido_max@inbox.ru>
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: Wed, 21 Jun 2023 15:35:49 +0100 [thread overview]
Message-ID: <c054b036-d5fd-482b-adc4-913edbcd007c@sirena.org.uk> (raw)
In-Reply-To: <0ada8334-4006-438f-8461-5c4c8e13f65d@inbox.ru>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On Wed, Jun 21, 2023 at 05:28:41PM +0300, Maxim Kochetkov wrote:
> Yep. But we have to specify TDM parameters (slot masks, slot width, etc) any
> way. Because there is no default TDM configuration like I2S and so. And pure
> DSP_A/B mode just have no sense.
No, they make perfect sense and are widely supported - the sample size
is chosen based on the hwparams instead of being forced by configuring
TDM mode.
> Anyway. What do you suggest? Should I perform some refactoring for the
> driver? Should I move M98090_REG_TDM_FORMAT/M98090_REG_TDM_CONTROL registers
> setup to the max98090_dai_set_fmt()?
To repeat:
> > > I'm saying there should be some interlock between these two settings, if
> > > nothing else setting DSP A mode should force TDM mode with automatically
> > > configured slot sizes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-21 14:36 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 [this message]
2023-06-21 19:57 ` Maxim Kochetkov
2023-06-21 20:46 ` Mark Brown
2023-06-22 6:30 ` Maxim Kochetkov
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=c054b036-d5fd-482b-adc4-913edbcd007c@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=claudiu.beznea@microchip.com \
--cc=fido_max@inbox.ru \
--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®