[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231009091625.GB22463@lst.de>
Date: Mon, 9 Oct 2023 11:16:25 +0200
From: Christoph Hellwig <hch@....de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Christoph Hellwig <hch@....de>, iommu@...ts.linux.dev,
Robin Murphy <robin.murphy@....com>,
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>
Subject: Re: [PATCH 1/6] dma-direct: add depdenencies to
CONFIG_DMA_GLOBAL_POOL
On Mon, Oct 09, 2023 at 10:43:57AM +0200, Geert Uytterhoeven wrote:
> > config DMA_DIRECT_REMAP
>
> riscv defconfig + CONFIG_NONPORTABLE=y + CONFIG_ARCH_R9A07G043=y:
>
> WARNING: unmet direct dependencies detected for DMA_GLOBAL_POOL
> Depends on [n]: !ARCH_HAS_DMA_SET_UNCACHED [=n] && !DMA_DIRECT_REMAP [=y]
> Selected by [y]:
> - ARCH_R9A07G043 [=y] && SOC_RENESAS [=y] && RISCV [=y] && NONPORTABLE [=y]
And that's exactly what this patch is supposed to show. RISCV must not
select DMA_DIRECT_REMAP at the same time as DMA_GLOBAL_POOL. I though
the fix for that just went upstream?
Powered by blists - more mailing lists