From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Vinod Koul <vkoul@kernel.org>, <dmaengine@vger.kernel.org>
Cc: Sekhar Nori <nsekhar@ti.com>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] dmaengine: ti: k3-udma-glue: move psi-l pairing in channel en/dis functions
Date: Wed, 4 Nov 2020 13:32:20 +0200 [thread overview]
Message-ID: <c9857385-1af4-55eb-722f-cd8b00512378@ti.com> (raw)
In-Reply-To: <62a8dc0b-821d-c3a6-279c-97b3082b898c@ti.com>
On 02/11/2020 09:46, Peter Ujfalusi wrote:
>
>
> On 30/10/2020 22.30, Grygorii Strashko wrote:
>> The NAVSS UDMA will stuck if target IP module is disabled by PM while PSI-L
>> threads are paired UDMA<->IP and no further transfers is possible. This
>> could be the case for IPs J721E Main CPSW (cpsw9g).
>>
>> Hence, to avoid such situation do PSI-L threads pairing only when UDMA
>> channel is going to be enabled as at this time DMA consumer module expected
>> to be active already.
>
> Is this patch on top of the AM64 (BCDMA/PKTDMA) series or not?
> Will it cause any conflict?
No. It was not based on top of AM64 series and I've not checked for conflicts.
>
> Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> ---
>> drivers/dma/ti/k3-udma-glue.c | 64 +++++++++++++++++++++--------------
>> 1 file changed, 38 insertions(+), 26 deletions(-)
...
--
Best regards,
grygorii
next prev parent reply other threads:[~2020-11-04 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 20:30 [PATCH] dmaengine: ti: k3-udma-glue: move psi-l pairing in channel en/dis functions Grygorii Strashko
2020-11-02 7:46 ` Peter Ujfalusi
2020-11-04 11:32 ` Grygorii Strashko [this message]
2020-11-09 11:54 ` 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=c9857385-1af4-55eb-722f-cd8b00512378@ti.com \
--to=grygorii.strashko@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=vigneshr@ti.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