Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2960207iog; Mon, 27 Jun 2022 06:31:55 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vDk0c2+PZooojt7OEgewGVjMhMVmxnp1dBx1M7GEDPGIev9AtHTkXee4lOSVXZeYv1UIJB X-Received: by 2002:a17:902:7282:b0:16b:7a53:3b41 with SMTP id d2-20020a170902728200b0016b7a533b41mr6560458pll.1.1656336715162; Mon, 27 Jun 2022 06:31:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656336715; cv=none; d=google.com; s=arc-20160816; b=0MNiPgyX3MiFzN3ulXdzzZS86yhIQnyOGEjMhJys13GAf2G6yx7wYX74/vK35O0Y8z KepkLEcxSAoy9BLyQHNsXzEQ2TZc3Ea4BiPZb/jBz24e1iSKivoir/nOzH5vKRJo2VfY iAovVjvcjR0RD2v3i5AnWGSgWNhKrVjYxq+9kf+Qtt2ZR0roUCvWOn+XeSosMzvnV/Bn c/aDuzbCCxUwae2RZ4OS1iG7ENKEBaPE45j0zAh5mU6jkOImGyZJVEy7gC3IlQHHdKll ExCsXd0ccEIh1TVUVltU9FdaA6BWUqew7De4xyaQxBsTpcVOtv4Fqxe5omIqwfvnG89j mLng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=kOSI8zp0jjxL5+CxolovAvYdFi+BiCcWlLjESh/UX/A=; b=CwbRcURpdKdBXjxyK0fk086bToe3/6w4Nl7r3HBDtftjWiXCTs9nRBP+cxJpP1Izbi chj1mUwWbqqXtrB5Xq6pb9fVXK0BPnUsq1SJ9irb9PdQ5DvusUAcmMmmpLeLw+R2ISZ9 /BOeyn3h1r145hpE91IwIg99isxnda8L9kIdKFjvtKYIO+CZsYegdxr+zdLbo8b0Ntr8 6pd5GQK2SSUKUEAL905U8haPFOzYph6YacRa4/grikpSZTa+k3K5xaXU3jQjB4pfoGvT +7naktIbi8J0MNfkISMg2v2GgjOM1nYS+5t1ZUrJF9Ybhpfg819HWYWNjhq+a0cUyJ2M fNLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=pHkkuP5Q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m75-20020a633f4e000000b003ab7a1a2193si15356715pga.151.2022.06.27.06.31.41; Mon, 27 Jun 2022 06:31:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=pHkkuP5Q; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234295AbiF0NG7 (ORCPT + 99 others); Mon, 27 Jun 2022 09:06:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39282 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234707AbiF0NGq (ORCPT ); Mon, 27 Jun 2022 09:06:46 -0400 Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9A20165C1; Mon, 27 Jun 2022 06:06:32 -0700 (PDT) Received: by mail-ej1-x62b.google.com with SMTP id cw10so19067785ejb.3; Mon, 27 Jun 2022 06:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kOSI8zp0jjxL5+CxolovAvYdFi+BiCcWlLjESh/UX/A=; b=pHkkuP5Q6EifbGayLDb0Ez91DuQx5xkhc7QCQ0k+IT34Ns9HcJSehFYOEZX129kJLq 4S8r1tOQeEiTjNdu51RsxAD6S6J1ciPSuWHY5hRT53ATbCu2St/zspi0Le62FvgBlAt5 vXrLIbtl+2fyvBRWIGQ84HxG/Z9KcA9yZjs6fyux7BQBLgl6jvhd0vPxkOsf/Ox0IXcg fpbJTgBhgmq5AAm8s70wmFHoi7K5JHltfXni+FekAFAlsWfRLN1tkYdB7sAqM4LpTJ85 wQD5KtqGMknCMQ1o0xKPb5MecVivc6TvIxNjLtdeiACpQN/JNVyIF75+3tqmAK8u3x6e wxUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kOSI8zp0jjxL5+CxolovAvYdFi+BiCcWlLjESh/UX/A=; b=Cpujh2e8zMrpMhEdEdDjK8NWUPt96+W++RdW4EvPKlM57dchaWhvf2Qj3nR/pKg+OM o7DCbFaDtUBt79TPG9Vwz7gGLUsCvmEcqVjiFyzp25vs5pj0+Q2OiDN5NqaLRUrLq6Am TEsLyDE/wbhDS7bS9UOnvIxxSK89EHwnpYW769HunInyDdxu4Qd5Zwg40qbymH6nKMV8 XBaInrwzjeOqzkMD/OypRZyq1e2BxVWTwUZg/BKwGsjXteh2Gpajxb2VXJUEBMkfcaFw hqKP7FLD/xSakdVhwF+TfmS4fQpsnEDNNDtZRuDyR1Z/4HLnl5ZYeDKbsuEDAEkJ0WdY 7/5Q== X-Gm-Message-State: AJIora97VDSjl+2i6ctGsjzJle3Yp69swZsyzbD+BkGZ51XAdIBNfVRI Ukvl2OWqp1bd2QcoWotMcUa9q86hTQUCx4ETlZw= X-Received: by 2002:a17:906:b05a:b0:718:cc6b:61e0 with SMTP id bj26-20020a170906b05a00b00718cc6b61e0mr12731068ejb.501.1656335190863; Mon, 27 Jun 2022 06:06:30 -0700 (PDT) MIME-Version: 1.0 References: <20220626004326.8548-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20220626004326.8548-3-prabhakar.mahadev-lad.rj@bp.renesas.com> <87wnd3erab.wl-maz@kernel.org> <87v8snehwi.wl-maz@kernel.org> In-Reply-To: From: "Lad, Prabhakar" Date: Mon, 27 Jun 2022 14:06:04 +0100 Message-ID: Subject: Re: [PATCH v2 2/2] irqchip/sifive-plic: Add support for Renesas RZ/Five SoC To: Geert Uytterhoeven Cc: Marc Zyngier , Lad Prabhakar , Thomas Gleixner , Rob Herring , Krzysztof Kozlowski , Sagar Kadam , Palmer Dabbelt , Paul Walmsley , linux-riscv , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Geert Uytterhoeven , Linux-Renesas , LKML , Biju Das Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, On Mon, Jun 27, 2022 at 9:53 AM Geert Uytterhoeven wrote: > > Hi Marc, > > On Sun, Jun 26, 2022 at 2:19 PM Marc Zyngier wrote: > > On Sun, 26 Jun 2022 10:38:18 +0100, > > "Lad, Prabhakar" wrote: > > > On Sun, Jun 26, 2022 at 9:56 AM Marc Zyngier wrote: > > > > On Sun, 26 Jun 2022 01:43:26 +0100, > > > > Lad Prabhakar wrote: > > > > > The Renesas RZ/Five SoC has a RISC-V AX45MP AndesCore with NCEPLIC100. The > > > > > NCEPLIC100 supports both edge-triggered and level-triggered interrupts. In > > > > > case of edge-triggered interrupts NCEPLIC100 ignores the next interrupt > > > > > edge until the previous completion message has been received and > > > > > NCEPLIC100 doesn't support pending interrupt counter, hence losing the > > > > > interrupts if not acknowledged in time. > > > > > > > > > > So the workaround for edge-triggered interrupts to be handled correctly > > > > > and without losing is that it needs to be acknowledged first and then > > > > > handler must be run so that we don't miss on the next edge-triggered > > > > > interrupt. > > > > > > > > > > This patch adds a new compatible string for Renesas RZ/Five SoC and adds > > > > > support to change interrupt flow based on the interrupt type. It also > > > > > implements irq_ack and irq_set_type callbacks. > > > > > > > > > > Signed-off-by: Lad Prabhakar > > > > > > + if (of_device_is_compatible(node, "renesas,r9a07g043-plic")) { > > > > > + priv->of_data = RENESAS_R9A07G043_PLIC; > > > > > + plic_chip.name = "Renesas RZ/Five PLIC"; > > > > > > > > NAK. The irq_chip structure isn't the place for platform marketing. > > > > This is way too long anyway (and same for the edge version), and you > > > > even sent me a patch to make that structure const... > > > > > > > My bad will drop this. > > > > And why you're at it, please turn this rather random 'of_data' into > > something like: > > > > diff --git a/drivers/irqchip/irq-sifive-plic.c b/drivers/irqchip/irq-sifive-plic.c > > index bb87e4c3b88e..cd1683b77caf 100644 > > --- a/drivers/irqchip/irq-sifive-plic.c > > +++ b/drivers/irqchip/irq-sifive-plic.c > > @@ -64,6 +64,10 @@ struct plic_priv { > > struct cpumask lmask; > > struct irq_domain *irqdomain; > > void __iomem *regs; > > + enum { > > + VANILLA_PLIC, > > + RENESAS_R9A07G043_PLIC, > > + } flavour; > > }; > > > > struct plic_handler { > > > > to give some structure to the whole thing, because I'm pretty sure > > we'll see more braindead implementations as time goes by. > > What about using a feature flag (e.g. had_edge_irqs) instead? > diff --git a/drivers/irqchip/irq-sifive-plic.c b/drivers/irqchip/irq-sifive-plic.c index 9f16833dcb41..247c3c98b655 100644 --- a/drivers/irqchip/irq-sifive-plic.c +++ b/drivers/irqchip/irq-sifive-plic.c @@ -60,13 +60,13 @@ #define PLIC_DISABLE_THRESHOLD 0x7 #define PLIC_ENABLE_THRESHOLD 0 +#define PLIC_QUIRK_EDGE_INTERRUPT BIT(0) struct plic_priv { struct cpumask lmask; struct irq_domain *irqdomain; void __iomem *regs; + u32 plic_quirks; }; What about something like above? Cheers, Prabhakar