From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
Cc: ore-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Subject: Re: [PATCH v3] arm: dts: sun7i-a20-bananapi: name the GPIO lines
Date: Wed, 10 May 2017 14:47:41 +0200 [thread overview]
Message-ID: <20170510124741.GI5465@flea.lan> (raw)
In-Reply-To: <17553199-cc74-96ae-bc75-5e91b866ccd1-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2478 bytes --]
On Wed, May 10, 2017 at 06:47:58AM +0200, Oleksij Rempel wrote:
> >> + "", "", "", "", "SCL", "SDA", "", "",
> >
> > I'm not sure how it's called in the schematics / documentation, but
> > having a way to get which bus it's from would be helpful (like you did
> > for the PMIC I2C bus).
>
> I use only names provided by schematics. Using something different IMO
> makes no sense and confusing.
Indeed.
> >> + "", "", "", "", "", "", "", "",
> >> + /* PC */
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + /* PD */
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + /* PE */
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + /* PF */
> >> + "SD0-D1", "SD0-D0", "SD0-CLK", "SD0-CMD", "SD0-D3",
> >> + "SD0-D2", "", "",
> >
> > Why did you change the wrapping and indentation on those two lines?
>
> i use 8 entry per line to keep counting easier. If line is too wide, i
> wrap it with changed indentation.
Ack.
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + /* PG */
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + "", "", "", "", "", "", "", "",
> >> + /* PH */
> >> + "TXD0", "RXD0", "IO-1", "PH3", "USB0-IDDET", "PH5", "", "",
> >
> > What are PH3 and PH5 used for on the board? Can't we provide a more
> > explicit name?
>
> Only names used by schematic :) If we will use something different users
> will hate us even more.
Those schematics suck then :)
> I can image to use some kind of combination of connector name and pin
> name. For example: "JP1-RXD0", or some thing like this.
There's no mark on the PCB either? RXD0 and the other are fine, the
only ones that concern me are PH3 and PH5, which are basically only
the SoC pin name, and nothing else.
I guess we don't really have the choice if the schematic uses that,
and there's nothing on the PCB..
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-05-10 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 5:30 [PATCH v3] arm: dts: sun7i-a20-bananapi: name the GPIO lines Oleksij Rempel
2017-05-07 7:41 ` Linus Walleij
[not found] ` <1494048638-24365-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2017-05-09 20:27 ` Maxime Ripard
2017-05-10 4:47 ` Oleksij Rempel
[not found] ` <17553199-cc74-96ae-bc75-5e91b866ccd1-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2017-05-10 12:47 ` Maxime Ripard [this message]
2017-05-10 14:27 ` Oleksij Rempel
2017-05-10 14:54 ` 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=20170510124741.GI5465@flea.lan \
--to=maxime.ripard-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=ore-bIcnvbaLZ9MEGnE8C9+IrQ@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).