From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sneh Shah <quic_snehshah@quicinc.com>
Cc: Andrew Halaney <ahalaney@redhat.com>,
Vinod Koul <vkoul@kernel.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com
Subject: Re: [PATCH net-next] net: stmmac: dwmac-qcom-ethqos: Add support for 2.5G SGMII
Date: Wed, 29 May 2024 21:09:19 +0100 [thread overview]
Message-ID: <ZleLb+dtJ8Uspq4S@shell.armlinux.org.uk> (raw)
In-Reply-To: <d246bd64-18b3-4002-bc71-eccd67bbd61f@quicinc.com>
On Wed, May 29, 2024 at 07:43:15PM +0530, Sneh Shah wrote:
> In this version of qualcomm ethernet, PCS is not an independent HW
> block. It is integrated to MAC block itself. It has very limited
> configuration.Here PCS doesn't have it's own link speed/duplex
> capabities. Hence we are bypassing all this PCS related functionalities.
I want to concentrate on this part first - we'll address the 2.5G
issues separately once I've got a picture of this hardware (and thus
can work out what needs to change in my phylink_pcs implementation to
support the standard Cisco SGMII speeds.
From what I understand you're saying, your integrated PCS is different
from the DesignWare integrated PCS?
Which core does it use? dwmac4_core.c or dwmac1000_core.c, or some
other? Not knowing which core makes asking the following questions
harder, since I'm having to double them up to cover both cores with
their different definitions.
Does it only present its status via the GMAC_PHYIF_CONTROL_STATUS or
GMAC_RGSMIIIS register?
From what you're saying:
- if using the dwmac1000 core, then for the registers at GMAC_PCS_BASE
(0xc0 offset)...
- if using the dwmac4 core, then for registers at GMAC_PCS_BASE
(0xe0 offset)...
... is it true that only the GMAC_AN_CTRL() register is implemented
and none of the other registers listed in stmmac_pcs.h?
In terms of interrupts when the link status changes, how do they
present? Are they through the GMAC_INT_RGSMIIS interrupt only?
What about GMAC_INT_PCS_LINK or GMAC_INT_PCS_ANE? Or in the case
of the other core, is it through the PCS_RGSMIIIS_IRQ interrupt
only? Similarly, what about PCS_LINK_IRQ or PCS_ANE_IRQ?
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-05-29 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 7:11 [PATCH net-next] net: stmmac: dwmac-qcom-ethqos: Add support for 2.5G SGMII Sneh Shah
2023-12-18 14:21 ` Maxime Chevallier
2023-12-18 14:32 ` Sneh Shah
2023-12-18 16:20 ` Andrew Halaney
2023-12-18 16:31 ` Andrew Halaney
2023-12-20 7:32 ` Sneh Shah
2023-12-20 15:59 ` Andrew Halaney
2023-12-21 8:53 ` Sneh Shah
2023-12-21 14:30 ` Andrew Halaney
2023-12-21 16:58 ` [Linux-stm32] " Maxime Chevallier
2024-05-26 16:27 ` Russell King (Oracle)
2024-05-28 22:35 ` Andrew Halaney
2024-05-29 14:13 ` Sneh Shah
2024-05-29 14:28 ` Andrew Lunn
2024-05-29 20:13 ` Russell King (Oracle)
2024-06-03 11:15 ` Sneh Shah
2024-05-29 20:09 ` Russell King (Oracle) [this message]
2024-06-03 11:27 ` Sneh Shah
2024-06-03 13:12 ` 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=ZleLb+dtJ8Uspq4S@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ahalaney@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=bhupesh.sharma@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kernel@quicinc.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_snehshah@quicinc.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).