From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH v2] pinctrl: generic: Add output-enable property Date: Thu, 29 Jun 2017 14:33:17 +0200 Message-ID: References: <1498125658-14554-1-git-send-email-jacopo+renesas@jmondi.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <1498125658-14554-1-git-send-email-jacopo+renesas@jmondi.org> Sender: linux-kernel-owner@vger.kernel.org To: Jacopo Mondi Cc: Andy Shevchenko , Dong Aisheng , Geert Uytterhoeven , Chris Brandt , Laurent Pinchart , Rob Herring , Mark Rutland , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , Linux-Renesas , "linux-kernel@vger.kernel.org" List-Id: linux-gpio@vger.kernel.org On Thu, Jun 22, 2017 at 12:00 PM, Jacopo Mondi wrote: > Add output-enable generic pin configuration property. > This properties allows enabling/disabling pin's output capabilities > without actually driving any value on the line. > > --- > v1->v2: > - Expand the property description as suggested by Laurent. I ended up > mentioning the in-famous output buffer :) I have applied the patch adding a few elaborations in the binding that the situation where you may use this is typically when enabling/disabling input or output buffers irrespective of the mode of the line as a whole. We might need even more documentation because this is really confusing. But for now it lets drivers work, which is nice. Rough consensus and running code should be our guide. Yours, Linus Walleij