Re: [PATCH] riscv: dts: nezha-d1: add gpio-line-names

From: Trevor Woerner
Date: Wed Feb 08 2023 - 11:57:53 EST


Hi Conor,

Thank you for your review!

On Wed 2023-02-08 @ 04:43:06 PM, Conor Dooley wrote:
> On Tue, Feb 07, 2023 at 08:45:03PM -0500, Trevor Woerner wrote:
> > Add descriptive names so users can associate specific lines with their
> > respective pins on the 40-pin header according to the schematics found at:
> >
> > http://dl.linux-sunxi.org/D1/D1_Nezha_development_board_schematic_diagram_20210224.pdf
>
> Dunno about the sunxi folk, but ideally that'd be a Link: tag IMO.

Okay, np.

> >
> > Signed-off-by: Trevor Woerner <twoerner@xxxxxxxxx>
> > ---
> > .../boot/dts/allwinner/sun20i-d1-nezha.dts | 53 +++++++++++++++++++
> > 1 file changed, 53 insertions(+)
> >
> > diff --git a/arch/riscv/boot/dts/allwinner/sun20i-d1-nezha.dts b/arch/riscv/boot/dts/allwinner/sun20i-d1-nezha.dts
> > index a0769185be97..33489c7619cb 100644
> > --- a/arch/riscv/boot/dts/allwinner/sun20i-d1-nezha.dts
> > +++ b/arch/riscv/boot/dts/allwinner/sun20i-d1-nezha.dts
> > @@ -90,6 +90,15 @@ pcf8574a: gpio@38 {
> > gpio-controller;
> > #gpio-cells = <2>;
> > #interrupt-cells = <2>;
> > + gpio-line-names =
> > + "pin13 [PP0,gpio8] ",
> > + "pin16 [PP1,gpio10]",
> > + "pin18 [PP2,gpio11]",
> > + "pin26 [PP3,gpio17]",
> > + "pin22 [PP4,gpio14]",
> > + "pin28 [PP5,gpio19]",
> > + "pin37 [PP6,gpio23]",
> > + "pin11 [PP7,gpio6] ";
>
> dtbs_check does not like this:
> arch/riscv/boot/dts/allwinner/sun20i-d1-nezha.dtb: gpio@38: 'gpio-line-names' does not match any of the regexes: '^(.+-hog(-[0-9]+)?)$', 'pinctrl-[0-9]+'
> From schema: Documentation/devicetree/bindings/gpio/nxp,pcf8575.yaml
>
> > };
> > };

Okay, I'll look for other examples of giving names to io-expanders to see
what's needed to keep dtc happy.

> >
> > @@ -164,3 +173,47 @@ &usbphy {
> > usb1_vbus-supply = <&reg_vcc>;
> > status = "okay";
> > };
> > +
> > +&pio {
> > + gpio-line-names =
> > + /* Port A */
> > + "", "", "", "", "", "", "", "",
> > + "", "", "", "", "", "", "", "",
> > + "", "", "", "", "", "", "", "",
> > + "", "", "", "", "", "", "", "",
> > + /* Port B */
> > + "pin5 [PB0, gpio2/twi2-sck]",
> > + "pin3 [PB1, gpio1/twi2-sda]",
> > + "",
> > + "pin38 [PB3, gpio24/i2s2-din]",
> > + "pin40 [PB4, gpio25/i2s2-dout]",
> > + "pin12 [PB5, gpio7/i2s-clk]",
> > + "pin35 [PB6, gpio22/i2s2-lrck]",
> > + "",
> > + "pin8 [PB8, gpio4/uart0-txd]",
> > + "pin10 [PB9, gpio5/uart0-rxd]",
> > + "",
> > + "",
> > + "pin15 [PB12,gpio9]",
>
> Why not pick a consistent styling w.r.t. the space between PB#, & gpio?

I thought it looked better when doing:

nezha-allwinner-d1:~# gpioinfo
gpiochip0 - 224 lines:
...
line 32: "pin5 [PB0, gpio2/twi2-sck]" kernel input active-high [used]
line 33: "pin3 [PB1, gpio1/twi2-sda]" kernel input active-high [used]
line 34: unnamed "interrupt" input active-high [used]
line 35: "pin38 [PB3, gpio24/i2s2-din]" unused input active-high
line 36: "pin40 [PB4, gpio25/i2s2-dout]" unused input active-high
line 37: "pin12 [PB5, gpio7/i2s-clk]" unused input active-high
line 38: "pin35 [PB6, gpio22/i2s2-lrck]" unused input active-high
line 39: unnamed unused input active-high
line 40: "pin8 [PB8, gpio4/uart0-txd]" kernel input active-high [used]
line 41: "pin10 [PB9, gpio5/uart0-rxd]" kernel input active-high [used]
...

I guess "better" is subjective :-)

I'll do a v2, thanks!