Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753038AbbEDNcj (ORCPT ); Mon, 4 May 2015 09:32:39 -0400 Received: from mail-oi0-f42.google.com ([209.85.218.42]:36381 "EHLO mail-oi0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752324AbbEDNcc (ORCPT ); Mon, 4 May 2015 09:32:32 -0400 MIME-Version: 1.0 In-Reply-To: <1429637257-11055-1-git-send-email-semen.protsenko@globallogic.com> References: <1429637257-11055-1-git-send-email-semen.protsenko@globallogic.com> Date: Mon, 4 May 2015 15:32:31 +0200 Message-ID: Subject: Re: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller From: Linus Walleij To: Semen Protsenko 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: 762 Lines: 24 On Tue, Apr 21, 2015 at 7:27 PM, Semen Protsenko wrote: > Set .irq_set_wake callback to prevent possible issues on wake-up. > > This patch was inspired by this commit: > b80eef95beb04760629822fa130aeed54cdfafca > > Signed-off-by: Semen Protsenko Are these real, observed issues? Patch applied, but it seems we need a general approach to cover a few GPIO drivers with this kind of thing. Is this how we should always do it? 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/