[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176061935426.510550.684278188506408313.b4-ty@kernel.org>
Date: Thu, 16 Oct 2025 18:25:54 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>,
Yixun Lan <dlan@...too.org>, Guodong Xu <guodong@...cstar.com>
Cc: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, linux-riscv@...ts.infradead.org,
spacemit@...ts.linux.dev, elder@...cstar.com,
Naresh Kamboju <naresh.kamboju@...aro.org>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] dmaengine: mmp_pdma: fix DMA mask handling
On Thu, 18 Sep 2025 22:27:27 +0800, Guodong Xu wrote:
> The driver's existing logic for setting the DMA mask for "marvell,pdma-1.0"
> was flawed. It incorrectly relied on pdev->dev->coherent_dma_mask instead
> of declaring the hardware's fixed addressing capability. A cleaner and
> more correct approach is to define the mask directly based on the hardware
> limitations.
>
> The MMP/PXA PDMA controller is a 32-bit DMA engine. This is supported by
> datasheets and various dtsi files for PXA25x, PXA27x, PXA3xx, and MMP2,
> all of which are 32-bit systems.
>
> [...]
Applied, thanks!
[1/1] dmaengine: mmp_pdma: fix DMA mask handling
commit: 88ebb29d3244e515a92c2331434bb73fef7efdc6
Best regards,
--
~Vinod
Powered by blists - more mailing lists