From: Christian Eggers <ceggers@arri.de>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Helmut Grohne <helmut.grohne@intenta.de>,
Paul Barker <pbarker@konsulko.com>,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
George McCollister <george.mccollister@gmail.com>,
Marek Vasut <marex@denx.de>,
Tristram Ha <Tristram.Ha@microchip.com>,
"David S . Miller" <davem@davemloft.net>,
Woojung Huh <woojung.huh@microchip.com>,
"Microchip Linux Driver Support" <UNGLinuxDriver@microchip.com>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 7/9] net: dsa: microchip: ksz9477: add hardware time stamping support
Date: Tue, 17 Nov 2020 12:27:17 +0100 [thread overview]
Message-ID: <1813904.kIZFssEuCH@n95hx1g2> (raw)
In-Reply-To: <2477133.fPTnnZM2lx@n95hx1g2>
On Thursday, 12 November 2020, 16:28:44 CET, Christian Eggers wrote:
> Hi Vladimir,
>
> On Tuesday, 10 November 2020, 20:32:45 CET, Vladimir Oltean wrote:
> > But something is still wrong if you need to special-case the negative
> > correctionField, it looks like the arithmetic is not done on the correct
> > number of bits, either by the driver or by the hardware.
>
> I got it!
I got it not!
While keeping the (negative) correction field works perfect when using
PTP over L2 (what I did the last weeks), this causes an unwanted side effect
when using UDP:
...
> User Datagram Protocol, Src Port: 319, Dst Port: 319
>
> Source Port: 319
> Destination Port: 319
> Length: 62
>
> Checksum: 0x2285 incorrect, should be 0x2286 (maybe caused by "UDP checksum offload"?)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [Checksum Status: Bad]
> [Stream index: 0]
> [Timestamps]
>
> Precision Time Protocol (IEEE1588)
>
> 0000 .... = transportSpecific: 0x0
> .... 0011 = messageId: Peer_Delay_Resp Message (0x3)
> 0000 .... = Reserved: 0
> .... 0010 = versionPTP: 2
> messageLength: 54
> subdomainNumber: 0
> Reserved: 0
> flags: 0x0000
> correction: 5579788,000000 nanoseconds
> Reserved: 0
> ClockIdentity: 0x849000fffe0980f7
> SourcePortID: 1
> sequenceId: 785
> control: Other Message (5)
> logMessagePeriod: 127
> requestreceiptTimestamp (seconds): 0
> requestreceiptTimestamp (nanoseconds): 0
> requestingSourcePortIdentity: 0x849000fffe0980f6
> requestingSourcePortId: 2
While correction field is ok (residential delay ~5ms, using one printk...),
the UDP checksum is off by one in all PDelay_Resp messages.
The KSZ device offers on option to set the UDP checksum to zero, but this also
didn't help and additionally wouldn't work for IPv6.
It seems that I should return to "moving T2 from the correction field to the
tail tag" on tx.
regards
Christian
next prev parent reply other threads:[~2020-11-17 11:28 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 17:24 [RFC PATCH 0/9] net: dsa: microchip: PTP support for KSZ956x Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 1/9] dt-bindings: net: dsa: convert ksz bindings document to yaml Christian Eggers
2020-10-21 6:52 ` Kurt Kanzenbach
2020-10-21 8:46 ` Christian Eggers
2020-10-22 0:16 ` Vladimir Oltean
2020-10-22 0:40 ` Florian Fainelli
2020-10-22 10:54 ` Kurt Kanzenbach
2020-10-22 12:37 ` Vladimir Oltean
2020-10-22 19:17 ` Florian Fainelli
2020-10-26 13:54 ` Rob Herring
2020-10-19 17:24 ` [RFC PATCH net-next 2/9] net: dsa: microchip: split ksz_common.h Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 3/9] net: dsa: microchip: rename ksz9477.c to ksz9477_main.o Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 4/9] dt-bindings: net: dsa: microchip,ksz: add interrupt property Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 5/9] net: dsa: microchip: ksz9477: basic interrupt support Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 6/9] net: dsa: microchip: ksz9477: add Posix clock support for chip PTP clock Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 7/9] net: dsa: microchip: ksz9477: add hardware time stamping support Christian Eggers
2020-10-20 0:10 ` Vladimir Oltean
2020-10-20 8:39 ` Christian Eggers
2020-10-21 23:39 ` Vladimir Oltean
2020-10-22 2:42 ` Richard Cochran
2020-10-22 7:30 ` Christian Eggers
2020-10-22 10:17 ` Christian Eggers
2020-10-30 18:24 ` Vladimir Oltean
2020-11-01 9:35 ` Christian Eggers
2020-11-01 11:10 ` Vladimir Oltean
2020-11-01 22:14 ` Christian Eggers
2020-11-01 23:41 ` Vladimir Oltean
2020-11-01 23:55 ` Vladimir Oltean
2020-11-02 10:35 ` Christian Eggers
2020-11-02 12:28 ` Vladimir Oltean
2020-10-22 3:02 ` Richard Cochran
2020-10-22 9:01 ` Vladimir Oltean
2020-10-22 10:50 ` Vladimir Oltean
2020-10-22 11:11 ` Christian Eggers
2020-10-22 11:32 ` Vladimir Oltean
2020-10-22 14:34 ` Richard Cochran
2020-11-05 20:18 ` Christian Eggers
2020-11-10 1:42 ` Vladimir Oltean
2020-11-10 14:36 ` Christian Eggers
2020-11-10 16:40 ` Vladimir Oltean
2020-11-10 19:32 ` Vladimir Oltean
2020-11-11 21:49 ` Christian Eggers
2020-11-11 21:50 ` Christian Eggers
2020-11-12 15:28 ` Christian Eggers
2020-11-12 15:38 ` Vladimir Oltean
2020-11-17 11:27 ` Christian Eggers [this message]
2020-10-19 17:24 ` [RFC PATCH net-next 8/9] net: dsa: microchip: ksz9477: add Pulse Per Second (PPS) support Christian Eggers
2020-10-19 17:46 ` Vladimir Oltean
2020-10-20 8:38 ` Christian Eggers
2020-10-19 17:24 ` [RFC PATCH net-next 9/9] net: dsa: microchip: ksz9477: add periodic output support Christian Eggers
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=1813904.kIZFssEuCH@n95hx1g2 \
--to=ceggers@arri.de \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=codrin.ciubotariu@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=helmut.grohne@intenta.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pbarker@konsulko.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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).