Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754345Ab3I0TcQ (ORCPT ); Fri, 27 Sep 2013 15:32:16 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:34582 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753421Ab3I0TcK (ORCPT ); Fri, 27 Sep 2013 15:32:10 -0400 Message-ID: <5245DD23.6000508@ti.com> Date: Fri, 27 Sep 2013 15:31:47 -0400 From: Santosh Shilimkar User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Javier Martinez Canillas CC: Linus Walleij , Kevin Hilman , Stephen Warren , Lars Poeschel , Grant Likely , Mark Rutland , Ian Campbell , Kumar Gala , Pawel Moll , Tomasz Figa , Enric Balletbo i Serra , Jean-Christophe PLAGNIOL-VILLARD , Balaji T K , Tony Lindgren , Jon Hunter , , , , , , Subject: Re: [PATCH 1/2] gpio/omap: maintain GPIO and IRQ usage separately References: <1380069414-2922-1-git-send-email-javier.martinez@collabora.co.uk> In-Reply-To: <1380069414-2922-1-git-send-email-javier.martinez@collabora.co.uk> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 24 On Tuesday 24 September 2013 08:36 PM, Javier Martinez Canillas wrote: > The GPIO OMAP controller pins can be used as IRQ and GPIO > independently so is necessary to keep track GPIO pins and > IRQ lines usage separately to make sure that the bank will > always be enabled while being used. > > Also move gpio_is_input() definition in preparation for the > next patch that setups the controller's irq_chip driver when > a caller requests an interrupt line. > > Signed-off-by: Javier Martinez Canillas > --- Considering GPIO core maintainer is fine with this approach, am fine with both of your patches. Again thanks a lot for fixing the long nagging issue. FWIW, Acked-by: Santosh Shilimkar -- 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/