On Thu, Jun 29, 2017 at 9:37 PM, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote: > On 06/23/2017 07:33 AM, Linus Walleij wrote: >> >> I think using "lsgpio" fron tools/gpio/lsgpio.c is better to inspect >> the available GPIOs. >> >> If you haven't tested the GPIO tools, please try it out. > > > Unfortunately, this tool isn't very useful: > > $ sudo ./lsgpio > GPIO chip: gpiochip0, "QCOM8001:00", 150 GPIO lines > line 0: unnamed unused [output] > line 1: unnamed unused [output] > line 2: unnamed unused [output] They can be given reasonable names using the line-names property in the DTS file, preferably the top-level file. arch/arm/boot/dts/bcm2835-rpi-b-plus.dts is a good example. Do the same with your target board and things will be very much more helpful. gpio-hammer can help you test a line (try it with a LED) and gpio-event-mon can help you listen at a key for example. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html