Netdev List
 help / color / mirror / Atom feed
From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Andrew Lunn'" <andrew@lunn.ch>
Cc: <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<chris.packham@alliedtelesis.co.nz>, <daniel@makrotopia.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>
Subject: AW: [PATCH net-next v5 2/8] net: mdio: realtek-rtl9300: Add polling documentation
Date: Thu, 23 Jul 2026 21:43:02 +0200	[thread overview]
Message-ID: <005601dd1adb$7d1cc3a0$77564ae0$@gmx.de> (raw)
In-Reply-To: <420dbb03-6a39-4ef3-9cb3-da78401fd4ce@lunn.ch>

> Von: Andrew Lunn <andrew@lunn.ch> 
> Gesendet: Donnerstag, 23. Juli 2026 16:18
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Betreff: Re: [PATCH net-next v5 2/8] net: mdio: realtek-rtl9300: Add
polling documentation
> ..
> Just to be sure. You have a broken cable, so could trigger downshift?

I usually tape pin 8 for these kind of tests.
RTL838x switch side gives (port 8 aka LAN1):

MAC link status:
root@OpenWrt:~# devmem 0x1b00a190
0x00010000

So Port 8 = 100 Mbit
see https://svanheule.net/realtek/maple/register/mac_link_spd_sts

MAC force mode for port 8:
root@OpenWrt:~# devmem 0x1b00a124
0x00D71EEC

So port 8: NWAY_EN=1 SPD_SEL=3 (aka 1000Mbit)
See https://svanheule.net/realtek/maple/register/mac_force_mode_ctrl

PHY view
root@OpenWrt:~# ethtool lan1
Settings for lan1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 8
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Link detected: yes

Nanopi R5S on other side gives:

root@nanopi:~# ethtool eth2
Settings for eth2:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Link detected: yes


  reply	other threads:[~2026-07-23 19:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  6:23 [PATCH net-next v5 0/8] net: mdio: realtek-rtl9300: Add RTL83xx support Markus Stockhausen
2026-07-22  6:23 ` [PATCH net-next v5 1/8] dt-bindings: net: realtek,rtl9301-mdio: Add RTL83xx series Markus Stockhausen
2026-07-22  6:23 ` [PATCH net-next v5 2/8] net: mdio: realtek-rtl9300: Add polling documentation Markus Stockhausen
2026-07-22 19:09   ` Andrew Lunn
2026-07-23  6:23     ` AW: " Markus Stockhausen
2026-07-23 14:18       ` Andrew Lunn
2026-07-23 19:43         ` Markus Stockhausen [this message]
2026-07-22  6:23 ` [PATCH net-next v5 3/8] net: phy: add (*notify_phy_attach/detach)() hooks to struct mii_bus Markus Stockhausen
2026-07-22 18:43   ` Andrew Lunn
2026-07-22  6:23 ` [PATCH net-next v5 4/8] net: mdio: realtek-rtl9300: Configure hardware polling during probing Markus Stockhausen
2026-07-22 18:50   ` Andrew Lunn
2026-07-22  6:23 ` [PATCH net-next v5 5/8] net: mdio: realtek-rtl9300: Add page tracking Markus Stockhausen
2026-07-22 18:55   ` Andrew Lunn
2026-07-22  6:23 ` [PATCH net-next v5 6/8] net: mdio: realtek-rtl9300: Increase MDIO timeout Markus Stockhausen
2026-07-22 18:55   ` Andrew Lunn
2026-07-22  6:23 ` [PATCH net-next v5 7/8] net: mdio: realtek-rtl9300: Add support for RTL838x Markus Stockhausen
2026-07-22  6:23 ` [PATCH net-next v5 8/8] net: mdio: realtek-rtl9300: Add support for RTL839x Markus Stockhausen

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='005601dd1adb$7d1cc3a0$77564ae0$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=andrew@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.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