mbox series

[v3,0/7] DMA40 SRAM refactoring and cleanup

Message ID 20230417-ux500-dma40-cleanup-v3-0-60bfa6785968@linaro.org (mailing list archive)
Headers show
Series DMA40 SRAM refactoring and cleanup | expand

Message

Linus Walleij May 16, 2023, 12:55 p.m. UTC 
I started out by augmenting the STE DMA40 driver to get
its LCPA SRAM memory from a proper SRAM handle in the
device tree instead of as a reg cell, and then I saw
that the driver was in a bit of sad state so I did a bit
of cleanups on top.

Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v3:
- Rebased on v6.4-rc1
- Fixed a cast for a complaining print in probe()
- Collected ACKs on the DT bindings.
- Link to v2: https://lore.kernel.org/r/20230417-ux500-dma40-cleanup-v2-0-cdaa68a4b863@linaro.org

Changes in v2:
- Amendments to the bindings after review.
- Link to v1: https://lore.kernel.org/r/20230417-ux500-dma40-cleanup-v1-0-b26324956e47@linaro.org

---
Linus Walleij (7):
      dt-bindings: dma: dma40: Prefer to pass sram through phandle
      dmaengine: ste_dma40: Get LCPA SRAM from SRAM node
      dmaengine: ste_dma40: Add dev helper variable
      dmaengine: ste_dma40: Remove platform data
      dmaengine: ste_dma40: Pass dev to OF function
      dmaengine: ste_dma40: Use managed resources
      dmaengine: ste_dma40: Return error codes properly

 .../devicetree/bindings/dma/stericsson,dma40.yaml  |  36 ++-
 drivers/dma/Kconfig                                |   1 +
 drivers/dma/ste_dma40.c                            | 336 +++++++++------------
 .../dma-ste-dma40.h => drivers/dma/ste_dma40.h     | 101 +------
 drivers/dma/ste_dma40_ll.c                         |   3 +-
 5 files changed, 183 insertions(+), 294 deletions(-)
---
base-commit: a2f15a1753d590f30c07d439a04ec7e839cd2305
change-id: 20230417-ux500-dma40-cleanup-fe4f8d9b19c5

Best regards,

Comments

Vinod Koul May 16, 2023, 5:30 p.m. UTC | #1 
On 16-05-23, 14:55, Linus Walleij wrote:
> I started out by augmenting the STE DMA40 driver to get
> its LCPA SRAM memory from a proper SRAM handle in the
> device tree instead of as a reg cell, and then I saw
> that the driver was in a bit of sad state so I did a bit
> of cleanups on top.

Applied, thanks