From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Matthew Majewski <mattwmajewski@gmail.com>,
Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ti: edma: support sw triggered chans in of_edma_xlate()
Date: Wed, 19 Feb 2025 17:06:54 +0200 [thread overview]
Message-ID: <55d56d32-64b5-4cef-8c1c-fb29b7b93b87@gmail.com> (raw)
In-Reply-To: <20250216214741.207538-1-mattwmajewski@gmail.com>
On 16/02/2025 23:47, Matthew Majewski wrote:
> The .of_edma_xlate() function always sets the hw_triggered flag to
> true. This causes sw triggered channels consumed via the device-tree
> to not function properly, as the driver incorrectly assumes they are
> hw triggered. Modify the xlate() function to correctly set the
> hw_triggered flag to false for channels reserved for memcpy
> operation (ie, sw triggered).
>
> Signed-off-by: Matthew Majewski <mattwmajewski@gmail.com>
Good catch,
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
> ---
> drivers/dma/ti/edma.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/ti/edma.c b/drivers/dma/ti/edma.c
> index 4ece125b2ae7..0554a18d84ba 100644
> --- a/drivers/dma/ti/edma.c
> +++ b/drivers/dma/ti/edma.c
> @@ -2258,8 +2258,12 @@ static struct dma_chan *of_edma_xlate(struct of_phandle_args *dma_spec,
>
> return NULL;
> out:
> - /* The channel is going to be used as HW synchronized */
> - echan->hw_triggered = true;
> + /*
> + * The channel is going to be HW synchronized, unless it was
> + * reserved as a memcpy channel
> + */
> + echan->hw_triggered =
> + !edma_is_memcpy_channel(i, ecc->info->memcpy_channels);
> return dma_get_slave_channel(chan);
> }
> #else
--
Péter
next prev parent reply other threads:[~2025-02-19 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 21:47 [PATCH] dmaengine: ti: edma: support sw triggered chans in of_edma_xlate() Matthew Majewski
2025-02-19 15:06 ` Péter Ujfalusi [this message]
2025-03-10 21:06 ` Vinod Koul
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=55d56d32-64b5-4cef-8c1c-fb29b7b93b87@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattwmajewski@gmail.com \
--cc=vkoul@kernel.org \
/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