From: Andrew Lunn <andrew@lunn.ch>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [net-next PATCH v2 09/11] fbnic: Add SW shim for MDIO interface to PMA/PMD and PCS
Date: Mon, 3 Nov 2025 19:59:31 +0100 [thread overview]
Message-ID: <2fabbe4a-754d-40bb-ba10-48ef79df875c@lunn.ch> (raw)
In-Reply-To: <176218926115.2759873.9672365918256502904.stgit@ahduyck-xeon-server.home.arpa>
> The interface will consist of 2 PHYs each consisting of a PMA/PMD and a PCS
> located at addresses 0 and 1.
I'm missing a bit of architecture here.
At least for speeds up to 10G, we have the MAC enumerate what it can
do, the PCS enumerates its capabilities, and we read the EERPOM of the
SFP to find out what it supports. From that, we can figure out the
subset of link modes which are supported, and configure the MAC and
PCS as required.
What information is missing from this picture that requires the
PMA/PMD to be represented? And how is this going to work when we do
have access to the SFPs EERPOM?
Andrew
next prev parent reply other threads:[~2025-11-03 18:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 16:59 [net-next PATCH v2 00/11] net: phy: Add support for fbnic PHY w/ 25G, 50G, and 100G support Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 01/11] net: phy: Add support for 25, 50 and 100Gbps PMA to genphy_c45_read_pma Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 02/11] net: phy: Add support for 25G, 50G, and 100G interfaces to xpcs driver Alexander Duyck
2025-11-03 17:42 ` Russell King (Oracle)
2025-11-03 17:00 ` [net-next PATCH v2 03/11] net: phy: Fix PMA identifier handling in XPCS Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 04/11] net: phy: Add identifier for fbnic PMA and use it to skip initial reset Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 05/11] net: phy: Add fbnic specific PHY driver fbnic_phy Alexander Duyck
2025-11-03 20:50 ` Heiner Kallweit
2025-11-03 17:00 ` [net-next PATCH v2 06/11] fbnic: Rename PCS IRQ to MAC IRQ as it is actually a MAC interrupt Alexander Duyck
2025-11-03 17:47 ` Russell King (Oracle)
2025-11-03 18:49 ` Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 07/11] fbnic: Add logic to track PMD state via MAC/PCS signals Alexander Duyck
2025-11-03 17:00 ` [net-next PATCH v2 08/11] fbnic: Cleanup handling for link down event statistics Alexander Duyck
2025-11-03 17:49 ` Russell King (Oracle)
2025-11-03 18:44 ` Alexander Duyck
2025-11-03 17:01 ` [net-next PATCH v2 09/11] fbnic: Add SW shim for MDIO interface to PMA/PMD and PCS Alexander Duyck
2025-11-03 18:59 ` Andrew Lunn [this message]
2025-11-03 20:18 ` Alexander Duyck
2025-11-03 21:49 ` Andrew Lunn
2025-11-04 0:26 ` Alexander Duyck
2025-11-03 17:01 ` [net-next PATCH v2 10/11] fbnic: Add phydev representing PMD to phylink setup Alexander Duyck
2025-11-03 17:01 ` [net-next PATCH v2 11/11] fbnic: Replace use of internal PCS w/ Designware XPCS Alexander Duyck
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=2fabbe4a-754d-40bb-ba10-48ef79df875c@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexander.duyck@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kernel-team@meta.com \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.