Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6CDAC6FA99 for ; Fri, 10 Mar 2023 11:57:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229546AbjCJL5E (ORCPT ); Fri, 10 Mar 2023 06:57:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229522AbjCJL5B (ORCPT ); Fri, 10 Mar 2023 06:57:01 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 28058C562E; Fri, 10 Mar 2023 03:57:00 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C739EB821BD; Fri, 10 Mar 2023 11:56:58 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 73C45C433EF; Fri, 10 Mar 2023 11:56:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1678449417; bh=7i/O5youjH9jNHfG2Dg9EU6CeFBIYVpumpfWkEMxXfU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=a46pcBzu9a477UOMmZuc+sSkhr6PUFGJwhE8oX4QMI/g4zvYUAbeYfBamCRRS6uGv Sh93VbL1dkUoaOapB6wyhvccd8w9n4+Ouuj/VUeQtIgEdQ6Z4ZosAYcfVeau9FYEUe mT1T1Ws0V3XxP/jj4VVw8ygHLIvVJceTyVKzB0gfCAjzxgO4e6o3M9H/3qD06pJQG0 ehsCcwMEkqMR8sXQIObj0WvlwnvHphmJsRHGOhd6ENkoEQ6II6GLRAfVOZVhhqEyeM sWDEipfoaGI7d6RVEBj1sMqlLswIhXSGvgwQwQfilVq3LWQtMEuSpTSNh9ofl3/Qf2 P5dNa1H/+ocEQ== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pabMl-00Gan5-3J; Fri, 10 Mar 2023 11:56:55 +0000 Date: Fri, 10 Mar 2023 11:56:54 +0000 Message-ID: <86v8j8yg3d.wl-maz@kernel.org> From: Marc Zyngier To: Peter Geis Cc: Lucas Tanure , Vinod Koul , Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski , Heiko Stuebner , Thomas Gleixner , Lorenzo Pieralisi , Krzysztof Wilczynski , Bjorn Helgaas , Qu Wenruo , Piotr Oniszczuk , Kever Yang , linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, kernel@collabora.com, Robin Murphy Subject: Re: [PATCH 1/7] irqchip/gic-v3: Add a DMA Non-Coherent flag In-Reply-To: References: <20230310080518.78054-1-lucas.tanure@collabora.com> <20230310080518.78054-2-lucas.tanure@collabora.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.2 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: pgwipeout@gmail.com, lucas.tanure@collabora.com, vkoul@kernel.org, kishon@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de, tglx@linutronix.de, lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com, wqu@suse.com, piotr.oniszczuk@gmail.com, kever.yang@rock-chips.com, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, kernel@collabora.com, robin.murphy@arm.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 10 Mar 2023 11:41:46 +0000, Peter Geis wrote: > > On Fri, Mar 10, 2023 at 3:05 AM Lucas Tanure wrote: > > > > The GIC600 integration in RK356x, used in rk3588, doesn't support > > any of the shareability or cacheability attributes, and requires > > both values to be set to 0b00 for all the ITS and Redistributor > > tables. > > > > This is loosely based on prior work from XiaoDong Huang and > > Peter Geis fixing this issue specifically for Rockchip 356x. > > Good Morning, > > Since the gic is using dma, would it be reasonable to have all memory > allocations be requested with the GFP_DMA flag? Otherwise this doesn't > fully solve the problem for rk356x, where only the lower 4GB range is > DMA capable, but this tends to get allocated in the upper 4GB on 8GB > boards. That's an erratum. Please treat as such. M. -- Without deviation from the norm, progress is not possible.