From: Mohd Ayaan Anwar <mohd.anwar@oss.qualcomm.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: andrew@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, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: qcom: qca808x: Add .get_rate_matching support
Date: Mon, 15 Sep 2025 20:24:26 +0530 [thread overview]
Message-ID: <aMgootkPQ/GcdiXX@oss.qualcomm.com> (raw)
In-Reply-To: <aMgCA13MhTnG80_V@shell.armlinux.org.uk>
On Mon, Sep 15, 2025 at 01:09:39PM +0100, Russell King (Oracle) wrote:
> This shows that the PHY supports SGMII (4) and 2500base-X (23). However,
> as we only validate 2500base-X, this suggests stmmac doesn't support
> switching between SGMII and 2500base-X.
>
> What *exactly* is the setup with stmmac here? Do you have an external
> PCS to support 2500base-X, or are you using the stmmac internal PCS?
Internal PCS. But it's not really pure 2500base-X...
I found an older thread for this exact MAC core [0], and it looks like
we have an overclocked SGMII, i.e., 2500base-X without in-band
signalling.
Just wondering if registering a `.get_interfaces` callback in
`dwmac-qcom-ethqos.c` and doing something like the following will be
helpful?
case PHY_INTERFACE_MODE_2500BASEX:
__set_bit(PHY_INTERFACE_MODE_2500BASEX, interfaces);
fallthrough;
case PHY_INTERFACE_MODE_SGMII:
__set_bit(PHY_INTERFACE_MODE_SGMII, interfaces);
break;
...
This should ensure that both SGMII and 2500base-X are validated,
allowing switching between them.
Ayaan
---
[0] https://lore.kernel.org/netdev/4f642463-3a8c-4412-a007-42fb65c4276e@lunn.ch/
next prev parent reply other threads:[~2025-09-15 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 15:06 [PATCH net-next] net: phy: qcom: qca808x: Add .get_rate_matching support Mohd Ayaan Anwar
2025-09-14 18:10 ` Russell King (Oracle)
2025-09-14 18:37 ` Andrew Lunn
2025-09-15 8:55 ` Mohd Ayaan Anwar
2025-09-15 11:58 ` Mohd Ayaan Anwar
2025-09-15 12:09 ` Russell King (Oracle)
2025-09-15 14:54 ` Mohd Ayaan Anwar [this message]
2025-09-15 15:11 ` Russell King (Oracle)
2025-09-15 15:41 ` Mohd Ayaan Anwar
2025-09-16 22:19 ` Russell King (Oracle)
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=aMgootkPQ/GcdiXX@oss.qualcomm.com \
--to=mohd.anwar@oss.qualcomm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).