From: Jakub Kicinski <kuba@kernel.org>
To: Wei Fang <wei.fang@nxp.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>, Frank Li <frank.li@nxp.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 net-next 0/6] net: enetc: Add i.MX94 ENETC support
Date: Tue, 28 Oct 2025 17:19:00 -0700 [thread overview]
Message-ID: <20251028171900.5f0ba82c@kernel.org> (raw)
In-Reply-To: <PAXPR04MB8510AC62551ABD89E75EB97188FAA@PAXPR04MB8510.eurprd04.prod.outlook.com>
On Wed, 29 Oct 2025 00:13:14 +0000 Wei Fang wrote:
> > On Mon, 27 Oct 2025 09:44:57 +0800 Wei Fang wrote:
> > > i.MX94 NETC has two kinds of ENETCs, one is the same as i.MX95, which
> > > can be used as a standalone network port. The other one is an internal
> > > ENETC, it connects to the CPU port of NETC switch through the pseudo
> > > MAC. Also, i.MX94 have multiple PTP Timers, which is different from
> > > i.MX95. Any PTP Timer can be bound to a specified standalone ENETC by
> > > the IERB ETBCR registers. Currently, this patch only add ENETC support
> > > and Timer support for i.MX94. The switch will be added by a separate
> > > patch set.
> >
> > Is there a reason to add the imx94 code after imx95?
>
> Actually, i.MX94 is the latest i.MX SoC, which is tapped out after
> i.MX95 (about 1 year).
I see, so there is some logic behind it.
I'm not sure this will still be clear 10 years from now to the people
who come after us. 1 year is not a long time. But up to you..
next prev parent reply other threads:[~2025-10-29 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 1:44 [PATCH v3 net-next 0/6] net: enetc: Add i.MX94 ENETC support Wei Fang
2025-10-27 1:44 ` [PATCH v3 net-next 1/6] dt-bindings: net: netc-blk-ctrl: add compatible string for i.MX94 platforms Wei Fang
2025-10-27 1:44 ` [PATCH v3 net-next 2/6] dt-bindings: net: enetc: add compatible string for ENETC with pseduo MAC Wei Fang
2025-10-27 1:45 ` [PATCH v3 net-next 3/6] net: enetc: add preliminary i.MX94 NETC blocks control support Wei Fang
2025-10-27 1:45 ` [PATCH v3 net-next 4/6] net: enetc: add ptp timer binding support for i.MX94 Wei Fang
2025-10-28 23:56 ` Jakub Kicinski
2025-10-29 0:14 ` Wei Fang
2025-10-27 1:45 ` [PATCH v3 net-next 5/6] net: enetc: add basic support for the ENETC with pseudo MAC " Wei Fang
2025-10-27 8:26 ` Claudiu Manoil
2025-10-27 1:45 ` [PATCH v3 net-next 6/6] net: enetc: add standalone ENETC support " Wei Fang
2025-10-28 23:57 ` [PATCH v3 net-next 0/6] net: enetc: Add i.MX94 ENETC support Jakub Kicinski
2025-10-29 0:13 ` Wei Fang
2025-10-29 0:19 ` Jakub Kicinski [this message]
2025-10-29 0:26 ` 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=20251028171900.5f0ba82c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@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;
as well as URLs for NNTP newsgroup(s).