Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Felipe Balbi <balbi@kernel.org>
To:     Linus Walleij <linus.walleij@linaro.org>
Cc:     Drew Fustini <drew@beagleboard.org>,
        Grygorii Strashko <grygorii.strashko@ti.com>,
        =?utf-8?Q?Beno=C3=AEt?= Cousson <bcousson@baylibre.com>,
        Tony Lindgren <tony@atomide.com>,
        Rob Herring <robh+dt@kernel.org>,
        Linux-OMAP <linux-omap@vger.kernel.org>,
        "open list\:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@vger.kernel.org>,
        "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Jason Kridner <jkridner@beagleboard.org>,
        Robert Nelson <robertcnelson@beagleboard.org>
Subject: Re: [PATCH] arm: dts: am33xx-bone-common: add gpio-line-names
In-Reply-To: <CACRpkdZnnRXwv0-71t93HX42jL-muty4yJx5gW6_P3yOM-sGAg@mail.gmail.com>
References: <20200508165821.GA14555@x1> <CACRpkdb+ZP6rfjGg6Ef9_wYvNf6qmSc7LZyYBVKA3XWCtxPfqQ@mail.gmail.com> <875zcty7tt.fsf@kernel.org> <CACRpkdZnnRXwv0-71t93HX42jL-muty4yJx5gW6_P3yOM-sGAg@mail.gmail.com>
Date:   Mon, 18 May 2020 15:34:23 +0300
Message-ID: <87zha5whf4.fsf@kernel.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
        micalg=pgp-sha256; protocol="application/pgp-signature"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Linus Walleij <linus.walleij@linaro.org> writes:

> On Mon, May 18, 2020 at 10:18 AM Felipe Balbi <balbi@kernel.org> wrote:
>> Linus Walleij <linus.walleij@linaro.org> writes:
>> >> gpiochip0 - 32 lines:
>> >>         line   0:   "ethernet"       unused   input  active-high
>> >>         line   1:   "ethernet"       unused   input  active-high
>> >
>> > Why are the ethernet lines not tagged with respective signal name
>> > when right below the SPI lines are explicitly tagged with
>> > sclk, cs0 etc?
>> >
>> > Ethernet is usually RGMII and has signal names like
>> > tx_clk, tx_d0, tx_en etc.
>> >
>> > Also some lines seem to be tagged with the pin number
>> > like P9_22, P2_21 below, it seems a bit inconsistent
>> > to have much information on some pins and very sketchy
>> > information on some.
>>
>> the pin names match the beagle bone documentation and would help users
>> figure out which pins on the expansion headers match to a gpio signal.
>
> OK if it is how it looks in the documentation I agree that is what
> users need, maybe the documentation is confusing but there is not
> much to do about that.

the board has two expansion headers, P1 and P2:

https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual#53=
1_Expansion_Headers

Pins are always the pin number on the header, hence P2_21 and P1_10 and
so on.

=2D-=20
balbi

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEElLzh7wn96CXwjh2IzL64meEamQYFAl7CgM8ACgkQzL64meEa
mQa02A//W7ZWqA6ND2rDES1cxSEAwXyx02mdXu96eVdXV+2Q9FXd/OJvXrWSZDGa
xf0Yu7ve9EMUVbzq5kwINzMBL6nN7F2rtEtyfZkAcTFFSnedjHeWJqpqB1aKfZHs
/e+iy8NIcdVmCR9SAbW2Lfm0729cCBK/jSKLqnOeZIEzDn7Cg3VPtzzGNKUWqz2R
oiUq5GceYpHhOlQ+EuTDv1e5i/lr/UvQ08XWU08Mw7xQxTkdAUThM5Z0w3oi3BPo
zZ3rG7teke3+yUflzUX1fh9Uoa3aJeq2msafROF45kSeYTl7GBwXDB528sLtWAai
YX/f+z7LgdGd/vVNgRd+m/qv0qfnaCvDf/bJqqyI1JKRL+aYmv3j/T72ebgAw7EV
LpQfP6/mA7vVvVEJ78rJMgn5nkexXvs7vV34nAZ45H+Zyp+rHUfhYFVw8MEGOBZb
M4xzKfE40amu05zPkRMkVddTfjsBDpFD7biZu9aJREzi564Hnt8CQ/SUqq2fOVRw
5OQsIsSi8paC797xILnFHaM1PK/NaNqp8qKsF/dv98k1sELP1SAi9k+oJJ4KhWJ8
zdxnU9+1mbjd5AgrLac153LyaPX8z/W3TrjvvPpA9bHok2+vizWuVRDQl1dgcj16
n5OuWeutgO3DIi+iBhJtVtV1RUK7ywUHoYuZ3NM23VfFYA8bVAI=
=8tVN
-----END PGP SIGNATURE-----
--=-=-=--