public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Wei Fang <wei.fang@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Clark Wang <xiaoning.wang@nxp.com>,
	"christophe.leroy@csgroup.eu" <christophe.leroy@csgroup.eu>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH net-next 02/11] dt-bindings: net: add i.MX95 ENETC support
Date: Thu, 10 Oct 2024 11:16:50 -0400	[thread overview]
Message-ID: <Zwfv4if3mWPLStb/@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <PAXPR04MB8510E8B2938E88DB022648F588782@PAXPR04MB8510.eurprd04.prod.outlook.com>

On Thu, Oct 10, 2024 at 02:14:50AM +0000, Wei Fang wrote:
> > -----Original Message-----
> > From: Rob Herring <robh@kernel.org>
> > Sent: 2024年10月10日 4:53
> > To: Frank Li <frank.li@nxp.com>
> > Cc: Wei Fang <wei.fang@nxp.com>; davem@davemloft.net;
> > edumazet@google.com; kuba@kernel.org; pabeni@redhat.com;
> > krzk+dt@kernel.org; conor+dt@kernel.org; Vladimir Oltean
> > <vladimir.oltean@nxp.com>; Claudiu Manoil <claudiu.manoil@nxp.com>; Clark
> > Wang <xiaoning.wang@nxp.com>; christophe.leroy@csgroup.eu;
> > linux@armlinux.org.uk; bhelgaas@google.com; imx@lists.linux.dev;
> > netdev@vger.kernel.org; devicetree@vger.kernel.org;
> > linux-kernel@vger.kernel.org; linux-pci@vger.kernel.org
> > Subject: Re: [PATCH net-next 02/11] dt-bindings: net: add i.MX95 ENETC support
> >
> > On Wed, Oct 09, 2024 at 12:29:57PM -0400, Frank Li wrote:
> > > On Wed, Oct 09, 2024 at 05:51:07PM +0800, Wei Fang wrote:
> > > > The ENETC of i.MX95 has been upgraded to revision 4.1, and the vendor
> > > > ID and device ID have also changed, so add the new compatible strings
> > > > for i.MX95 ENETC. In addition, i.MX95 supports configuration of RGMII
> > > > or RMII reference clock.
> > > >
> > > > Signed-off-by: Wei Fang <wei.fang@nxp.com>
> > > > ---
> > > >  .../devicetree/bindings/net/fsl,enetc.yaml    | 23 +++++++++++++++----
> > > >  1 file changed, 19 insertions(+), 4 deletions(-)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > b/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > > index e152c93998fe..1a6685bb7230 100644
> > > > --- a/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > > +++ b/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > > @@ -20,14 +20,29 @@ maintainers:
> > > >
> > > >  properties:
> > > >    compatible:
> > > > -    items:
> > > > -      - enum:
> > > > -          - pci1957,e100
> > > > -      - const: fsl,enetc
> > > > +    oneOf:
> > > > +      - items:
> > > > +          - enum:
> > > > +              - pci1957,e100
> > > > +          - const: fsl,enetc
> > > > +      - items:
> > > > +          - const: pci1131,e101
> > > > +      - items:
> > > > +          - enum:
> > > > +              - nxp,imx95-enetc
> > > > +          - const: pci1131,e101
> > >
> > >     oneOf:
> > >       - items:
> > >           - enum:
> > >               - pci1957,e100
> > >           - const: fsl,enetc
> > >       - items:
> > >           - const: pci1131,e101
> > >           - enum:
> > >               - nxp,imx95-enetc
> >
> > const.
> >
> > Or maybe just drop it. Hopefully the PCI ID changes with each chip. If
> > not, we kind of have the compatibles backwards.
>
> I am pretty sure that the device ID will not change in later chips unless
> the functionality of the ENETC is different.

It is quite weird for PCIe devices. Device ID, at least Reversion ID should
change. At least, I have not see use "nxp,imx95-enetc" at driver code.

Frank

> >
> > >           minItems: 1
> >
> > Then why have the fallback?

  reply	other threads:[~2024-10-10 15:17 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  9:51 [PATCH net-next 00/11] add basic support for i.MX95 NETC Wei Fang
2024-10-09  9:51 ` [PATCH net-next 01/11] dt-bindings: net: add compatible string for i.MX95 EMDIO Wei Fang
2024-10-09 16:26   ` Frank Li
2024-10-10  1:42     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 02/11] dt-bindings: net: add i.MX95 ENETC support Wei Fang
2024-10-09 16:29   ` Frank Li
2024-10-09 20:53     ` Rob Herring
2024-10-10  2:14       ` Wei Fang
2024-10-10 15:16         ` Frank Li [this message]
2024-10-11  1:56           ` Wei Fang
2024-10-10  2:00     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 03/11] dt-bindings: net: add bindings for NETC blocks control Wei Fang
2024-10-09 16:36   ` Frank Li
2024-10-10  2:10     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 04/11] net: enetc: add initial netc-blk-ctrl driver support Wei Fang
2024-10-09 17:02   ` Frank Li
2024-10-10  2:31     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 05/11] net: enetc: add enetc-pf-common " Wei Fang
2024-10-09 17:16   ` Frank Li
2024-10-10  3:19     ` Wei Fang
2024-10-10 14:16   ` kernel test robot
2024-10-10 17:10   ` kernel test robot
2024-10-13  2:27   ` kernel test robot
2024-10-09  9:51 ` [PATCH net-next 06/11] net: enetc: only enable ERR050089 workaround on LS1028A Wei Fang
2024-10-09  9:51 ` [PATCH net-next 07/11] PCI: Add NXP NETC vendor ID and device IDs Wei Fang
2024-10-10 19:34   ` Bjorn Helgaas
2024-10-11  2:06     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 08/11] net: enetc: add i.MX95 EMDIO support Wei Fang
2024-10-09  9:51 ` [PATCH net-next 09/11] net: enetc: optimize the allocation of tx_bdr Wei Fang
2024-10-09 17:25   ` Frank Li
2024-10-10  3:25     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 10/11] net: enetc: add preliminary support for i.MX95 ENETC PF Wei Fang
2024-10-09 17:41   ` Frank Li
2024-10-10  4:59     ` Wei Fang
2024-10-10 15:22       ` Frank Li
2024-10-11  2:02         ` Wei Fang
2024-10-11  4:11           ` Frank Li
2024-10-11  7:16             ` Wei Fang
2024-10-14  9:06   ` Simon Horman
2024-10-14  9:13     ` Wei Fang
2024-10-09  9:51 ` [PATCH net-next 11/11] MAINTAINERS: update ENETC driver files and maintainers Wei Fang
2024-10-10 19:20   ` Frank Li
2024-10-11  2:05     ` Wei Fang
2024-10-11  4:13       ` Frank Li
2024-10-11  7: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=Zwfv4if3mWPLStb/@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=claudiu.manoil@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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