[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251028165757.3b7c2f96@kernel.org>
Date: Tue, 28 Oct 2025 16:57:57 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Wei Fang <wei.fang@....com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
claudiu.manoil@....com, vladimir.oltean@....com, xiaoning.wang@....com,
Frank.Li@....com, andrew+netdev@...n.ch, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, richardcochran@...il.com,
imx@...ts.linux.dev, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v3 net-next 0/6] net: enetc: Add i.MX94 ENETC support
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?
If in doubt order things alphabetically.
Powered by blists - more mailing lists