From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> To: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> Cc: Oleksij Rempel <fixed-term.Oleksij.Rempel-V5te9oGctAVWk0Htik3J/w@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org> Subject: Re: [PATCH] arm: dts: sun7i-a20-bananapi: name the GPIO lines Date: Fri, 22 Jul 2016 16:55:45 +0200 [thread overview] Message-ID: <CACRpkdZLG1Ffdiw3xkP4G0XBr=WDXg2Vbh2Xmgno1PTNhfZHfg@mail.gmail.com> (raw) In-Reply-To: <1468496825-4896-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> On Thu, Jul 14, 2016 at 1:47 PM, Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> wrote: > This names the GPIO lines on the Banana Pi board in accordance with > the A20_Banana_Pi v1.4 Specification. > > This will make these line names reflect through to userspace > so that they can easily be identified and used with the new > character device ABI. > > Some care has been taken to name all lines, not just those used > by the external connectors, also lines that are muxed into some > other function than GPIO: these are named "[FOO]" so that users > can see with lsgpio what all lines are used for. > > Ps: most of the text was taken from Linux Wallej patch. LinuS > > Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > Cc: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> > Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org > Cc: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org> > Signed-off-by: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> Nice usecase! > + /* > + * Legend: proper name = the GPIO line is used as GPIO > + * NC = not connected (not routed from the SoC) > + * "[PER]" = pin is muxed for peripheral (not GPIO) > + * "" = no idea, schematic doesn't say, could be > + * unrouted (not connected to any external pin) > + * LSEC = Low Speed External Connector > + * HSEC = High Speed External Connector > + */ So maybe we should make this naming convention a suggested standard. People seem to like it. > + gpio-line-names = > + /* PA */ > + "[ERXD3]", "[ERXD2]", "[ERXD1]", "[ERXD0]", "[ETXD3]", > + "[ETXD2]", "[ETXD1]", "[ETXD0]", > + "[ERXCK]", "[ERXERR]", "[ERXDV]", "[EMDC]", "[EMDIO]", > + "[ETXEN]", "[ETXCK]", "[ECRS]", > + "[ECOL]", "[ETXERR]", "", "", "", "", "", "", > + "", "", "", "", "", "", "", "", > + /* PB */ > + "[PMU-SCK]", "[PMU-SDA]", "", "", "", "NC", "NC", "NC", > + "NC", "[USB0-DRV]", "NC", "NC", "NC", "NC", "", "", > + "", "", "", "", "SCL", "SDA", "", "", Are these bit-banged SCL and SDA for doing I2C with GPIO? Otherwise you probably want to name them "[SCL]" and "[SDA]" > + "TXD0", "RXD0", "IO-1", "PH3", "[USB0-IDDET]", "PH5", "", "", Same here. You probably want "[TXD0]" etc unless you're bit-banging the serial port. "IO-1" sounds like a real GPIO though and should probably be named like that without [] and "PH3" what is that really? A device-muxed pin or some kind of GPIO? > + "", "", "[SD0-DET]", "", "", "", "", "", > + "NC", "", "", "", "IO-4", "IO-5", "NC", "[EMAC-PWR-EN]", So these seem correct too. > + "[LED1]", "NC", "NC", "NC", "", "", "", "", "LED1" seems like the right name, if this is a GPIO used to drive a LED. > + "", "", "", "IO-GCLK", "NC", "NC", "NC", "NC", WHat is IO-GCLK? A real GPIO line used for toggling a clock? Or a hardware clock signal? In the first case it it correctly named, in the other case it should be "[IO-GCLK]". > + "NC", "NC", "[SPI-CE0]", "[SPI-CLK]", "[SPI-MOSI]", > + "[SPI-MISO]", "[SPI-CE1]", "NC", > + "IO-6", "IO-3", "IO-2", "IO-0", "", "", "", "", Looks right. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] arm: dts: sun7i-a20-bananapi: name the GPIO lines Date: Fri, 22 Jul 2016 16:55:45 +0200 [thread overview] Message-ID: <CACRpkdZLG1Ffdiw3xkP4G0XBr=WDXg2Vbh2Xmgno1PTNhfZHfg@mail.gmail.com> (raw) In-Reply-To: <1468496825-4896-1-git-send-email-linux@rempel-privat.de> On Thu, Jul 14, 2016 at 1:47 PM, Oleksij Rempel <linux@rempel-privat.de> wrote: > This names the GPIO lines on the Banana Pi board in accordance with > the A20_Banana_Pi v1.4 Specification. > > This will make these line names reflect through to userspace > so that they can easily be identified and used with the new > character device ABI. > > Some care has been taken to name all lines, not just those used > by the external connectors, also lines that are muxed into some > other function than GPIO: these are named "[FOO]" so that users > can see with lsgpio what all lines are used for. > > Ps: most of the text was taken from Linux Wallej patch. LinuS > > Cc: devicetree at vger.kernel.org > Cc: Linus Walleij <linus.walleij@linaro.org> > Cc: linux-arm-kernel at lists.infradead.org > Cc: Chen-Yu Tsai <wens@csie.org> > Signed-off-by: Oleksij Rempel <linux@rempel-privat.de> Nice usecase! > + /* > + * Legend: proper name = the GPIO line is used as GPIO > + * NC = not connected (not routed from the SoC) > + * "[PER]" = pin is muxed for peripheral (not GPIO) > + * "" = no idea, schematic doesn't say, could be > + * unrouted (not connected to any external pin) > + * LSEC = Low Speed External Connector > + * HSEC = High Speed External Connector > + */ So maybe we should make this naming convention a suggested standard. People seem to like it. > + gpio-line-names = > + /* PA */ > + "[ERXD3]", "[ERXD2]", "[ERXD1]", "[ERXD0]", "[ETXD3]", > + "[ETXD2]", "[ETXD1]", "[ETXD0]", > + "[ERXCK]", "[ERXERR]", "[ERXDV]", "[EMDC]", "[EMDIO]", > + "[ETXEN]", "[ETXCK]", "[ECRS]", > + "[ECOL]", "[ETXERR]", "", "", "", "", "", "", > + "", "", "", "", "", "", "", "", > + /* PB */ > + "[PMU-SCK]", "[PMU-SDA]", "", "", "", "NC", "NC", "NC", > + "NC", "[USB0-DRV]", "NC", "NC", "NC", "NC", "", "", > + "", "", "", "", "SCL", "SDA", "", "", Are these bit-banged SCL and SDA for doing I2C with GPIO? Otherwise you probably want to name them "[SCL]" and "[SDA]" > + "TXD0", "RXD0", "IO-1", "PH3", "[USB0-IDDET]", "PH5", "", "", Same here. You probably want "[TXD0]" etc unless you're bit-banging the serial port. "IO-1" sounds like a real GPIO though and should probably be named like that without [] and "PH3" what is that really? A device-muxed pin or some kind of GPIO? > + "", "", "[SD0-DET]", "", "", "", "", "", > + "NC", "", "", "", "IO-4", "IO-5", "NC", "[EMAC-PWR-EN]", So these seem correct too. > + "[LED1]", "NC", "NC", "NC", "", "", "", "", "LED1" seems like the right name, if this is a GPIO used to drive a LED. > + "", "", "", "IO-GCLK", "NC", "NC", "NC", "NC", WHat is IO-GCLK? A real GPIO line used for toggling a clock? Or a hardware clock signal? In the first case it it correctly named, in the other case it should be "[IO-GCLK]". > + "NC", "NC", "[SPI-CE0]", "[SPI-CLK]", "[SPI-MOSI]", > + "[SPI-MISO]", "[SPI-CE1]", "NC", > + "IO-6", "IO-3", "IO-2", "IO-0", "", "", "", "", Looks right. Yours, Linus Walleij
next prev parent reply other threads:[~2016-07-22 14:55 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-14 11:47 [PATCH] arm: dts: sun7i-a20-bananapi: name the GPIO lines Oleksij Rempel 2016-07-14 11:47 ` Oleksij Rempel [not found] ` <1468496825-4896-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> 2016-07-22 14:55 ` Linus Walleij [this message] 2016-07-22 14:55 ` Linus Walleij [not found] ` <CACRpkdZLG1Ffdiw3xkP4G0XBr=WDXg2Vbh2Xmgno1PTNhfZHfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-07-22 15:47 ` Chen-Yu Tsai 2016-07-22 15:47 ` Chen-Yu Tsai 2016-07-25 5:27 ` fixed-term.Oleksij.Rempel 2016-07-25 5:27 ` fixed-term.Oleksij.Rempel [not found] ` <5795A334.3000701-V5te9oGctAVWk0Htik3J/w@public.gmane.org> 2016-07-25 13:27 ` Linus Walleij 2016-07-25 13:27 ` Linus Walleij [not found] ` <CACRpkdYnK=7C=F5hZUo-nYv6Z+Pb+eT7vm1e4hL8N-QgJnuLfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-08-05 8:05 ` Oleksij Rempel 2016-08-05 8:05 ` Oleksij Rempel 2016-08-05 8:06 ` [PATCH v2] " Oleksij Rempel 2016-08-05 8:06 ` Oleksij Rempel [not found] ` <1470384404-6796-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> 2016-08-08 17:51 ` Linus Walleij 2016-08-08 17:51 ` Linus Walleij 2017-04-28 5:11 ` Oleksij Rempel 2017-04-28 5:11 ` Oleksij Rempel 2017-04-28 8:45 ` Linus Walleij 2017-04-28 8:45 ` Linus Walleij 2017-04-28 9:03 ` Oleksij Rempel 2017-04-28 9:03 ` Oleksij Rempel 2017-05-03 7:09 ` [PATCH v2 resend] " Oleksij Rempel 2017-05-03 7:09 ` Oleksij Rempel [not found] ` <1493795360-18629-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org> 2017-05-04 14:56 ` Maxime Ripard 2017-05-04 14:56 ` Maxime Ripard
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACRpkdZLG1Ffdiw3xkP4G0XBr=WDXg2Vbh2Xmgno1PTNhfZHfg@mail.gmail.com' \ --to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=fixed-term.Oleksij.Rempel-V5te9oGctAVWk0Htik3J/w@public.gmane.org \ --cc=linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=wens-jdAy2FN1RRM@public.gmane.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.