[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231009124805.GA7042@lst.de>
Date: Mon, 9 Oct 2023 14:48:05 +0200
From: Christoph Hellwig <hch@....de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Robin Murphy <robin.murphy@....com>, Christoph Hellwig <hch@....de>,
iommu@...ts.linux.dev, Marek Szyprowski <m.szyprowski@...sung.com>,
Wei Fang <wei.fang@....com>, Shenwei Wang <shenwei.wang@....com>,
Clark Wang <xiaoning.wang@....com>,
NXP Linux Team <linux-imx@....com>, linux-m68k@...ts.linux-m68k.org,
netdev@...r.kernel.org, Jim Quinlan <james.quinlan@...adcom.com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@...renesas.com>,
arm-soc <soc@...nel.org>
Subject: Re: [PATCH 1/6] dma-direct: add depdenencies to
CONFIG_DMA_GLOBAL_POOL
On Mon, Oct 09, 2023 at 01:10:26PM +0200, Geert Uytterhoeven wrote:
> RISCV_DMA_NONCOHERENT does not select DMA_GLOBAL_POOL,
> ARCH_R9A07G043 selects DMA_GLOBAL_POOL.
> RISCV_DMA_NONCOHERENT does select DMA_DIRECT_REMAP if MMU.
Yeah, and we'll basically need to split RISCV_DMA_NONCOHERENT into
an option for each type of non-coherent support. This is why we
should never have added support for any of the non-standard versions,
as it's turning into a giant mess.
Powered by blists - more mailing lists