[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231020054024.78295-1-hch@lst.de>
Date: Fri, 20 Oct 2023 07:40:16 +0200
From: Christoph Hellwig <hch@....de>
To: Greg Ungerer <gerg@...ux-m68k.org>,
iommu@...ts.linux.dev
Cc: Robin Murphy <robin.murphy@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Wei Fang <wei.fang@....com>,
Shenwei Wang <shenwei.wang@....com>,
Clark Wang <xiaoning.wang@....com>,
NXP Linux Team <linux-imx@....com>,
linux-m68k@...ts.linux-m68k.org,
netdev@...r.kernel.org
Subject: fix the non-coherent coldfire dma_alloc_coherent v4
Hi all,
this is the next attempt to not return memory that is not DMA coherent
on coldfire/m68knommu. The last one needed more fixups in the fec
driver, which this versions includes. On top of that I've also added
a few more cleanups to the core DMA allocation code.
Note: without the separately submitted
fix a few RISC-V / renesas Kconfig dependencies
series this will cause Kconfig warnings on riscv. These warnings are
due to real dependency issues, so I do not plan to hold the series for
those patches to be applied.
Changes since v2:
- drop the separatly submitted riscv/soc patches and rebase on top of the
soc tree
- rename CONFIG_ARCH_DMA_ALLOC to ARCH_HAS_DMA_ALLOC
- fix stray CONFIG_ prefixes in a Kconfig file
Changes since v1:
- sort out the dependency mess in RISCV
- don't even built non-coherent DMA support for coldfire cores without
data caches
- apply the fec workarounds to all coldfire platforms with data caches
- add a trivial cleanup for m68k dma.c
Powered by blists - more mailing lists