Netdev List
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Liu Changjie <liucj1228@outlook.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org
Cc: Russell King <linux@armlinux.org.uk>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Luo Jie <jie.luo@oss.qualcomm.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: phy: Add Maxio MAE0621A support
Date: Mon, 3 Aug 2026 15:31:56 +0200	[thread overview]
Message-ID: <2635661d-4be2-4abf-84aa-c3024941f787@arm.com> (raw)
In-Reply-To: <MN0PR19MB609154F210DF84DCB29D3696ACC62@MN0PR19MB6091.namprd19.prod.outlook.com>

Hi,

thanks for sending this, one question and an update below ...

On 7/17/26 05:39, Liu Changjie wrote:
> Add a binding and PHY driver for the Maxio MAE0621A Gigabit Ethernet
> PHY. The driver matches the exact PHY ID and optionally selects a
> 125 MHz clock on CLKOUT. When the property is absent, the driver
> preserves the hardware strap or bootloader setting.
> 
> This was tested on the LCKFB Taishan Pi 3M. With the PHY's default
> CLKOUT configuration, the RK3576 GMAC negotiated a 1 Gbit/s link but
> the data path did not work. A read-modify-write of page 0xa43,
> register 0x19, setting bits 0 and 11 produced a readback value of
> 0x0823 and restored the data path without changing the RGMII delays.
> The readback also confirmed that the unrelated set bits were
> preserved.
> 
> Only the 125 MHz setting has been exercised on hardware and only that
> value is exposed by this series. The 0 and 25 MHz choices from the
> initial draft have been removed.

So what is this clock for, exactly? Is that the RXC clock, supposed to 
depend on the line speed? Then it would need to change if a 100MBit/s 
link is negotiated?
Or is this something else entirely, and merely used as an optional 
auxiliary clock, to support a switch or other network chips?

If I read the schematic of that Taishan board correctly, it's the 
former? But it's odd that both on the Radxa Cubie A5E (sporting the same 
-Q3C variant) and the X96QPro+ box (-Q2C) don't need any extra setting, 
and the clock there looks like the normal PHY controlled RXC clock.

> Public documentation for the MAE0621A register is not available. The

There seems to be now a datasheet, explaining all the non-standard 
registers, including the one for the 125MHz clock out register:

https://www.lcsc.com/datasheet/C49308069.pdf

If the link doesn't work (in the future), just find the PHY in the LCSC 
catalogue, it should have a link to the datasheet there.

Cheers,
Andre

> exact definitions of page 0xa43, register 0x19 bits 0 and 11, their
> reset defaults, and whether a soft reset is required after changing
> them still need confirmation from Maxio. The register programming in
> this series is therefore supported by the hardware A/B result, not by
> a public datasheet citation.
> 
> Hardware tests with the 125 MHz setting:
> - all supported 10/100/1000 Mbit/s link modes
> - 100 ICMP packets in each direction with no loss
> - 936/934 Mbit/s host-to-board iperf3, no retransmits
> - 943/941 Mbit/s board-to-host iperf3, no retransmits
> - link unplug/replug and a normal reboot, followed by another 100 ICMP
>    packets in each direction with no loss
> - no RX errors, missed packets, carrier errors or collisions
> 
> Static tests on net-next commit f6f3b36c15ed:
> - dt_binding_check with dtschema 2026.6
> - W=1 arm64 defconfig build of drivers/net/phy/maxio.o with GCC 10.3
> - W=1 arm64 allmodconfig build of drivers/net/phy/maxio.o with GCC 10.3
> - git diff --check and checkpatch.pl
> 
> Changes in v2:
> - Extend hardware validation to all supported 10/100/1000 Mbit/s link
>    modes.
> - Keep the binding limited to the tested 125 MHz setting. CLKOUT-disable
>    support can be added later after its register behavior is documented
>    and tested.
> - No binding or driver code changes.
> 
> Link: https://lore.kernel.org/r/MN0PR19MB6091CD5A84D2DA5DACF434DAACF92@MN0PR19MB6091.namprd19.prod.outlook.com [v1]
> 
> Liu Changjie (2):
>    dt-bindings: net: Add Maxio MAE0621A PHY
>    net: phy: Add support for the Maxio MAE0621A
> 
>   .../bindings/net/maxio,mae0621a.yaml          |  38 +++++++
>   .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
>   drivers/net/phy/Kconfig                       |   8 ++
>   drivers/net/phy/Makefile                      |   1 +
>   drivers/net/phy/maxio.c                       | 103 ++++++++++++++++++
>   5 files changed, 152 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/net/maxio,mae0621a.yaml
>   create mode 100644 drivers/net/phy/maxio.c
> 
> 
> base-commit: f6f3b36c15ed44de1fbb44e645e4fae8c4a4453e


      parent reply	other threads:[~2026-08-03 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  3:39 [PATCH net-next v2 0/2] net: phy: Add Maxio MAE0621A support Liu Changjie
2026-07-17  3:44 ` [PATCH net-next v2 2/2] net: phy: Add support for the Maxio MAE0621A Liu Changjie
2026-07-17 15:15   ` Andrew Lunn
2026-07-17  3:44 ` [PATCH net-next v2 1/2] dt-bindings: net: Add Maxio MAE0621A PHY Liu Changjie
2026-07-17  9:05   ` Krzysztof Kozlowski
2026-07-17  9:26     ` Liu Changjie
2026-07-19  6:04   ` Krzysztof Kozlowski
2026-08-03 13:31 ` Andre Przywara [this message]

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=2635661d-4be2-4abf-84aa-c3024941f787@arm.com \
    --to=andre.przywara@arm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=jie.luo@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=liucj1228@outlook.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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