Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934246AbbEMMXG (ORCPT ); Wed, 13 May 2015 08:23:06 -0400 Received: from mail-la0-f45.google.com ([209.85.215.45]:36181 "EHLO mail-la0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754509AbbEMMXE (ORCPT ); Wed, 13 May 2015 08:23:04 -0400 MIME-Version: 1.0 Reply-To: semen.protsenko@globallogic.com In-Reply-To: References: <1429637257-11055-1-git-send-email-semen.protsenko@globallogic.com> Date: Wed, 13 May 2015 15:23:01 +0300 Message-ID: Subject: Re: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller From: Sam Protsenko To: Linus Walleij Cc: Alexandre Courbot , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 920 Lines: 21 On Tue, May 12, 2015 at 10:34 AM, Linus Walleij wrote: > OK yeah, maybe we could provide a list of "usual suspects", what do you > say about "my" expanders: > > drivers/gpio/gpio-stmpe.c > drivers/gpio/gpio-tc3589x.c > > I can surely patch and test these. This issue seems to be pretty common for all GPIO chips that have IRQ chip capability. So your expanders should be patched too. But still, the best course here is to actually reproduce the issue first, and only then proceed to patching. So if you have boards with those expanders -- it should be easy to come up with some use-case that reproduces the issue mentioned in the original commit. -- 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/