On Mon, Dec 9, 2013 at 11:34 AM, boris brezillon <b.brezillon@xxxxxxxxxxx> wrote: > [Me] >> This has been suggested under the name "GPIO hogs" in the past. >> >> It would work similar to how pinctrl hogs work by associating the >> GPIO line the controller itself, using some specific string >> like gpio-input-hogs = <...> / gpio-output-hogs = <...>; >> >> The gpiolib core will then grab and set up these before >> returning from the registration call so noone ever gets a chance >> to use them. > > One more question, and I'm done :). > > In which case should we use output-high or output-low config > instead of gpio-output-hogs ? This is specified in Documentation/pinctrl.txt under the heading "GPIO mode pitfalls". Basically: the generic pinconfig output-high/output-low are for the case where this is a valid state for a Linux device driver driving a piece of hardware, like an IP-block, which is making use of these pins and during that usecase passes through states the data sheet may call "GPIO mode", but which are actually a way which the *device* uses the pins, not independent GPIO lines, like, just some 1-bit line. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
