Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] dmaengine: ti: k3-udma-glue: move psi-l pairing in
 channel en/dis functions
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>
References: <20201030203000.4281-1-grygorii.strashko@ti.com>
 <62a8dc0b-821d-c3a6-279c-97b3082b898c@ti.com>
From:   Grygorii Strashko <grygorii.strashko@ti.com>
Message-ID: <c9857385-1af4-55eb-722f-cd8b00512378@ti.com>
Date:   Wed, 4 Nov 2020 13:32:20 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <62a8dc0b-821d-c3a6-279c-97b3082b898c@ti.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


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