netdev - Re: [PATCH net-next v3] net: dsa: mv88e6xxx: Enable PTP receive for mv88e6390

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230114203605.gyapleqtadgcumhk@skbuf>
Date:   Sat, 14 Jan 2023 22:36:05 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     Kurt Kanzenbach <kurt@...utronix.de>
Cc:     Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Richard Cochran <richardcochran@...il.com>,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3] net: dsa: mv88e6xxx: Enable PTP receive for
 mv88e6390

On Fri, Jan 13, 2023 at 04:12:58PM +0100, Kurt Kanzenbach wrote:
> The switch receives management traffic such as STP and LLDP. However, PTP
> messages are not received, only transmitted.
> 
> Ideally, the switch would trap all PTP messages to the management CPU. This
> particular switch has a PTP block which identifies PTP messages and traps them
> to a dedicated port. There is a register to program this destination. This is
> not used at the moment.
> 
> Therefore, program it to the same port as the MGMT traffic is trapped to. This
> allows to receive PTP messages as soon as timestamping is enabled.
> 
> In addition, the datasheet mentions that this register is not valid e.g., for
> 6190 variants. So, add a new PTP operation which is added for the 6390 and 6290
> devices.
> 
> Tested simply like this on Marvell 88E6390, revision 1:
> 
> |/ # ptp4l -2 -i lan4 --tx_timestamp_timeout=40 -m
> |[...]
> |ptp4l[147.450]: master offset         56 s2 freq   +1262 path delay       413
> |ptp4l[148.450]: master offset         22 s2 freq   +1244 path delay       434
> |ptp4l[149.450]: master offset          5 s2 freq   +1234 path delay       446
> |ptp4l[150.451]: master offset          3 s2 freq   +1233 path delay       451
> |ptp4l[151.451]: master offset          1 s2 freq   +1232 path delay       451
> |ptp4l[152.451]: master offset         -3 s2 freq   +1229 path delay       451
> |ptp4l[153.451]: master offset          9 s2 freq   +1240 path delay       451
> 
> Link: https://lore.kernel.org/r/CAFSKS=PJBpvtRJxrR4sG1hyxpnUnQpiHg4SrUNzAhkWnyt9ivg@mail.gmail.com
> Signed-off-by: Kurt Kanzenbach <kurt@...utronix.de>
> ---

Tested-by: Vladimir Oltean <olteanv@...il.com>

Thanks!