Re: [PATCH v2] pinctrl: core: print gpio in pins debugfs file

2020-07-20 Thread Andy Shevchenko
On Mon, Jul 20, 2020 at 10:18 PM Drew Fustini 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 output on the BeagleBone Black from: > /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pin

[PATCH v2] pinctrl: core: print gpio in pins debugfs file

2020-07-20 Thread Drew Fustini
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 output on the BeagleBone Black from: /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins pin 100 (PIN100) gpiochip:gpio-96-127 line-name:P1.36 [PWM0A]

Re: [PATCH v2] pinctrl: core: print gpio in pins debugfs file

2020-07-19 Thread Drew Fustini
On Sun, Jul 19, 2020 at 03:22:01PM +0200, Drew Fustini 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 output on the BeagleBone Black from: > /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-sin

[PATCH v2] pinctrl: core: print gpio in pins debugfs file

2020-07-19 Thread Drew Fustini
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 output on the BeagleBone Black from: /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins pin 103 (PIN103) GPIO-113 44e1099c 0027 pinctrl-single pin