[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211015125527.28445238@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 15 Oct 2021 12:55:27 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Rob Herring <robh@...nel.org>,
Vladimir Oltean <vladimir.oltean@....com>
Cc: Prasanna Vengateshan <prasanna.vengateshan@...rochip.com>,
devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Russell King <linux@...linux.org.uk>,
Ansuel Smith <ansuelsmth@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, Vivien Didelot <vivien.didelot@...il.com>,
Andrew Lunn <andrew@...n.ch>, Shawn Guo <shawnguo@...nel.org>,
Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Alvin Šipraga <alsi@...g-olufsen.dk>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 5/6] dt-bindings: net: dsa: sja1105: add
{rx,tx}-internal-delay-ps
On Thu, 14 Oct 2021 09:31:04 -0500 Rob Herring wrote:
> On Thu, 14 Oct 2021 01:23:12 +0300, Vladimir Oltean wrote:
> > Add a schema validator to nxp,sja1105.yaml and to dsa.yaml for explicit
> > MAC-level RGMII delays. These properties must be per port and must be
> > present only for a phy-mode that represents RGMII.
> >
> > We tell dsa.yaml that these port properties might be present, we also
> > define their valid values for SJA1105. We create a common definition for
> > the RX and TX valid range, since it's quite a mouthful.
> >
> > We also modify the example to include the explicit RGMII delay properties.
> > On the fixed-link ports (in the example, port 4), having these explicit
> > delays is actually mandatory, since with the new behavior, the driver
> > shouts that it is interpreting what delays to apply based on phy-mode.
> >
> > Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
>
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
FWIW I dropped the set from pw based on Rob's report, I see a mention
of possible issues with fsl-lx2160a-bluebox3.dts, but it's not clear
to me which DT is disagreeing with the schema.. or is the schema itself
not 100?
Powered by blists - more mailing lists