linux-kernel - Re: [PATCH v4 0/3] Use dma_default_coherent for devicetree default coherency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <C51B954E-FA96-450D-BB4F-D8D9D1FFC525@flygoat.com>
Date:   Thu, 6 Apr 2023 08:12:01 +0100
From:   Jiaxun Yang <jiaxun.yang@...goat.com>
To:     Christoph Hellwig <hch@....de>
Cc:     "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
        linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        mpe@...erman.id.au, paul.walmsley@...ive.com, palmer@...belt.com,
        Rob Herring <robh+dt@...nel.org>, m.szyprowski@...sung.com,
        Robin Murphy <robin.murphy@....com>,
        linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
        iommu@...ts.linux.dev
Subject: Re: [PATCH v4 0/3] Use dma_default_coherent for devicetree default
 coherency



> 2023年4月1日 10:15，Jiaxun Yang <jiaxun.yang@...goat.com> 写道：
> 
> 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
> and powerpc in some cases.

Ping.

Is there any issue remain in this series?

Thanks
Jiaxun

> 
> Thanks
> - Jiaxun
> ---
> v2:
>  - Add PATCH 1 to help with backporting
>  - Use Kconfig option to set dma_default_coherent 
> 
> v3:
>  - Style fixes
>  - Squash setting ARCH_DMA_DEFAULT_COHERENT into PATCH 4
>  - Setting ARCH_DMA_DEFAULT_COHERENT for PowerPC
> 
> v4:
>  - Drop first patch
> 
> Jiaxun Yang (3):
>  dma-mapping: Provide a fallback dma_default_coherent
>  dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT
>  of: address: Always use dma_default_coherent for default coherency
> 
> arch/powerpc/Kconfig        | 2 +-
> arch/riscv/Kconfig          | 2 +-
> drivers/of/Kconfig          | 4 ----
> drivers/of/address.c        | 2 +-
> include/linux/dma-map-ops.h | 2 ++
> kernel/dma/Kconfig          | 7 +++++++
> kernel/dma/mapping.c        | 6 +++++-
> 7 files changed, 17 insertions(+), 8 deletions(-)
> 
> -- 
> 2.39.2 (Apple Git-143)
>