On Fri, Jul 17, 2020 at 11:09:11PM +0300, Andy Shevchenko wrote:
> On Fri, Jul 17, 2020 at 10:50 PM Drew Fustini <drew@xxxxxxxxxxxxxxx> wrote:
> > On Fri, Jul 17, 2020 at 06:14:06PM +0300, Andy Shevchenko wrote:
> > > On Fri, Jul 17, 2020 at 4:36 AM Drew Fustini <drew@xxxxxxxxxxxxxxx> wrote:
>
> ...
>
> > > > 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.
>
> ...
>
> > I added the gpio column based on Tony's feedback [0].
> >
> > I'm not sure how I could do it genericly.
> >
> > The pin_dbg_show callback is implemented in pcs_pin_dbg_show() which
> > prints the contents of each line in the 'pins' file.
> >
> > Any advice on how I could implement a gpio column for 'pins' file
> > without chaning the pin_dbg_show in all the drivers?A
>
> My question was exactly about changing core, i.e. pinctrl_pins_show(),
> rather than each driver.
>
> --
> With Best Regards,
> Andy Shevchenko
Ah ok, so I see in pinctrl_pins_show() that it prints:
seq_printf(s, "pin %d (%s) ", pin, desc->name);
and then calls ops->pin_dbg_show() to have the driver finish printing
the line.
I will try to add the gpio number to the seq_printf() after desc->name.
thanks,
drew
