[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174065806076.367410.10114461097310533807.b4-ty@kernel.org>
Date: Thu, 27 Feb 2025 17:37:40 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Peter Ujfalusi <peter.ujfalusi@...il.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
MD Danish Anwar <danishanwar@...com>,
Siddharth Vadapalli <s-vadapalli@...com>,
Vignesh Raghavendra <vigneshr@...com>, Roger Quadros <rogerq@...nel.org>
Cc: srk@...com, dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] dmaengine: ti: k3-udma-glue: Drop skip_fdq argument
from k3_udma_glue_reset_rx_chn
On Thu, 16 Jan 2025 17:00:46 +0200, Roger Quadros wrote:
> The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can
> run on multiple platforms having different DMA architectures.
> On some platforms there can be one FDQ for all flows in the RX channel
> while for others there is a separate FDQ for each flow in the RX channel.
>
> So far we have been relying on the skip_fdq argument of
> k3_udma_glue_reset_rx_chn().
>
> [...]
Applied, thanks!
[1/1] dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn
commit: 0da30874729baeb01889b0eca16cfda122687503
Best regards,
--
~Vinod
Powered by blists - more mailing lists