jqz

Wow thanks! I'm guessing the column with gpiod is all I need, assuming the numbers in that column corresponds to chipnum : line number . I'd also tinker with diozero and see if I could figure out how to use it. Thanks again.

so I managed to add some names to the device tree, but I'm not quite sure if it's correct? There are 32 lines in gpiochip5 and I'm not sure if GP5B0 is actually at line0. Surely, If I was able to do something like this, this should be easily done by the experts. I added this to .dts file &gpio5 { gpio-line-names = "GP5B0", "GP5B1", "GP5B2", "GP5B3", "GP5B4", "GP5B5", "GP5B6", "GP5B7", "GP5C0", "", /* GPIO5C1 */ "", /* GPIO5C2 */ "GPIO5C3"; }; This is on a slackwarearm kernel 5.10. and the result is this:

Hi, Does anyone uses libgpiod library on TBoard-s? The command gpioinfo displays the gpiochips and lines that the library can access and there's a lot of them. In reality there's only a few gpio lines on each gpiochips that are usable if their respective alternate functions are not already set in the devicetree. It would be super nice if those usable lines are labeled that correspond to that fancy colour coded pinout in the board. But for now I would like to know which of the lines I could actually use as gpios. Any pointer or directions where to look for more help would be greatly appreciated.