From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752249AbdF3MRo (ORCPT ); Fri, 30 Jun 2017 08:17:44 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34832 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751911AbdF3MRm (ORCPT ); Fri, 30 Jun 2017 08:17:42 -0400 Date: Fri, 30 Jun 2017 14:17:23 +0200 (CEST) From: Thomas Gleixner To: Linus Walleij cc: LKML , Marc Zyngier , Brian Norris , Heiko Stuebner , "open list:ARM/Rockchip SoC..." , Julia Cartwright , "linux-gpio@vger.kernel.org" , John Keeping , Doug Anderson , Tomasz Figa , Krzysztof Kozlowski , Sylwester Nawrocki , Kukjin Kim , "linux-arm-kernel@lists.infradead.org" , linux-samsung-soc Subject: Re: [patch 1/5] pinctrl: samsung: Remove bogus irq_[un]mask from resource management In-Reply-To: Message-ID: References: <20170629213334.375848050@linutronix.de> <20170629214343.882576048@linutronix.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 Jun 2017, Linus Walleij wrote: > On Thu, Jun 29, 2017 at 11:33 PM, Thomas Gleixner wrote: > > > The irq chip callbacks irq_request/release_resources() have absolutely no > > business with masking and unmasking the irq. > > > > The core code unmasks the interrupt after complete setup and masks it > > before invoking irq_release_resources(). > > > > The unmask is actually harmful as it happens before the interrupt is > > completely initialized in __setup_irq(). > > > > Remove it. > > > > Fixes: f6a8249f9e55 ("pinctrl: exynos: Lock GPIOs as interrupts when used as EINTs") > > Signed-off-by: Thomas Gleixner > > Cc: Tomasz Figa > > Cc: Krzysztof Kozlowski > > Cc: Sylwester Nawrocki > > Cc: Linus Walleij > > Cc: Kukjin Kim > > Cc: linux-arm-kernel@lists.infradead.org > > Cc: linux-samsung-soc@vger.kernel.org > > Cc: linux-gpio@vger.kernel.org > > Reviewed-by: Linus Walleij > > Does this patch have a dependency on the rest of the series or should > I just apply it as-is? Has no dependecies at all.