From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 76589C4360C for ; Thu, 10 Oct 2019 13:51:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 557B72067B for ; Thu, 10 Oct 2019 13:51:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726100AbfJJNvm (ORCPT ); Thu, 10 Oct 2019 09:51:42 -0400 Received: from muru.com ([72.249.23.125]:36904 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726067AbfJJNvl (ORCPT ); Thu, 10 Oct 2019 09:51:41 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id D7D9E80BB; Thu, 10 Oct 2019 13:52:14 +0000 (UTC) Date: Thu, 10 Oct 2019 06:51:38 -0700 From: Tony Lindgren To: Yi Zheng Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, Jason Cooper , Sekhar Nori , Zheng Yi Subject: Re: Maybe a bug in kernel/irq/chip.c unmask_irq(), device IRQ masked unexpectedly. (re-formated the mail body, sorry) Message-ID: <20191010135138.GU5610@atomide.com> References: <20191009174500.GM5610@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Yi Zheng [191010 06:22]: > Hi > > My patch is canceled. I have tested that simple adjustment, the > device IRQ masked unexpectedly. It seems that it is more easily to > occur with that patch. > > So, the root cause is not found yet. OK. Based on your description, it could be a missing flush of a posted write somewhere in the gpio-omap or intc path. Regards, Tony