lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20230412131421.3xeeahzp6dj46jit@skbuf> Date: Wed, 12 Apr 2023 16:14:21 +0300 From: Vladimir Oltean <vladimir.oltean@....com> To: Köry Maincent <kory.maincent@...tlin.com> Cc: netdev@...r.kernel.org, kuba@...nel.org, glipus@...il.com, maxime.chevallier@...tlin.com, vadim.fedorenko@...ux.dev, richardcochran@...il.com, gerhard@...leder-embedded.com, thomas.petazzoni@...tlin.com, krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org, linux@...linux.org.uk Subject: Re: [PATCH net-next RFC v4 3/5] dt-bindings: net: phy: add timestamp preferred choice property On Thu, Apr 06, 2023 at 07:33:06PM +0200, Köry Maincent wrote: > From: Kory Maincent <kory.maincent@...tlin.com> > > Add property to select the preferred hardware timestamp layer. > The choice of using devicetree binding has been made as the PTP precision > and quality depends of external things, like adjustable clock, or the lack > of a temperature compensated crystal or specific features. Even if the > preferred timestamp is a configuration it is hardly related to the design > of the board. > > Signed-off-by: Kory Maincent <kory.maincent@...tlin.com> > --- > Documentation/devicetree/bindings/net/ethernet-phy.yaml | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > index ac04f8efa35c..32d7ef7520e6 100644 > --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml > +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > @@ -144,6 +144,13 @@ properties: > Mark the corresponding energy efficient ethernet mode as > broken and request the ethernet to stop advertising it. > > + preferred-timestamp: > + enum: > + - phy > + - mac > + description: > + Specifies the preferred hardware timestamp layer. > + > pses: > $ref: /schemas/types.yaml#/definitions/phandle-array > maxItems: 1 > -- > 2.25.1 > Do we need this device tree functionality?
Powered by blists - more mailing lists