[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75Vec23BDJt3woKL+SiY0dxPLFADdGaf=RbDuOWCHwtj_iA@mail.gmail.com>
Date: Tue, 21 Jul 2020 09:49:07 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Drew Fustini <drew@...gleboard.org>
Cc: Tony Lindgren <tony@...mide.com>,
Linus Walleij <linus.walleij@...aro.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jason Kridner <jkridner@...gleboard.org>,
Robert Nelson <robertcnelson@...il.com>
Subject: Re: [PATCH v2] pinctrl: core: print gpio in pins debugfs file
On Mon, Jul 20, 2020 at 10:18 PM Drew Fustini <drew@...gleboard.org> 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/pins
>
> pin 100 (PIN100) gpiochip:gpio-96-127 line-name:P1.36 [PWM0A] 44e10990 00000001 pinctrl-single
> pin 101 (PIN101) gpiochip:gpio-96-127 line-name:P1.33 [PRU0.1] 44e10994 00000027 pinctrl-single
> pin 102 (PIN102) gpiochip:gpio-96-127 line-name:P2.32 [PRU0.2] 44e10998 00000027 pinctrl-single
It becomes unnecessarily long. I would drop these 'gpiochip:' and
'line-name:' prefixes and NA case you rather should have the same
amount of arguments, so here would be something like NA NA or alike.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists