On Mon, Aug 17, 2015 at 9:29 AM, Alexandre Courbot <[email protected]> wrote: > On Mon, Aug 10, 2015 at 7:02 PM, Linus Walleij <[email protected]> > wrote: >> On Tue, Aug 4, 2015 at 11:23 AM, Markus Pargmann <[email protected]> wrote: >> >>> Add some information about gpio names to the debugfs gpio file. name and >>> label of a GPIO are then displayed next to each other. This way it is >>> easy to see what the real name of GPIO is and what the driver requested >>> it for. >>> >>> Signed-off-by: Markus Pargmann <[email protected]> >> >> This patch looks correct in the context. > > Looks correct indeed, but on a related note one might question the > need to have both a "name" and a "label" for a GPIO?
The way I see it a certain GPIO controller has names for the GPIO lines, like gpio0,1,2...n, while the label is for the actual use of the GPIO line. It's a bit like the regulator name, rail name and consumer endpoints guess. Just we only have two names, not three :P Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
