Linus Walleij <linus.walleij@xxxxxxxxxx> writes: > On Mon, May 18, 2020 at 10:18 AM Felipe Balbi <balbi@xxxxxxxxxx> wrote: >> Linus Walleij <linus.walleij@xxxxxxxxxx> 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#531_Expansion_Headers Pins are always the pin number on the header, hence P2_21 and P1_10 and so on. -- balbi
Attachment:
signature.asc
Description: PGP signature