From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D5998F6D for ; Mon, 9 Oct 2023 12:48:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9586093; Mon, 9 Oct 2023 05:48:13 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 3A32068CFE; Mon, 9 Oct 2023 14:48:06 +0200 (CEST) Date: Mon, 9 Oct 2023 14:48:05 +0200 From: Christoph Hellwig To: Geert Uytterhoeven Cc: Robin Murphy , Christoph Hellwig , iommu@lists.linux.dev, Marek Szyprowski , Wei Fang , Shenwei Wang , Clark Wang , NXP Linux Team , linux-m68k@lists.linux-m68k.org, netdev@vger.kernel.org, Jim Quinlan , linux-riscv , Linux-Renesas , "Lad, Prabhakar" , arm-soc Subject: Re: [PATCH 1/6] dma-direct: add depdenencies to CONFIG_DMA_GLOBAL_POOL Message-ID: <20231009124805.GA7042@lst.de> References: <20231009074121.219686-1-hch@lst.de> <20231009074121.219686-2-hch@lst.de> <20231009091625.GB22463@lst.de> <20231009094330.GA24836@lst.de> <1cd44af1-10ac-465a-8d20-e0aa268e036f@arm.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net 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.