From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Frank Li <frank.li@nxp.com>, Wei Fang <wei.fang@nxp.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"robh@kernel.org" <robh@kernel.org>,
"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>,
"horms@kernel.org" <horms@kernel.org>,
"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 v3 net-next 02/13] dt-bindings: net: add i.MX95 ENETC support
Date: Fri, 18 Oct 2024 08:52:55 +0200 [thread overview]
Message-ID: <3657116.R56niFO833@steina-w> (raw)
In-Reply-To: <PAXPR04MB851058F40F264FA9D20F385888402@PAXPR04MB8510.eurprd04.prod.outlook.com>
Hi,
Am Freitag, 18. Oktober 2024, 03:20:55 CEST schrieb Wei Fang:
> > -----Original Message-----
> > From: Frank Li <frank.li@nxp.com>
> > Sent: 2024年10月18日 0:23
> > To: Wei Fang <wei.fang@nxp.com>
> > Cc: davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
> > pabeni@redhat.com; robh@kernel.org; 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;
> > horms@kernel.org; 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 v3 net-next 02/13] dt-bindings: net: add i.MX95 ENETC
> > support
> >
> > On Thu, Oct 17, 2024 at 03:46:26PM +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>
> > > ---
> > > v2: Remove "nxp,imx95-enetc" compatible string.
> > > v3:
> > > 1. Add restriction to "clcoks" and "clock-names" properties and rename
> > > the clock, also remove the items from these two properties.
> > > 2. Remove unnecessary items for "pci1131,e101" compatible string.
> > > ---
> > > .../devicetree/bindings/net/fsl,enetc.yaml | 22 ++++++++++++++++---
> > > 1 file changed, 19 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > b/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > index e152c93998fe..e418c3e6e6b1 100644
> > > --- a/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > +++ b/Documentation/devicetree/bindings/net/fsl,enetc.yaml
> > > @@ -20,10 +20,13 @@ maintainers:
> > >
> > > properties:
> > > compatible:
> > > - items:
> > > + oneOf:
> > > + - items:
> > > + - enum:
> > > + - pci1957,e100
> > > + - const: fsl,enetc
> > > - enum:
> > > - - pci1957,e100
> > > - - const: fsl,enetc
> > > + - pci1131,e101
> > >
> > > reg:
> > > maxItems: 1
> > > @@ -40,6 +43,19 @@ required:
> > > allOf:
> > > - $ref: /schemas/pci/pci-device.yaml
> > > - $ref: ethernet-controller.yaml
> > > + - if:
> > > + properties:
> > > + compatible:
> > > + contains:
> > > + enum:
> > > + - pci1131,e101
> > > + then:
> > > + properties:
> > > + clocks:
> > > + maxItems: 1
> > > + description: MAC transmit/receiver reference clock
> > > + clock-names:
> > > + const: ref
> >
> > Did you run CHECK_DTBS for your dts file? clocks\clock-names should be under
> > top 'properties" firstly. Then use 'if' restrict it. But I am not sure for that. only
> > dt_binding_check is not enough because your example have not use clocks and
> > clok-names.
> >
>
> I have run dtbs_check and dt_binding_check in my local env. there were no
> warnings and errors.
Is there already the DT part somewhere? Do you mind sharing it?
Best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2024-10-18 6:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 7:46 [PATCH v3 net-next 00/13] add basic support for i.MX95 NETC Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 01/13] dt-bindings: net: add compatible string for i.MX95 EMDIO Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 02/13] dt-bindings: net: add i.MX95 ENETC support Wei Fang
2024-10-17 16:23 ` Frank Li
2024-10-18 1:20 ` Wei Fang
2024-10-18 6:52 ` Alexander Stein [this message]
2024-10-18 7:50 ` Wei Fang
2024-10-18 11:39 ` Alexander Stein
2024-10-19 9:58 ` Wei Fang
2024-10-18 13:09 ` Rob Herring
2024-10-19 9:58 ` Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 03/13] dt-bindings: net: add bindings for NETC blocks control Wei Fang
2024-10-17 16:27 ` Frank Li
2024-10-18 1:22 ` Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 04/13] net: enetc: add initial netc-blk-ctrl driver support Wei Fang
2024-10-17 16:33 ` Frank Li
2024-10-18 1:23 ` Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 05/13] net: enetc: extract common ENETC PF parts for LS1028A and i.MX95 platforms Wei Fang
2024-10-17 16:34 ` Frank Li
2024-10-17 7:46 ` [PATCH v3 net-next 06/13] net: enetc: build enetc_pf_common.c as a separate module Wei Fang
2024-10-17 16:39 ` Frank Li
2024-10-18 1:30 ` Wei Fang
2024-10-18 21:09 ` kernel test robot
2024-10-19 9:43 ` kernel test robot
2024-10-17 7:46 ` [PATCH v3 net-next 07/13] net: enetc: remove ERR050089 workaround for i.MX95 Wei Fang
2024-10-17 16:40 ` Frank Li
2024-10-17 7:46 ` [PATCH v3 net-next 08/13] PCI: Add NXP NETC vendor ID and device IDs Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 09/13] net: enetc: add i.MX95 EMDIO support Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 10/13] net: enetc: extract enetc_int_vector_init/destroy() from enetc_alloc_msix() Wei Fang
2024-10-17 16:42 ` Frank Li
2024-10-17 7:46 ` [PATCH v3 net-next 11/13] net: enetc: optimize the allocation of tx_bdr Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 12/13] net: enetc: add preliminary support for i.MX95 ENETC PF Wei Fang
2024-10-17 16:59 ` Frank Li
2024-10-18 2:04 ` Wei Fang
2024-10-18 3:05 ` Wei Fang
2024-10-18 18:10 ` Frank Li
2024-10-19 10:22 ` Wei Fang
2024-10-17 18:30 ` Claudiu Manoil
2024-10-18 2:18 ` Wei Fang
2024-10-17 7:46 ` [PATCH v3 net-next 13/13] MAINTAINERS: update ENETC driver files and maintainers 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=3657116.R56niFO833@steina-w \
--to=alexander.stein@ew.tq-group.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=frank.li@nxp.com \
--cc=horms@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).