From: Christoph Hellwig <hch@lst.de>
To: Greg Ungerer <gerg@linux-m68k.org>, iommu@lists.linux.dev
Cc: Robin Murphy <robin.murphy@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Wei Fang <wei.fang@nxp.com>, Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-m68k@lists.linux-m68k.org, netdev@vger.kernel.org
Subject: fix the non-coherent coldfire dma_alloc_coherent v4
Date: Fri, 20 Oct 2023 07:40:16 +0200 [thread overview]
Message-ID: <20231020054024.78295-1-hch@lst.de> (raw)
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
next reply other threads:[~2023-10-20 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 5:40 Christoph Hellwig [this message]
2023-10-20 5:40 ` [PATCH 1/8] dma-direct: add depdenencies to CONFIG_DMA_GLOBAL_POOL Christoph Hellwig
2023-10-20 7:18 ` Geert Uytterhoeven
2023-10-23 5:50 ` Christoph Hellwig
2023-10-20 5:40 ` [PATCH 2/8] dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbol Christoph Hellwig
2023-10-20 5:40 ` [PATCH 3/8] dma-direct: simplify the use atomic pool logic in dma_direct_alloc Christoph Hellwig
2023-10-20 5:40 ` [PATCH 4/8] dma-direct: warn when coherent allocations aren't supported Christoph Hellwig
2023-10-20 5:40 ` [PATCH 5/8] m68k: use the coherent DMA code for coldfire without data cache Christoph Hellwig
2023-10-20 5:40 ` [PATCH 6/8] net: fec: use dma_alloc_noncoherent for data cache enabled coldfire Christoph Hellwig
2023-10-20 5:40 ` [PATCH 7/8] m68k: don't provide arch_dma_alloc for nommu/coldfire Christoph Hellwig
2023-10-20 5:40 ` [PATCH 8/8] m68k: remove unused includes from dma.c Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231020054024.78295-1-hch@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=iommu@lists.linux.dev \
--cc=linux-imx@nxp.com \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).