[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e34b098-bdab-448e-a34a-02bdc643f700@oss.nxp.com>
Date: Thu, 29 Jan 2026 11:25:17 +0200
From: Daniel Baluta <daniel.baluta@....nxp.com>
To: Shengjiu Wang <shengjiu.wang@....com>, lgirdwood@...il.com,
broonie@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, shawnguo@...nel.org, s.hauer@...gutronix.de,
kernel@...gutronix.de, festevam@...il.com, linux-sound@...r.kernel.org,
devicetree@...r.kernel.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
shengjiu.wang@...il.com, Xiubo.Lee@...il.com, nicoleotsuka@...il.com,
perex@...ex.cz, tiwai@...e.com, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH 3/3] ASoC: fsl_asrc_dma: allocate memory from dma device
On 1/28/26 09:18, Shengjiu Wang wrote:
> As the dma device may support dma-coherent property on the i.MX952,
> allocate memory from dma device to make asrc driver to be compatible with
> such a case.
This commit message refers to imx952 but the change in the code apply to all supported platforms
So in not really clear what is the intention of it.
Also, it is not clear why do you allocate a pair only to free it at the end of the function.
Powered by blists - more mailing lists