From: Vladimir Oltean <olteanv@gmail.com>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux@armlinux.org.uk,
Tristram.Ha@microchip.com, richardcochran@gmail.com,
ceggers@arri.de
Subject: Re: [Patch net-next v3 09/13] net: dsa: microchip: ptp: move pdelay_rsp correction field to tail tag
Date: Fri, 9 Dec 2022 17:08:18 +0200 [thread overview]
Message-ID: <20221209150818.jmva3syosfxjigpg@skbuf> (raw)
In-Reply-To: <20221209072437.18373-10-arun.ramadoss@microchip.com> <20221209072437.18373-10-arun.ramadoss@microchip.com>
On Fri, Dec 09, 2022 at 12:54:33PM +0530, Arun Ramadoss wrote:
> From: Christian Eggers <ceggers@arri.de>
>
> For PDelay_Resp messages we will likely have a negative value in the
> correction field. The switch hardware cannot correctly update such
> values (produces an off by one error in the UDP checksum), so it must be
> moved to the time stamp field in the tail tag. Format of the correction
> field is 48 bit ns + 16 bit fractional ns. After updating the
> correction field, clone is no longer required hence it is freed.
>
> Signed-off-by: Christian Eggers <ceggers@arri.de>
Similar. This needs your sign off too.
next prev parent reply other threads:[~2022-12-09 15:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 7:24 [Patch net-next v3 00/13] net: dsa: microchip: add PTP support for KSZ9563/KSZ8563 and LAN937x Arun Ramadoss
2022-12-09 7:24 ` [Patch net-next v3 01/13] net: dsa: microchip: ptp: add the posix clock support Arun Ramadoss
2022-12-09 11:36 ` Vladimir Oltean
2022-12-10 0:10 ` Florian Fainelli
2022-12-09 7:24 ` [Patch net-next v3 02/13] net: dsa: microchip: ptp: Initial hardware time stamping support Arun Ramadoss
2022-12-09 15:19 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 03/13] net: dsa: microchip: ptp: add 4 bytes in tail tag when ptp enabled Arun Ramadoss
2022-12-09 11:38 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 04/13] net: dsa: microchip: ptp: manipulating absolute time using ptp hw clock Arun Ramadoss
2022-12-09 7:24 ` [Patch net-next v3 05/13] net: dsa: microchip: ptp: enable interrupt for timestamping Arun Ramadoss
2022-12-09 19:40 ` Christian Eggers
2022-12-12 10:13 ` Arun.Ramadoss
2022-12-09 7:24 ` [Patch net-next v3 06/13] net: ptp: add helper for one-step P2P clocks Arun Ramadoss
2022-12-09 15:02 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 07/13] net: dsa: microchip: ptp: add packet reception timestamping Arun Ramadoss
2022-12-09 15:06 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 08/13] net: dsa: microchip: ptp: add packet transmission timestamping Arun Ramadoss
2022-12-09 15:07 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 09/13] net: dsa: microchip: ptp: move pdelay_rsp correction field to tail tag Arun Ramadoss
2022-12-09 15:08 ` Vladimir Oltean [this message]
2022-12-09 7:24 ` [Patch net-next v3 10/13] net: dsa: microchip: ptp: add periodic output signal Arun Ramadoss
2022-12-09 15:16 ` Vladimir Oltean
2022-12-09 7:24 ` [Patch net-next v3 11/13] net: dsa: microchip: ptp: add support for perout programmable pins Arun Ramadoss
2022-12-09 7:24 ` [Patch net-next v3 12/13] net: dsa: microchip: ptp: lan937x: add 2 step timestamping Arun Ramadoss
2022-12-09 7:24 ` [Patch net-next v3 13/13] net: dsa: microchip: ptp: lan937x: Enable periodic output in LED pins Arun Ramadoss
2022-12-09 15:24 ` [Patch net-next v3 00/13] net: dsa: microchip: add PTP support for KSZ9563/KSZ8563 and LAN937x Vladimir Oltean
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=20221209150818.jmva3syosfxjigpg@skbuf \
--to=olteanv@gmail.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.