From: Chen-Yu Tsai <wenst@chromium.org>
To: "Darren.Ye" <darren.ye@mediatek.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
Subject: Re: [PATCH v6 01/10] ASoC: mediatek: common: modify mtk afe platform driver for mt8196
Date: Tue, 22 Jul 2025 15:38:05 +0800 [thread overview]
Message-ID: <CAGXv+5HQcGiUnsaOxHz86Y8JxUHh6e0ypusFEBLKchNx3fqKBA@mail.gmail.com> (raw)
In-Reply-To: <20250708111806.3992-2-darren.ye@mediatek.com>
Hi,
On Tue, Jul 8, 2025 at 7:33 PM Darren.Ye <darren.ye@mediatek.com> wrote:
>
> From: Darren Ye <darren.ye@mediatek.com>
>
> Mofify the pcm pointer interface to support 64-bit address access.
^ Modify
And the subject should say the same, or shorter:
Support 64-bit addresses in PCM pointer callback
> Signed-off-by: Darren Ye <darren.ye@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Tested-by: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
> ---
> .../mediatek/common/mtk-afe-platform-driver.c | 47 ++++++++++++-------
> .../mediatek/common/mtk-afe-platform-driver.h | 2 +
> 2 files changed, 33 insertions(+), 16 deletions(-)
>
> diff --git a/sound/soc/mediatek/common/mtk-afe-platform-driver.c b/sound/soc/mediatek/common/mtk-afe-platform-driver.c
> index 70fd05d5ff48..cab4ef035199 100644
> --- a/sound/soc/mediatek/common/mtk-afe-platform-driver.c
> +++ b/sound/soc/mediatek/common/mtk-afe-platform-driver.c
> @@ -86,29 +86,44 @@ snd_pcm_uframes_t mtk_afe_pcm_pointer(struct snd_soc_component *component,
> const struct mtk_base_memif_data *memif_data = memif->data;
> struct regmap *regmap = afe->regmap;
> struct device *dev = afe->dev;
> - int reg_ofs_base = memif_data->reg_ofs_base;
> - int reg_ofs_cur = memif_data->reg_ofs_cur;
> - unsigned int hw_ptr = 0, hw_base = 0;
> - int ret, pcm_ptr_bytes;
> -
> - ret = regmap_read(regmap, reg_ofs_cur, &hw_ptr);
> - if (ret || hw_ptr == 0) {
> - dev_err(dev, "%s hw_ptr err\n", __func__);
> - pcm_ptr_bytes = 0;
> + unsigned int hw_ptr_lower32 = 0, hw_ptr_upper32 = 0;
> + unsigned int hw_base_lower32 = 0, hw_base_upper32 = 0;
> + unsigned long long hw_ptr = 0, hw_base = 0;
> + int ret;
> + unsigned long long pcm_ptr_bytes = 0;
> +
> + ret = regmap_read(regmap, memif_data->reg_ofs_cur, &hw_ptr_lower32);
> + if (ret || hw_ptr_lower32 == 0) {
I'm not sure how the hardware is, but I think hw_ptr_lower32 == 0
should no longer be a failure, since it could be 0x100000000 or
some other address with the lower 32-bits all zero. Instead the
check should be done once the addresses are put together.
> + dev_err(dev, "%s hw_ptr_lower32 err\n", __func__);
> goto POINTER_RETURN_FRAMES;
This is out of scope, but maybe this should just return zero directly
to simplify reading.
> }
>
> - ret = regmap_read(regmap, reg_ofs_base, &hw_base);
> - if (ret || hw_base == 0) {
> - dev_err(dev, "%s hw_ptr err\n", __func__);
> - pcm_ptr_bytes = 0;
> - goto POINTER_RETURN_FRAMES;
> + if (memif_data->reg_ofs_cur_msb) {
> + ret = regmap_read(regmap, memif_data->reg_ofs_cur_msb, &hw_ptr_upper32);
> + if (ret) {
> + dev_err(dev, "%s hw_ptr_upper32 err\n", __func__);
> + goto POINTER_RETURN_FRAMES;
> + }
> }
>
> - pcm_ptr_bytes = hw_ptr - hw_base;
> + ret = regmap_read(regmap, memif_data->reg_ofs_base, &hw_base_lower32);
> + if (ret || hw_base_lower32 == 0) {
Same here.
> + dev_err(dev, "%s hw_base_lower32 err\n", __func__);
> + goto POINTER_RETURN_FRAMES;
> + }
> + if (memif_data->reg_ofs_base_msb) {
> + ret = regmap_read(regmap, memif_data->reg_ofs_base_msb, &hw_base_upper32);
> + if (ret) {
> + dev_err(dev, "%s hw_base_upper32 err\n", __func__);
> + goto POINTER_RETURN_FRAMES;
> + }
> + }
> + hw_ptr = ((unsigned long long)hw_ptr_upper32 << 32) + hw_ptr_lower32;
> + hw_base = ((unsigned long long)hw_base_upper32 << 32) + hw_base_lower32;
Instead the check should be here. And to follow the original logic,
if either pointer value is zero, the function should return zero here
directly.
ChenYu
> POINTER_RETURN_FRAMES:
> - return bytes_to_frames(substream->runtime, pcm_ptr_bytes);
> + pcm_ptr_bytes = MTK_ALIGN_16BYTES(hw_ptr - hw_base);
> + return bytes_to_frames(substream->runtime, (ssize_t)pcm_ptr_bytes);
> }
> EXPORT_SYMBOL_GPL(mtk_afe_pcm_pointer);
>
> diff --git a/sound/soc/mediatek/common/mtk-afe-platform-driver.h b/sound/soc/mediatek/common/mtk-afe-platform-driver.h
> index fcc923b88f12..71070b26f8f8 100644
> --- a/sound/soc/mediatek/common/mtk-afe-platform-driver.h
> +++ b/sound/soc/mediatek/common/mtk-afe-platform-driver.h
> @@ -12,6 +12,8 @@
> #define AFE_PCM_NAME "mtk-afe-pcm"
> extern const struct snd_soc_component_driver mtk_afe_pcm_platform;
>
> +#define MTK_ALIGN_16BYTES(x) ((x) & GENMASK_ULL(39, 4))
> +
> struct mtk_base_afe;
> struct snd_pcm;
> struct snd_soc_component;
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-07-22 7:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:15 [PATCH v6 00/10] ASoC: mediatek: Add support for MT8196 SoC Darren.Ye
2025-07-08 11:15 ` [PATCH v6 01/10] ASoC: mediatek: common: modify mtk afe platform driver for mt8196 Darren.Ye
2025-07-22 7:38 ` Chen-Yu Tsai [this message]
2025-07-08 11:15 ` [PATCH v6 02/10] ASoC: mediatek: mt8196: add common header Darren.Ye
2025-07-30 8:23 ` Chen-Yu Tsai
2025-07-08 11:15 ` [PATCH v6 03/10] ASoC: mediatek: mt8196: support audio clock control Darren.Ye
2025-07-30 8:42 ` Chen-Yu Tsai
2025-07-08 11:15 ` [PATCH v6 04/10] ASoC: mediatek: mt8196: support ADDA in platform driver Darren.Ye
2025-07-29 11:45 ` Chen-Yu Tsai
2025-07-08 11:15 ` [PATCH v6 05/10] ASoC: mediatek: mt8196: support I2S " Darren.Ye
2025-08-11 11:03 ` Chen-Yu Tsai
2025-08-21 9:10 ` Darren Ye (叶飞)
2025-08-11 11:24 ` Chen-Yu Tsai
2025-07-08 11:15 ` [PATCH v6 06/10] ASoC: mediatek: mt8196: support TDM " Darren.Ye
2025-07-28 10:53 ` Chen-Yu Tsai
2025-08-21 8:58 ` Darren Ye (叶飞)
2025-07-08 11:15 ` [PATCH v6 07/10] ASoC: mediatek: mt8196: add " Darren.Ye
2025-08-05 10:40 ` Chen-Yu Tsai
2025-07-08 11:16 ` [PATCH v6 08/10] ASoC: dt-bindings: mediatek,mt8196-afe: add audio AFE Darren.Ye
2025-07-15 5:09 ` Chen-Yu Tsai
2025-07-15 7:34 ` Chen-Yu Tsai
2025-07-16 12:41 ` Darren Ye (叶飞)
2025-07-17 2:16 ` Chen-Yu Tsai
2025-07-08 11:16 ` [PATCH v6 09/10] ASoC: mediatek: mt8196: add machine driver with nau8825 Darren.Ye
2025-07-21 9:17 ` Chen-Yu Tsai
2025-07-08 11:16 ` [PATCH v6 10/10] ASoC: dt-bindings: mediatek,mt8196-nau8825: Add audio sound card Darren.Ye
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=CAGXv+5HQcGiUnsaOxHz86Y8JxUHh6e0ypusFEBLKchNx3fqKBA@mail.gmail.com \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=darren.ye@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).