[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250120120806.4d1fd70e@kernel.org>
Date: Mon, 20 Jan 2025 12:08:06 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Roger Quadros <rogerq@...nel.org>
Cc: Peter Ujfalusi <peter.ujfalusi@...il.com>, Vinod Koul
<vkoul@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, MD Danish Anwar <danishanwar@...com>, Siddharth
Vadapalli <s-vadapalli@...com>, Vignesh Raghavendra <vigneshr@...com>,
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().
Assuming this goes via the DMA tree:
Acked-by: Jakub Kicinski <kuba@...nel.org>
--
pw-bot: nap
Powered by blists - more mailing lists