From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: linux-mips@vger.kernel.org
Cc: tsbogend@alpha.franken.de, linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
robh+dt@kernel.org, palmer@dabbelt.com, paul.walmsley@sifive.com,
robin.murphy@arm.com, linuxppc-dev@lists.ozlabs.org, hch@lst.de,
m.szyprowski@samsung.com
Subject: [PATCH 1/7] MIPS: Remove DMA_PERDEV_COHERENT
Date: Tue, 21 Feb 2023 12:46:07 +0000 [thread overview]
Message-ID: <20230221124613.2859-2-jiaxun.yang@flygoat.com> (raw)
In-Reply-To: <20230221124613.2859-1-jiaxun.yang@flygoat.com>
As now we are always managing DMA coherence on per dev bias,
there is no need to have such option. And it's not selected
by any platform.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
arch/mips/Kconfig | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 15cb692b0a09..c6f3ad51f741 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -134,7 +134,6 @@ choice
config MIPS_GENERIC_KERNEL
bool "Generic board-agnostic MIPS kernel"
- select ARCH_HAS_SETUP_DMA_OPS
select MIPS_GENERIC
select BOOT_RAW
select BUILTIN_DTB
@@ -1079,11 +1078,6 @@ config FW_CFE
config ARCH_SUPPORTS_UPROBES
bool
-config DMA_PERDEV_COHERENT
- bool
- select ARCH_HAS_SETUP_DMA_OPS
- select DMA_NONCOHERENT
-
config DMA_NONCOHERENT
bool
#
@@ -1097,6 +1091,7 @@ config DMA_NONCOHERENT
select ARCH_HAS_DMA_PREP_COHERENT
select ARCH_HAS_SYNC_DMA_FOR_DEVICE
select ARCH_HAS_DMA_SET_UNCACHED
+ select ARCH_HAS_SETUP_DMA_OPS
select DMA_NONCOHERENT_MMAP
select NEED_DMA_MAP_STATE
--
2.37.1 (Apple Git-137.1)
next prev parent reply other threads:[~2023-02-21 17:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:46 [PATCH 0/7] MIPS DMA coherence fixes Jiaxun Yang
2023-02-21 12:46 ` Jiaxun Yang [this message]
2023-02-21 17:56 ` [PATCH 1/7] MIPS: Remove DMA_PERDEV_COHERENT Christoph Hellwig
2023-02-21 12:46 ` [PATCH 2/7] MIPS: Always select ARCH_HAS_SYNC_DMA_FOR_CPU for noncoherent platforms Jiaxun Yang
2023-02-21 12:46 ` [PATCH 3/7] MIPS: c-r4k: Always install dma flush functions Jiaxun Yang
2023-02-21 12:46 ` [PATCH 4/7] dma-mapping: Always provide dma_default_coherent Jiaxun Yang
2023-02-21 17:58 ` Christoph Hellwig
2023-02-21 19:35 ` Robin Murphy
2023-02-21 19:56 ` Jiaxun Yang
2023-02-21 12:46 ` [PATCH 5/7] dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT Jiaxun Yang
2023-02-21 17:58 ` Christoph Hellwig
2023-02-21 18:18 ` Jiaxun Yang
2023-02-21 12:46 ` [PATCH 6/7] riscv: Select ARCH_DMA_DEFAULT_COHERENT Jiaxun Yang
2023-02-21 18:14 ` Conor Dooley
2023-02-21 18:20 ` Jiaxun Yang
2023-02-21 12:46 ` [PATCH 7/7] of: address: Use dma_default_coherent to determine default coherency Jiaxun Yang
2023-02-21 17:54 ` [PATCH 0/7] MIPS DMA coherence fixes Christoph Hellwig
2023-02-21 18:15 ` Jiaxun Yang
2023-02-21 19:46 ` Robin Murphy
2023-02-21 19:55 ` Jiaxun Yang
2023-02-22 12:55 ` Robin Murphy
2023-02-22 13:04 ` Jiaxun Yang
2023-02-22 14:22 ` Robin Murphy
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=20230221124613.2859-2-jiaxun.yang@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tsbogend@alpha.franken.de \
/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).