From: Wei Fang <wei.fang@nxp.com>
To: claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: aziz.sellami@nxp.com, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/3] net: enetc: add port MDIO support for both i.MX94 and i.MX95
Date: Thu, 30 Oct 2025 17:15:35 +0800 [thread overview]
Message-ID: <20251030091538.581541-1-wei.fang@nxp.com> (raw)
For the external PHY devices, NETC provide external MDIO interface to
manage them. ENETC can use a set of MDIO registers provided by EMDIO to
access its PHY, which is a method currently supported by the driver. It
also can use its own set of MDIO registers to access its PHY, but the
premise is that its corresponding LaBCR[MDIO_PHYAD_PRTAD] needs to be
set correctly, which indicates its PHY address.
Similar to the external MDIO registers, each ENETC has a set of internal
MDIO registers to access its on-die PHY (PCS), so internal MDIO support
is also added.
Aziz Sellami (1):
net: enetc: set external MDIO PHY address for i.MX95 ENETC
Wei Fang (2):
net: enetc: set external MDIO PHY address for i.MX94 ENETC
net: enetc: add port MDIO support for ENETC v4
.../net/ethernet/freescale/enetc/enetc4_hw.h | 6 +
.../freescale/enetc/enetc_pf_common.c | 14 ++-
.../ethernet/freescale/enetc/netc_blk_ctrl.c | 111 +++++++++++++++++-
3 files changed, 128 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2025-10-30 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 9:15 Wei Fang [this message]
2025-10-30 9:15 ` [PATCH net-next 1/3] net: enetc: set external MDIO PHY address for i.MX95 ENETC Wei Fang
2025-10-30 9:15 ` [PATCH net-next 2/3] net: enetc: set external MDIO PHY address for i.MX94 ENETC Wei Fang
2025-10-30 9:15 ` [PATCH net-next 3/3] net: enetc: add port MDIO support for ENETC v4 Wei Fang
2025-10-30 17:43 ` [PATCH net-next 0/3] net: enetc: add port MDIO support for both i.MX94 and i.MX95 Andrew Lunn
2025-10-31 1:49 ` Wei Fang
2025-10-31 12:31 ` Andrew Lunn
2025-11-01 0:24 ` Wei Fang
2025-11-01 14:43 ` Andrew Lunn
2025-11-03 2:11 ` Wei Fang
2025-11-03 13:16 ` Andrew Lunn
2025-11-04 2:29 ` Wei Fang
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=20251030091538.581541-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=aziz.sellami@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoning.wang@nxp.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
all inboxes | Powered by JetHome®