Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2671648pxb; Sun, 17 Oct 2021 22:18:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzzY3mvAFOwEHddHTSqNLRPAY3HwDbbB4yhAqgBpxEesdhr8xHk1db0dRwDnR6BQe4vo+wv X-Received: by 2002:a17:90b:2391:: with SMTP id mr17mr3751471pjb.61.1634534324787; Sun, 17 Oct 2021 22:18:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634534324; cv=none; d=google.com; s=arc-20160816; b=MAmQp+kWCUxGnr7RTrUY0JiFglSaGriTmeIdlIPL3qndK6mbTNkjublEYRxNpGi+6t RWgE0nSaiMAx7eGXa8OZ19aCbNvxAhfa8qCS5MJ/2YdKChhKMZJDSLSKzo23KORt6PwA VY7Hv+MwpkAZuaXUNQi6YAHMmaozIokjew6JmUbpTdslBKJc81dxp12X8kRcydeJAjHP 7vPWnNmnxqoirv8Qzaeod5m7nHSv7+06Em0yToUpeuBYTsfpnkEb87efudu0ZIEPkZwn N7HPHfb/3GeVaTeT3IvYggJXQjvmGhOJvWBF2gmf1foeSVtiZe7XWWBGUiYNvWORWiSZ 02bw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject:from :references:cc:to:dkim-signature:dkim-signature; bh=9YkoD4PdwekwWd/mgjOWSIeRZK66Yv4uJGo/UC0l1Uk=; b=fuId8deae5vOp5r2Y+lUOTgHwmVunmBrhzRknQQ/pUdniqGJebfvfIuoxrVEOg6xYk yzBiRzZ1YY9t0W1GldMtorL1jjPrLDgYl2tKpcwuM2afNhsWmOfV341L8ncdTemr1bU/ +5oQnidYtHJj75DJzTF7Pa40V0rdIKh3JoClQRgmUCjUnLVzQAKU4yERtKGGnFBJbhrc +GmHSt/KrTgHTdhsV3oSvZBcaAKvg4vaYSckpC4zNZA4i09rtLI0rWdqBRAvXsa235SS P+maxZzIw5CuyTilnLJz6hr043Nf+PP3zuosbJOhBx8JpIhOJX2Jd8P8jxXiZBwTSe9P daFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sholland.org header.s=fm1 header.b=dh0+fsF9; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=bXHNcv7P; 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 gp5si7407908pjb.139.2021.10.17.22.18.31; Sun, 17 Oct 2021 22:18:44 -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; dkim=pass header.i=@sholland.org header.s=fm1 header.b=dh0+fsF9; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=bXHNcv7P; 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 S229804AbhJRFTk (ORCPT + 99 others); Mon, 18 Oct 2021 01:19:40 -0400 Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]:50165 "EHLO wnew1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229534AbhJRFTk (ORCPT ); Mon, 18 Oct 2021 01:19:40 -0400 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.west.internal (Postfix) with ESMTP id 947952B0118D; Mon, 18 Oct 2021 01:17:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 18 Oct 2021 01:17:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sholland.org; h= to:cc:references:from:subject:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=9 YkoD4PdwekwWd/mgjOWSIeRZK66Yv4uJGo/UC0l1Uk=; b=dh0+fsF9EWRzEBaCx FgOJHtVnFljMiw6UJSPyGWG+nbgaONZg0W82EYep1orekmQesYkdNxyRFbIAFzto 3YAjbdzRsZ8BEUC5pjmOgKDfeyCRfOftCCvPXwfFu+LwfbN1Hll+Ye3xdm3hmj3Y g9UPk5eMXm5LqRyo+e8lOtm/62Kf17pChR2dTqhpWVuL+/NpYGZjPGbOjROtnXuS ATBdcFQ8Lf3n84aAobddauGbnr4A7Kpk7yK/N+umJsZrPG2ePKUkOHwikBU881IB pYbqGfYOtNVQoBjb65RUkQ3uHKf1av3i6NWqaI2OAT51643MPjsm/WV8hBa2Nkao phsKQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=9YkoD4PdwekwWd/mgjOWSIeRZK66Yv4uJGo/UC0l1 Uk=; b=bXHNcv7PuP7jRnDsNs06uCguh3ZhbG6RweK0kpQnY56iJYcE9CdTGsHq6 RETy8rNDrZSRXip/LvkCYPwblva1fflF0E+AQGVWkIcHedpmjHWDpOz5Asux/wJa viJc6x0zOH23eZCXLOeCzOClhimFHsm6B0olVVgoPmuzK2T2A9mFOPFGPIW3HX9O nOI1rld4Df+JAAwqFfSP2/n8f8MIsdNGArX70RoIZx4bCBfMe2wt1Dw9lgiCSoH0 gCpme3jws39dD7ovmRSExOTfqpOzVH9E6bH32VzczIyMbxiMayspURTc4WX3xGkA IT0mNsTAh+k6XkFRn/EhU2I6dwCMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdduledgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepvfhfhffukffffgggjggtgfesthekredttdefjeenucfhrhhomhepufgrmhhu vghlucfjohhllhgrnhguuceoshgrmhhuvghlsehshhholhhlrghnugdrohhrgheqnecugg ftrfgrthhtvghrnhepvddttdejieduudfgffevteekffegffeguddtgfefkeduvedukeff hedtfeevuedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepshgrmhhuvghlsehshhholhhlrghnugdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 18 Oct 2021 01:17:27 -0400 (EDT) To: guoren@kernel.org, anup@brainfault.org, atish.patra@wdc.com, maz@kernel.org, tglx@linutronix.de, palmer@dabbelt.com, heiko@sntech.de, robh@kernel.org Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, Guo Ren References: <20211016032200.2869998-1-guoren@kernel.org> <20211016032200.2869998-2-guoren@kernel.org> From: Samuel Holland Subject: Re: [PATCH V4 1/3] irqchip/sifive-plic: Add thead,c900-plic support Message-ID: <8be1bdbd-365d-cd28-79d7-b924908f9e39@sholland.org> Date: Mon, 18 Oct 2021 00:17:26 -0500 User-Agent: Mozilla/5.0 (X11; Linux ppc64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: <20211016032200.2869998-2-guoren@kernel.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/15/21 10:21 PM, guoren@kernel.org wrote: > From: Guo Ren > > 1) The irq_mask/unmask() is used by handle_fasteoi_irq() is mostly > for ONESHOT irqs and there is no limitation in the RISC-V PLIC driver > due to use of irq_mask/unmask() callbacks. In fact, a lot of irqchip > drivers using handle_fasteoi_irq() also implement irq_mask/unmask(). > > 2) 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. > > 3) This patch adds an errata fix for IRQS_ONESHOT handling on > C9xx PLIC by using irq_enable/disable() callbacks instead of > irq_mask/unmask(). > > Signed-off-by: Guo Ren > Cc: Anup Patel > Cc: Thomas Gleixner > Cc: Marc Zyngier > Cc: Palmer Dabbelt > Cc: Atish Patra > > --- > > Changes since V4: > - Update comment by Anup > > Changes since V3: > - Rename "c9xx" to "c900" > - Add sifive_plic_chip and thead_plic_chip for difference > > Changes since V2: > - Add a separate compatible string "thead,c9xx-plic" > - set irq_mask/unmask of "plic_chip" to NULL and point > irq_enable/disable of "plic_chip" to plic_irq_mask/unmask > - Add a detailed comment block in plic_init() about the > differences in Claim/Completion process of RISC-V PLIC and C9xx > PLIC. > --- > drivers/irqchip/irq-sifive-plic.c | 34 +++++++++++++++++++++++++++++-- > 1 file changed, 32 insertions(+), 2 deletions(-) > > diff --git a/drivers/irqchip/irq-sifive-plic.c b/drivers/irqchip/irq-sifive-plic.c > index cf74cfa82045..960b29d02070 100644 > --- a/drivers/irqchip/irq-sifive-plic.c > +++ b/drivers/irqchip/irq-sifive-plic.c > @@ -166,7 +166,7 @@ static void plic_irq_eoi(struct irq_data *d) > writel(d->hwirq, handler->hart_base + CONTEXT_CLAIM); > } > > -static struct irq_chip plic_chip = { > +static struct irq_chip sifive_plic_chip = { > .name = "SiFive PLIC", > .irq_mask = plic_irq_mask, > .irq_unmask = plic_irq_unmask, > @@ -176,12 +176,32 @@ static struct irq_chip plic_chip = { > #endif > }; > > +/* > + * 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. > + */ > +static struct irq_chip thead_plic_chip = { > + .name = "T-Head PLIC", > + .irq_disable = plic_irq_mask, > + .irq_enable = plic_irq_unmask, > + .irq_eoi = plic_irq_eoi, > +#ifdef CONFIG_SMP > + .irq_set_affinity = plic_set_affinity, > +#endif I tested this, and it doesn't work. Without IRQCHIP_EOI_THREADED, .irq_eoi is called at the end of the hard IRQ handler. This unmasks the IRQ before the irqthread has a chance to run, so it causes an interrupt storm for any threaded level IRQ (I saw this happen for sun8i_thermal). With IRQCHIP_EOI_THREADED, .irq_eoi is delayed until after the irqthread runs. This is good. Except that the call to unmask_threaded_irq() is inside a check for IRQD_IRQ_MASKED. And IRQD_IRQ_MASKED will never be set because .irq_mask is NULL. So the end result is that the IRQ is never EOI'd and is masked permanently. If you set .flags = IRQCHIP_EOI_THREADED, and additionally set .irq_mask and .irq_unmask to a dummy function that does nothing, the IRQ core will properly set/unset IRQD_IRQ_MASKED, and the IRQs will flow as expected. But adding dummy functions seems not so ideal, so I am not sure if this is the best solution. Regards, Samuel > +}; > + > +static struct irq_chip *def_plic_chip = &sifive_plic_chip; > + > static int plic_irqdomain_map(struct irq_domain *d, unsigned int irq, > irq_hw_number_t hwirq) > { > struct plic_priv *priv = d->host_data; > > - irq_domain_set_info(d, irq, hwirq, &plic_chip, d->host_data, > + irq_domain_set_info(d, irq, hwirq, def_plic_chip, d->host_data, > handle_fasteoi_irq, NULL, NULL); > irq_set_noprobe(irq); > irq_set_affinity(irq, &priv->lmask); > @@ -390,5 +410,15 @@ static int __init plic_init(struct device_node *node, > return error; > } > > +static int __init thead_c900_plic_init(struct device_node *node, > + struct device_node *parent) > +{ > + def_plic_chip = &thead_plic_chip; > + > + return plic_init(node, parent); > +} > + > IRQCHIP_DECLARE(sifive_plic, "sifive,plic-1.0.0", plic_init); > IRQCHIP_DECLARE(riscv_plic0, "riscv,plic0", plic_init); /* for legacy systems */ > +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); >