From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
mpe@ellerman.id.au, paul.walmsley@sifive.com, palmer@dabbelt.com,
Rob Herring <robh+dt@kernel.org>,
m.szyprowski@samsung.com, Robin Murphy <robin.murphy@arm.com>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
iommu@lists.linux.dev
Subject: Re: [PATCH v4 0/3] Use dma_default_coherent for devicetree default coherency
Date: Thu, 6 Apr 2023 08:12:01 +0100 [thread overview]
Message-ID: <C51B954E-FA96-450D-BB4F-D8D9D1FFC525@flygoat.com> (raw)
In-Reply-To: <20230401091531.47412-1-jiaxun.yang@flygoat.com>
> 2023年4月1日 10:15,Jiaxun Yang <jiaxun.yang@flygoat.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)
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-04-06 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 9:15 [PATCH v4 0/3] Use dma_default_coherent for devicetree default coherency Jiaxun Yang
2023-04-01 9:15 ` [PATCH v4 1/3] dma-mapping: Provide a fallback dma_default_coherent Jiaxun Yang
2023-04-01 9:15 ` [PATCH v4 2/3] dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT Jiaxun Yang
2023-04-01 9:15 ` [PATCH v4 3/3] of: address: Always use dma_default_coherent for default coherency Jiaxun Yang
2023-04-06 7:12 ` Jiaxun Yang [this message]
2023-04-07 5:39 ` [PATCH v4 0/3] Use dma_default_coherent for devicetree " 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=C51B954E-FA96-450D-BB4F-D8D9D1FFC525@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=mpe@ellerman.id.au \
--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).