Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753401Ab3FQQ4j (ORCPT ); Mon, 17 Jun 2013 12:56:39 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:32870 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752801Ab3FQQ4g (ORCPT ); Mon, 17 Jun 2013 12:56:36 -0400 MIME-Version: 1.0 In-Reply-To: References: <1371058399-31933-1-git-send-email-dianders@chromium.org> <1371141522-29255-3-git-send-email-dianders@chromium.org> Date: Mon, 17 Jun 2013 18:56:36 +0200 Message-ID: Subject: Re: [PATCH v2 3/3] pinctrl: exynos: ack level-triggered interrupts before unmasking From: Linus Walleij To: Doug Anderson Cc: Kukjin Kim , Tomasz Figa , Olof Johansson , Simon Glass , Luigi Semenzato , Ilho Lee , Eunki Kim , linux-samsung-soc , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1185 Lines: 29 On Thu, Jun 13, 2013 at 8:20 PM, Linus Walleij wrote: > On Thu, Jun 13, 2013 at 6:38 PM, Doug Anderson wrote: > >> A level-triggered interrupt should be acked after the interrupt line >> becomes inactive and before it is unmasked, or else another interrupt >> will be immediately triggered. Acking before or after calling the >> handler is not enough. >> >> Signed-off-by: Luigi Semenzato >> Signed-off-by: Doug Anderson >> --- >> Changes in v2: >> - Greatly simplified using Tomasz's suggestion of irqd_get_trigger_type >> - Moved acking out of the bank spinlock since since it's not needed. >> - Linus W. has already applied parts 1 and 2, so not resending. > > Thanks, this v2 version applied with Tomasz ACK. As noted this thing exploded due to patch fuzzing. Could you respin this on top of my "devel" branch? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/