* Drew Fustini <drew@xxxxxxxxxxxxxxx> [200713 17:47]: > Do you mean you would like to see the mapping added as a column in the pins file? > > debian@beaglebone:~$ sudo cat /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins |head > registered pins: 142 > pin 0 (PIN0) 44e10800 00000027 pinctrl-single > pin 1 (PIN1) 44e10804 00000027 pinctrl-single > pin 2 (PIN2) 44e10808 00000027 pinctrl-single > pin 3 (PIN3) 44e1080c 00000027 pinctrl-single > pin 4 (PIN4) 44e10810 00000027 pinctrl-single > pin 5 (PIN5) 44e10814 00000027 pinctrl-single > pin 6 (PIN6) 44e10818 00000027 pinctrl-single > pin 7 (PIN7) 44e1081c 00000027 pinctrl-single > pin 8 (PIN8) 44e10820 00000027 pinctrl-single > > So that could be: > > debian@beaglebone:~$ sudo cat /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins |head > registered pins: 142 > 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 Yes that would make the debugfs output more understandable and easier to use. > Should I try to add that in pcs_pin_dbg_show()? > > It currently prints: > > seq_printf(s, "%zx %08x %s ", pa, val, DRIVER_NAME); > > so I could change that to include the GPIO number if mapping exists. Sounds good to me yeah :) However, the issue of relying on debugfs for this still remains unsolved. But seems that probably should be done with the existing GPIO related API instead and a different issue from the pinctrl changes. Regards, Tony
