[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230223113644.23356-1-jiaxun.yang@flygoat.com>
Date: Thu, 23 Feb 2023 11:36:39 +0000
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: linux-mips@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
tsbogend@...ha.franken.de, mpe@...erman.id.au,
paul.walmsley@...ive.com, palmer@...belt.com, robh+dt@...nel.org,
hch@....de, m.szyprowski@...sung.com, robin.murphy@....com,
linux-riscv@...ts.infradead.org,
Jiaxun Yang <jiaxun.yang@...goat.com>
Subject: [PATCH v2 0/5] Use dma_default_coherent for devicetree default coherency
Hi all,
This series split out second half of my previous series
"[PATCH 0/4] MIPS DMA coherence fixes".
It intends to use dma_default_coherent to determine the default coherency of
devicetree probed devices instead of hardcoding it with Kconfig options.
For some MIPS systems, dma_default_coherent is determined with either
bootloader or hardware registers in platform initilization code, and devicetree
does not explicility specify the coherency of the device, so we need the ability
to change the default coherency of devicetree probed devices.
For other platforms that supports noncoherent, dma_default_coherent is a fixed
value set by arch code. It's defaulted to false for most archs except RISC-V.
Thanks
- Jiaxun
---
v2:
- Add PATCH 1 to help with backporting
- Use Kconfig option to set dma_default_coherent
Jiaxun Yang (5):
of: address: Fix default coherency for MIPS
dma-mapping: Provide a fallback dma_default_coherent
dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT
riscv: Select ARCH_DMA_DEFAULT_COHERENT
of: address: Always use dma_default_coherent for default coherency
arch/powerpc/Kconfig | 1 -
arch/riscv/Kconfig | 2 +-
drivers/of/Kconfig | 4 ----
drivers/of/address.c | 2 +-
include/linux/dma-map-ops.h | 1 +
kernel/dma/Kconfig | 3 +++
kernel/dma/mapping.c | 6 +++++-
7 files changed, 11 insertions(+), 8 deletions(-)
--
2.37.1 (Apple Git-137.1)
Powered by blists - more mailing lists