Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751535AbaLBO3t (ORCPT ); Tue, 2 Dec 2014 09:29:49 -0500 Received: from mail-ig0-f177.google.com ([209.85.213.177]:36942 "EHLO mail-ig0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751491AbaLBO3r (ORCPT ); Tue, 2 Dec 2014 09:29:47 -0500 MIME-Version: 1.0 In-Reply-To: References: <1416527684-19017-1-git-send-email-bparrot@ti.com> <1416527684-19017-2-git-send-email-bparrot@ti.com> <20141201163639.GI25249@lukather> Date: Tue, 2 Dec 2014 15:29:46 +0100 Message-ID: Subject: Re: [Patch v2 1/2] gpio: add GPIO hogging mechanism From: Linus Walleij To: Alexandre Courbot Cc: Maxime Ripard , Benoit Parrot , Pantelis Antoniou , Jiri Prchal , "linux-gpio@vger.kernel.org" , Linux Kernel Mailing List , "devicetree@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 On Tue, Dec 2, 2014 at 3:13 PM, Alexandre Courbot wrote: > On Tue, Dec 2, 2014 at 1:36 AM, Maxime Ripard > wrote: >> The only thing I'd like to have would be that the request here would >> be non-exclusive, so that a later driver would still be allowed later >> on to request that GPIO later on and manage it itself (ideally using >> the usual gpiod_request function). > > Actually we have a plan (and I have some code too) to allow multiple > consumers per GPIO. Although like Benoit I wonder why you would want > to hog a GPIO and then request it properly later. Also, that probably > means we should abandon the hog since it actively drives the line and > would interfere with the late requested. How to do that correctly is > not really clear to me. I don't get the usecase. A hogged GPIO is per definition hogged. This sounds more like "initial settings" or something, which is another usecase altogether. 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/