summaryrefslogtreecommitdiffstats
path: root/drivers/net/phy/mdio-mux-bcm-iproc.c
diff options
context:
space:
mode:
authorSerge Semin2019-05-08 23:51:15 +0200
committerDavid S. Miller2019-05-09 01:31:38 +0200
commitf81dadbcf7fd067baf184b63c179fc392bdb226e (patch)
tree7dee9a087f071742dff67dbd981e7864747b4845 /drivers/net/phy/mdio-mux-bcm-iproc.c
parentnet: dsa: sja1105: Don't return a negative in u8 sja1105_stp_state_get (diff)
downloadkernel-qcow2-linux-f81dadbcf7fd067baf184b63c179fc392bdb226e.tar.gz
kernel-qcow2-linux-f81dadbcf7fd067baf184b63c179fc392bdb226e.tar.xz
kernel-qcow2-linux-f81dadbcf7fd067baf184b63c179fc392bdb226e.zip
net: phy: realtek: Add rtl8211e rx/tx delays config
There are two chip pins named TXDLY and RXDLY which actually adds the 2ns delays to TXC and RXC for TXD/RXD latching. Alas this is the only documented info regarding the RGMII timing control configurations the PHY provides. It turns out the same settings can be setup via MDIO registers hidden in the extension pages layout. Particularly the extension page 0xa4 provides a register 0x1c, which bits 1 and 2 control the described delays. They are used to implement the "rgmii-{id,rxid,txid}" phy-mode. The hidden RGMII configs register utilization was found in the rtl8211e U-boot driver: https://elixir.bootlin.com/u-boot/v2019.01/source/drivers/net/phy/realtek.c#L99 There is also a freebsd-folks discussion regarding this register: https://reviews.freebsd.org/D13591 It confirms that the register bits field must control the so called configuration pins described in the table 12-13 of the official PHY datasheet: 8:6 = PHY Address 5:4 = Auto-Negotiation 3 = Interface Mode Select 2 = RX Delay 1 = TX Delay 0 = SELRGV Reviewed-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Serge Semin <fancer.lancer@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy/mdio-mux-bcm-iproc.c')
0 files changed, 0 insertions, 0 deletions