On Fri, Jul 17, 2020 at 4:36 AM Drew Fustini <drew@xxxxxxxxxxxxxxx> wrote: > > If there is a gpio range mapping for the pin, then print out the gpio > number for the pin in the debugfs 'pins' file. > > Here is an example on the BeagleBone Black: > pin 0 (PIN0) 44e10800 00000027 pinctrl-single GPIO-32 > pin 1 (PIN1) 44e10804 00000027 pinctrl-single GPIO-33 > pin 2 (PIN2) 44e10808 00000027 pinctrl-single GPIO-34 > pin 3 (PIN3) 44e1080c 00000027 pinctrl-single GPIO-35 > pin 4 (PIN4) 44e10810 00000027 pinctrl-single GPIO-36 > pin 5 (PIN5) 44e10814 00000027 pinctrl-single GPIO-37 > pin 6 (PIN6) 44e10818 00000027 pinctrl-single GPIO-38 > pin 7 (PIN7) 44e1081c 00000027 pinctrl-single GPIO-39 > pin 8 (PIN8) 44e10820 00000027 pinctrl-single GPIO-22 > pin 9 (PIN9) 44e10824 00000030 pinctrl-single GPIO-23 Wouldn't it be better to have this for all types of pin controllers? But I'm not sure about the format of output. -- With Best Regards, Andy Shevchenko
