Received: by 2002:a05:6358:f14:b0:e5:3b68:ec04 with SMTP id b20csp40987rwj; Thu, 22 Dec 2022 04:46:23 -0800 (PST) X-Google-Smtp-Source: AMrXdXsk8+A3w4iirPesTxEbnSih7sokGvfPQ+VtLGjO52isNmOUui5ky6YEM9gCHNKpF+WG0CrH X-Received: by 2002:a17:907:d08d:b0:7aa:76a:fb3 with SMTP id vc13-20020a170907d08d00b007aa076a0fb3mr5221480ejc.66.1671713183529; Thu, 22 Dec 2022 04:46:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671713183; cv=none; d=google.com; s=arc-20160816; b=FKHJEvDNEFYZMnIAWU6IV5+i8MrlprchK6lsrfNCCAsHsnFdk6utuhq2OgcLDBCoRl gem6da2NwciRchLwv5Qkpcm14MdEcbdqALdSxGoywME4VKAKFDjc3y5Ejtyf5kmFZHFC daYTe4RAVufA+XsuEI8M08YqciZJbJ5irov0YsLkcaT1kq2upXJvFM/gZLx/LDQHyjIz w1dDfoScWPdRzlIb3d5Zmur3mgn3H9LaFeEq3LfCtRD0ohV4F2loi/jErUF9mHwB+Qxv vgR3oKPBKjo32M/KbWpnYf+8dJlLd/SRQ4apkh5JcUsLsR5J/z0TpWRtnz18s90gouHL ZRQQ== 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=TufOMWDEgv+LdQVF9KDrnCcYkAYV1qSL3kWuyPvOfwA=; b=bN5Le7bFVM1XTYNfaLCJYsJv9Q9r+0/RpaMWxZOqZM1SRMzNRganuBQL1QQ6ejjN36 BlHnEScisx+PKgtsXJPB4cTKdm8Um5GbWnFESihpMlQ+FUFjLl3BeZqp6wmh2GeaaXyH vkNiYth+u6gwwiM1S60IzU3tIu7JmWvrVFXroRndtgy++vMZdbNAOzioXBkJva0hntO8 puuO0j4rX6GBLHIJVx2JiAbU8WREIpvQPA7PUUGT2O603BwMg+X6Jw+Zb6WFAU8hv/9M yFBnFD+6ZiZyuH1fkjW0SuacnSBAI2+d448mNkfvMhMP+aJe2Iy9k3cEjcRhW7DWSspx Y/jA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=inQmetdI; 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 ji20-20020a170907981400b007adfe2889efsi384842ejc.607.2022.12.22.04.46.08; Thu, 22 Dec 2022 04:46:23 -0800 (PST) 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=inQmetdI; 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 S235582AbiLVMAW (ORCPT + 67 others); Thu, 22 Dec 2022 07:00:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34504 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235849AbiLVL7v (ORCPT ); Thu, 22 Dec 2022 06:59:51 -0500 Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 307CA286C2; Thu, 22 Dec 2022 03:52:47 -0800 (PST) Received: by mail-ej1-x635.google.com with SMTP id tz12so4307121ejc.9; Thu, 22 Dec 2022 03:52:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TufOMWDEgv+LdQVF9KDrnCcYkAYV1qSL3kWuyPvOfwA=; b=inQmetdI5RRs36eir0mFdFWZ18MrFXh78ZYY6/l70HHY/dZKkEA0oU1esZNBUfrWvT XjQjK270kGKoSxURgH4GLqBFHbVdpg2GEKryI1ow6BRVpGmmiimPNPX2iwgDhudaulo7 3I2llcftHQOdIS+ajTrp/qSSmX1pIbOkpAeDwovR+Qri+Bmv3sM/6o1N63LAT2CmdaIa HC9QZN3mPXOLvEXC17kBbod8fyt0KcJ4TzfZp0+HxoRRSOltH6AZ0mf4USGuCELzDsUA kaCrZY2oZlB83r6kJwURh88ng06s4eNDyEXjl82bHRXsEBzj5HnSJj3vvn23f5IPSETc I+cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TufOMWDEgv+LdQVF9KDrnCcYkAYV1qSL3kWuyPvOfwA=; b=O2qS0UgbObHzNM/9NTdmVVjvLsi5V6Lgrti+rSM3f1JbYkaIUezym7RTI5vdMmicCy yrZIWEPTc+4J2P/rmJX9v0ZmeUpcu6OZyXd+K5kGCFkiZTVVOPcCkgYbzoC4eQV/06/i ha91kVrZemQdJg14e6vRfX6hOg9cy/SnDQabW8dd2T6ROQGVJyKOG94esHOu8AqqnFYh PNNG6lcCKhMpCDc5irRD4Qh9ePmtycSBEovfi2rA2UhPInn0xavG+WLwDSHEU9XZVtWF C99zQyEM/owRVAyT0KJPKEjpbj075dDL3dOFfs7eo/5Tl2TiPX60pQijiQVKkBzkCsJa cauA== X-Gm-Message-State: AFqh2koeoNIN/ZFclNmiTm23ej00/Pww26/IH7vrayobtQDiuensNSFa ORkb2hXbEOayjDOWb7OUI2D0QKH2eH5uzKBhVDsYvMn7fPQ= X-Received: by 2002:a17:906:b01:b0:7c1:808e:765b with SMTP id u1-20020a1709060b0100b007c1808e765bmr340816ejg.196.1671709965796; Thu, 22 Dec 2022 03:52:45 -0800 (PST) MIME-Version: 1.0 References: <20221221000242.340202-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20221221000242.340202-4-prabhakar.mahadev-lad.rj@bp.renesas.com> <86mt7haw0h.wl-maz@kernel.org> In-Reply-To: <86mt7haw0h.wl-maz@kernel.org> From: "Lad, Prabhakar" Date: Thu, 22 Dec 2022 11:52:19 +0000 Message-ID: Subject: Re: [PATCH v2 3/9] irqchip: irq-renesas-rzg2l: Skip mapping NMI interrupt as part of hierarchy domain To: Marc Zyngier , Geert Uytterhoeven Cc: Thomas Gleixner , Rob Herring , Krzysztof Kozlowski , Magnus Damm , Linus Walleij , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org, Biju Das , Lad Prabhakar 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 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 Marc, Geert, On Wed, Dec 21, 2022 at 10:31 AM Marc Zyngier wrote: > > On Wed, 21 Dec 2022 00:02:36 +0000, > Prabhakar wrote: > > > > From: Lad Prabhakar > > > > NMI interrupt is not an external interrupt as compared to the IRQ0-7 and > > TINT0-31, this means we need to install the irq handler for NMI in the > > IRQC driver and not include it as part of IRQ domain. > > > > This patch skips mapping NMI interrupt as part of the IRQ domain > > hierarchy. > > Does it mean nobody can connect anything to it? Where is the handler > you're mentioning for this NMI? > I got this clarified internally the NMI interrupt is an external interrupt just like the other IRQ0-7/TINT interrupts. I'll drop this patch in the next version. Cheers, Prabhakar