From: "Kumar, Udit" <u-kumar1@ti.com>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>,
<peter.ujfalusi@gmail.com>, <vkoul@kernel.org>
Cc: <vaishnav.a@ti.com>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] dmaengine: ti: k3-udma: Use cap_mask directly from dma_device structure instead of a local copy
Date: Mon, 27 Jan 2025 16:27:57 +0530 [thread overview]
Message-ID: <7bea4592-01d6-4e19-90e4-e645dfe9631e@ti.com> (raw)
In-Reply-To: <20250117121728.203452-1-y-abhilashchandra@ti.com>
Hi Abhilash,
On 1/17/2025 5:47 PM, Yemike Abhilash Chandra wrote:
> Currently, a local dma_cap_mask_t variable is used to store device
> cap_mask within udma_of_xlate(). However, the DMA_PRIVATE flag in
> the device cap_mask can get cleared when the last channel is released.
> This can happen right after storing the cap_mask locally in
> udma_of_xlate() and subsequent dma_request_channel() can fail due to
> mismatch in the cap_mask. Fix this by removing the local dma_cap_mask_t
This should carry fixes tag
> variable and directly using the one from the dma_device structure.
>
> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> ---
> drivers/dma/ti/k3-udma.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/dma/ti/k3-udma.c b/drivers/dma/ti/k3-udma.c
> index 7ed1956b4642..c775a2284e86 100644
> --- a/drivers/dma/ti/k3-udma.c
> +++ b/drivers/dma/ti/k3-udma.c
> @@ -4246,7 +4246,6 @@ static struct dma_chan *udma_of_xlate(struct of_phandle_args *dma_spec,
> struct of_dma *ofdma)
> {
> struct udma_dev *ud = ofdma->of_dma_data;
> - dma_cap_mask_t mask = ud->ddev.cap_mask;
> struct udma_filter_param filter_param;
> struct dma_chan *chan;
>
> @@ -4278,7 +4277,7 @@ static struct dma_chan *udma_of_xlate(struct of_phandle_args *dma_spec,
> }
> }
>
> - chan = __dma_request_channel(&mask, udma_dma_filter_fn, &filter_param,
> + chan = __dma_request_channel(&ud->ddev.cap_mask, udma_dma_filter_fn, &filter_param,
> ofdma->of_node);
With addition of fixes tag in subject,
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> if (!chan) {
> dev_err(ud->dev, "get channel fail in %s.\n", __func__);
prev parent reply other threads:[~2025-01-27 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 12:17 [PATCH RFC] dmaengine: ti: k3-udma: Use cap_mask directly from dma_device structure instead of a local copy Yemike Abhilash Chandra
2025-01-22 15:24 ` Péter Ujfalusi
2025-01-27 10:57 ` Kumar, Udit [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=7bea4592-01d6-4e19-90e4-e645dfe9631e@ti.com \
--to=u-kumar1@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vaishnav.a@ti.com \
--cc=vkoul@kernel.org \
--cc=y-abhilashchandra@ti.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