Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2616418pxb; Sun, 17 Oct 2021 20:37:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJykoS+ZhFCLIcyG+LtGvPdgiHlRmGlC12Fa8LyzVtB6i2dKhdd7Hn6Onr8c60Lzoam/Vpcb X-Received: by 2002:a65:6aa8:: with SMTP id x8mr21274275pgu.136.1634528234808; Sun, 17 Oct 2021 20:37:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634528234; cv=none; d=google.com; s=arc-20160816; b=f/I/3Z9NFLZ579+m4Fh15Hwjv122GCmmPnB4iirl01ZfwpdRZeGebWAQZjWUtJJKSq kx6pLY2L5W6q/As3SXaANK1cePUciQQ28X/c+5GDImrGBlZz+pXitb97oF3k36jXVKTY qXle54Bvo9VRxpb2A8lZ9lmGCAAE27xWjWbhppVjYVGCmcBR7ArCOS/y+vc2mOV9Ael4 5puRe37mPLSiljRS0M0exDkJv6Q02eDoCthkTWNtzQxk2X6FDN18B9q6ZQc9nnckGN63 xQ9unuVgaBht9NZotIhjSJBN8mnWix7aBzjpeMqJy5ultWutwdW/4r1InVkGeAqPXKPv gVzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=2a3Q+/mIdE3CXxpDe5QLD4lxtDVBYyEDiPEhMcWZOoA=; b=Pgf/ZST8zvuFk7IA2Ocs1OmE3lqllMD+agiiYBJvKgSVz/HahhWhOkOy9yx0AB0WOs IAp/bcNxGU+cjsrkWMJjeBeSgwMrCU9VBOVcc3wnYa19wYy7qVV3E+qaK+C6IPaORq2D B3DVWDA4+fBqdCk7uQEQQkupXYpc802FolwgYm74F5CPKfzBxyy+DhyaIydSvVGzixf+ v8TMlXqxHuEw00Nd+0eQ7uPmo7gniQ9MmvJcwpqRmq7B+rWqFBx6I/EMdcS2iKv/uHaS hGTRv1bDAV5GYXgegltoKqlI+bYrcX7j5sKgmcq7jixM5LjM/YRUnnDyPe7pGsRNVq7E ShZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m21si26447620pgu.294.2021.10.17.20.37.03; Sun, 17 Oct 2021 20:37:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240728AbhJPQeD (ORCPT + 98 others); Sat, 16 Oct 2021 12:34:03 -0400 Received: from gloria.sntech.de ([185.11.138.130]:46128 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230526AbhJPQeC (ORCPT ); Sat, 16 Oct 2021 12:34:02 -0400 Received: from p508fce7c.dip0.t-ipconnect.de ([80.143.206.124] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbmb6-0007eW-PS; Sat, 16 Oct 2021 18:31:48 +0200 From: Heiko Stuebner To: Guo Ren Cc: Anup Patel , Atish Patra , Marc Zyngier , Thomas Gleixner , Palmer Dabbelt , Rob Herring , Linux Kernel Mailing List , linux-riscv , Guo Ren , Palmer Dabbelt Subject: Re: [PATCH V4 2/3] dt-bindings: update riscv plic compatible string Date: Sat, 16 Oct 2021 18:31:47 +0200 Message-ID: <1708236.01x493v0YS@phil> In-Reply-To: References: <20211016032200.2869998-1-guoren@kernel.org> <2216787.nSqPeTNalD@phil> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Samstag, 16. Oktober 2021, 14:56:51 CEST schrieb Guo Ren: > On Sat, Oct 16, 2021 at 6:35 PM Heiko Stuebner wrote: > > > > Hi Guo, > > > > Am Samstag, 16. Oktober 2021, 05:21:59 CEST schrieb guoren@kernel.org: > > > From: Guo Ren > > > > > > Add the compatible string "thead,c900-plic" to the riscv plic > > > bindings to support allwinner d1 SOC which contains c906 core. > > > > The compatible strings sound good now, but some things below > > > > > > > > Signed-off-by: Guo Ren > > > Cc: Rob Herring > > > Cc: Palmer Dabbelt > > > Cc: Anup Patel > > > Cc: Atish Patra > > > > > > --- > > > > > > Changes since V4: > > > - Update description in errata style > > > - Update enum suggested by Anup, Heiko, Samuel > > > > > > Changes since V3: > > > - Rename "c9xx" to "c900" > > > - Add thead,c900-plic in the description section > > > --- > > > .../interrupt-controller/sifive,plic-1.0.0.yaml | 11 ++++++++++- > > > 1 file changed, 10 insertions(+), 1 deletion(-) > > > > > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml > > > index 08d5a57ce00f..272f29540135 100644 > > > --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml > > > +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml > > > @@ -35,6 +35,12 @@ description: > > > contains a specific memory layout, which is documented in chapter 8 of the > > > SiFive U5 Coreplex Series Manual . > > > > > > + The C9xx PLIC does not comply with the interrupt claim/completion process defined > > > + by the RISC-V PLIC specification because C9xx PLIC will mask an IRQ when it is > > > + claimed by PLIC driver (i.e. readl(claim) and the IRQ will be unmasked upon > > > + completion by PLIC driver (i.e. writel(claim). This behaviour breaks the handling > > > + of IRQS_ONESHOT by the generic handle_fasteoi_irq() used in the PLIC driver. > > > + > > > maintainers: > > > - Sagar Kadam > > > - Paul Walmsley > > > @@ -46,7 +52,10 @@ properties: > > > - enum: > > > - sifive,fu540-c000-plic > > > - canaan,k210-plic > > > - - const: sifive,plic-1.0.0 > > > + - enmu: > > > > ^ spelling enum > > > > > + - sifive,plic-1.0.0 > > > + - thead,c900-plic > > > + - allwinner,sun20i-d1-plic > > > > but in general I'd think that you want something like > > > > compatible: > > oneOf: > > - items: > > - enum: > > - sifive,fu540-c000-plic > > - canaan,k210-plic > > - const: sifive,plic-1.0.0 > > - items: > > - enum: > > - allwinner,sun20i-d1-plic > > - const: thead,c900-plic > > > > Having only one item list would allow as valid combinations like > > "sifive,fu540-c000-plic", "thead,c900-plic" when checking the schema. > > > > With the oneOf and separate lists we can make sure that such > > "illegal" combinations get flagged by the dtbs_check > > > > [the enum with the single allwinner entry already leaves > > room for later addition to the c900-plic variant] > Thx, I'll fix it in the next version. > > another question: Is the allwinner_sun20i_d1_plic needed to IRQCHIP_DECLARE? > > +IRQCHIP_DECLARE(thead_c900_plic, "thead,c900-plic", thead_c900_plic_init); > +IRQCHIP_DECLARE(allwinner_sun20i_d1_plic, "allwinner,sun20i-d1-plic", > thead_c900_plic_init); Doing IRQCHIP_DECLARE(thead_c900_plic, "thead,c900-plic", thead_c900_plic_init); should be enough for now. Compatible-parsing happens from left to right, from most-specific to most-generic. So having the allwinner-d1 compatible in there is sort of a safeguard. If at some _later point in time_ , some specific new quirk of the D1 implementation comes to light, we can _then_ just add a IRQCHIP_DECLARE(allwinner_d1_plic, "allwinner,sun20i-d1-plic", allwinner_d1_plic_init); Devicetrees should be stable and newer kernels should work with old devicetrees, so having the soc-specific compatible in there just makes it future proof :-) Heiko