Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp3741119iog; Tue, 28 Jun 2022 01:33:37 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sPu9oeRq5jUcHmzr8CbWyypljFj1ocFkNlQMS7aR7Q4jTyp5YAKcdeIVVxHq4f4RJL2UZH X-Received: by 2002:a17:902:ecca:b0:16a:53a0:75 with SMTP id a10-20020a170902ecca00b0016a53a00075mr3670664plh.43.1656405217045; Tue, 28 Jun 2022 01:33:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656405217; cv=none; d=google.com; s=arc-20160816; b=s3naqwU8fhQoexRexZ3O5McH3Ux+LQsmAoMxoNx7ubv70YZ2o+Ayk15on5yUd/F+EA aNu+kcFWE8K7tX35Lba6pONgBzD2nxT2jLcTzuU8wIG+hV4WJScGjXIRLcjOd8kvsVdt H3ANCcsA7yGKjorzVIseKr5vdyZFcBLUmSyLazKPNMUmhGu8naKzcDJBgo0FtXxMAeqI giK2YTQzyVJPC8Bep8MTYevrZ38M10rdbuig3+62R4rS/O6SlNszJ82MzE8msYZpo77+ ebvBloLnmsq7v/evG99eD2j/4EEl2e67X1SjEu5gyGxsJzU49mLSgJzvj1S7xcX3pbjC sWMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=2TpQEUwBlGb88p4IGzi7coXlKXR6VM/Rxu7edgxZRdk=; b=VnhW7r8Lv4NLf+twNq5Hot48s87t6z9X0kEYqwur8Lwq8RLWldoWhjID49BSneNAOk 4luerXQpTPSnvKupFsEoZXGgoXXUX0VT8sX1Uh3/HtD2ByrKMVQWyULWwEbxo7hkyJGC 6iIdYqzLyib/JsQGp9IKrCQ9f4cv66HVgMSNuEXKZKTvLAXXC63g1QciSbUlI/xxAwZI pr6r/S95idYhvnNgQbheUxr7T1DnOpy+I5zA1e4lC4S757tjQ20MRYt4PGojFq2eo6XT qShVCDhqiMlgXiq0jzWFM2Uuuw1FgwogNl+doN+j/mDD5zojJqlNTKDi5UK+E30XWbjr n6oA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=aDHAR+gT; 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 j15-20020a056a00174f00b0052568123ceasi11181980pfc.315.2022.06.28.01.33.24; Tue, 28 Jun 2022 01:33:37 -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=aDHAR+gT; 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 S245330AbiF1IbD (ORCPT + 99 others); Tue, 28 Jun 2022 04:31:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53492 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245258AbiF1IbB (ORCPT ); Tue, 28 Jun 2022 04:31:01 -0400 Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B033626AC5 for ; Tue, 28 Jun 2022 01:31:00 -0700 (PDT) Received: by mail-pg1-x52d.google.com with SMTP id 9so11506959pgd.7 for ; Tue, 28 Jun 2022 01:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=2TpQEUwBlGb88p4IGzi7coXlKXR6VM/Rxu7edgxZRdk=; b=aDHAR+gThE7DCHiMc4w+Xv3mkdu4rkVcgXPF4v+8X8PUvOGiD8/v36X1k4A6RW/uNs Wcs/s0KQGad+czgeUL1BFEdgFXjpzIGT9VHf1J3Btmuqn5TWE1SO9k3Ub1Cuj2wPXdjP oiHmgyW3Mo1xkPaGmn+cEOLw9ylL/C2D5qGfZNSwOS4wUGIXKAQsYoRB3mscXSt9hez0 6DsC1Mnw75dCIc/sU+YFSvQTk+9Ik1HJc+8FpUxpk7njKXZhvdr8dGLt8h34iV3XUKkz zAJL1cMHV+FtKiGWoDgKggTNoEugbHIL95tfX/HdtkUF9FBTCUSyWxKu+o8Z230rCi/n 5IJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=2TpQEUwBlGb88p4IGzi7coXlKXR6VM/Rxu7edgxZRdk=; b=eLHF4dUEi3xxAJb83BRIqH/r4q0BCJY+yYt3l/krF5ZGbpZPu1t3sBro47hIzXk1ia F9+e4Vt10hbg8BxkgTDAD/egwms9xUdtM64ykUHVkfGUsOFxdqsU+eyY4r853RJ/p2BI 9SiAGAtKbSkqkPfqWFmwMuYUYyKHOfBe/bZxox1rWoGngwK8Z+jh385g/TtI5Sq6/yFw uqaxJHZ8st4q7KfEiNQ7P2YZwoGgJCqwpez95Lb+j4TVmXp+rSeTJPbtxkvvzOadcNLv XL7q1kqKhL14vCs+wKzLNX7tEML3GwbbJdi7/NVlkoB4p3geW7YhgKSb0iMlRFg64KA6 mbkA== X-Gm-Message-State: AJIora8bA6KshoyomLay/4bOzltRFHvZI+EeBPEYNfXxE0HJW7FqlMnZ bAHDid4pjQCqJjM6iBr3WHs= X-Received: by 2002:a05:6a00:1489:b0:525:b83f:b32f with SMTP id v9-20020a056a00148900b00525b83fb32fmr3542633pfu.25.1656405059955; Tue, 28 Jun 2022 01:30:59 -0700 (PDT) Received: from localhost ([2409:10:24a0:4700:e8ad:216a:2a9d:6d0c]) by smtp.gmail.com with ESMTPSA id u9-20020a170902e5c900b0016760c06b76sm250708plf.194.2022.06.28.01.30.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Jun 2022 01:30:59 -0700 (PDT) Date: Tue, 28 Jun 2022 17:30:57 +0900 From: Stafford Horne To: Marc Zyngier Cc: LKML , Openrisc , Jonas Bonn , Stefan Kristiansson , Thomas Gleixner Subject: Re: [PATCH] irqchip: or1k-pic: Undefine mask_ack for level triggered hardware Message-ID: References: <20220628012854.681220-1-shorne@gmail.com> <877d512o0a.wl-maz@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877d512o0a.wl-maz@kernel.org> 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 On Tue, Jun 28, 2022 at 09:25:25AM +0100, Marc Zyngier wrote: > On Tue, 28 Jun 2022 02:28:54 +0100, > Stafford Horne wrote: > > > > The mask_ack operation clears the interrupt by writing to the PICSR > > register. This we don't want for level triggered interrupt because > > it does not actually clear the interrupt on the source hardware. > > > > This was causing issues in qemu with multi core setups where > > interrupts would continue to fire even though they had been cleared in > > PICSR. > > > > Just remove the mask_ack operation. > > > > Signed-off-by: Stafford Horne > > --- > > Note, > > > > I currently have this queued with openrisc fixes for 5.19-rcX. If this is ok > > with the IRQ maintainers I would like to have this merged via the OpenRISC > > queue. > > > > drivers/irqchip/irq-or1k-pic.c | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/drivers/irqchip/irq-or1k-pic.c b/drivers/irqchip/irq-or1k-pic.c > > index 49b47e787644..f289ccd95291 100644 > > --- a/drivers/irqchip/irq-or1k-pic.c > > +++ b/drivers/irqchip/irq-or1k-pic.c > > @@ -66,7 +66,6 @@ static struct or1k_pic_dev or1k_pic_level = { > > .name = "or1k-PIC-level", > > .irq_unmask = or1k_pic_unmask, > > .irq_mask = or1k_pic_mask, > > - .irq_mask_ack = or1k_pic_mask_ack, > > }, > > .handle = handle_level_irq, > > .flags = IRQ_LEVEL | IRQ_NOPROBE, > > Acked-by: Marc Zyngier > > Feel free to take this via your tree. Thanks, -Stafford