From: Jianhua Lu <lujianhua000@gmail.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Banajit Goswami <bgoswami@quicinc.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH v2 1/2] ASoC: qcom: sdw: Add TDM support
Date: Tue, 12 Dec 2023 22:32:56 +0800 [thread overview]
Message-ID: <ZXhvGEN28L5EqMx-@Gentoo> (raw)
In-Reply-To: <c43c4303-ed59-49e7-940a-62df6ad1b575@linaro.org>
On Tue, Dec 12, 2023 at 11:47:36AM +0000, Srinivas Kandagatla wrote:
> > +int qcom_snd_tdm_hw_params(struct snd_pcm_substream *substream,
> > + struct snd_pcm_hw_params *params)
> > +{
>
> TBH, this should not be part of sdw.c file, its intended for more of
> soundwire specific helpers, pl consider moving this to common.c for now.
> Because, Not all old qcom platforms have soundwire controllers.
Acked.
>
> > + ret = snd_soc_dai_set_tdm_slot(cpu_dai, 0, 0x3, 8, slot_width);
>
> slot mask is always set to 2 channels in this case, should you not check
> the number of channels to determine the correct one?
>
>
> These magic number 0, 0x3, 8 seems to make the code unreadable, can you
> do something like this:
> snd_soc_dai_set_tdm_slot(cpu_dai, tx_mask, rx_mask,
> ARRAY_SIZE(tdm_slot_offset), slot_width);
Acked.
>
> > + }
> > + }
> Finally ./sound/soc/qcom/sdm845.c does have exactly same code, can you
> consider removing this and make use of this new helper in that file too.
Acked.
Thanks for your reveiw very much, I will do it in patch v3.
prev parent reply other threads:[~2023-12-12 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 9:58 [RFC, PATCH v2 1/2] ASoC: qcom: sdw: Add TDM support Jianhua Lu
2023-12-12 9:58 ` [RFC, PATCH v2 2/2] ASoC: qcom: sm8250: Add TERTIARY_TDM_RX_0 support Jianhua Lu
2023-12-12 11:47 ` [RFC, PATCH v2 1/2] ASoC: qcom: sdw: Add TDM support Srinivas Kandagatla
2023-12-12 14:32 ` Jianhua Lu [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=ZXhvGEN28L5EqMx-@Gentoo \
--to=lujianhua000@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.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