netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Lukasz Majewski <lukma@denx.de>,
	netdev@vger.kernel.org,
	Arun Ramadoss <arun.ramadoss@microchip.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	Tristram.Ha@microchip.com, Christian Eggers <ceggers@arri.de>
Subject: Re: [PTP][KSZ9477][p2p1step] Questions for PTP support on KSZ9477 device
Date: Wed, 18 Jun 2025 08:27:11 +0200	[thread overview]
Message-ID: <aFJcP74s0xprhWLz@pengutronix.de> (raw)
In-Reply-To: <aFJJlGzu4DrmqH3P@hoboy.vegasvil.org>

On Tue, Jun 17, 2025 at 10:07:32PM -0700, Richard Cochran wrote:
> On Tue, Jun 17, 2025 at 05:10:11PM +0100, Vadim Fedorenko wrote:
> > On 17/06/2025 06:25, Oleksij Rempel wrote:
> > > No, this will not work correctly. Both sides must use the same timestamping
> > > mode: either both "one step" or both "two step".
> > 
> > I'm not quite sure this statement is fully correct. I don't have a
> > hardware on hands to make this setup, but reading through the code in
> > linuxptp - the two-step fsm kicks off based on the message type bit. In case
> > when linuxptp receives 1-step sync, it does all the calculations.
> 
> Correct.
> 
> > For delay response packets on GM side it doesn't matter as GM doesn't do
> > any calculations. I don't see any requirements here from the perspective
> > of protocol itself.
> 
> Running on a PTP client, ptp4l will happily use either one or two step
> Sync messages from the server.

Thank you for clarification! In this case, something else was wrong, and
I made a wrong assumption. I had a non-working configuration, so I made
the assumption without verifying the code.

Best Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2025-06-18  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 15:25 [PTP][KSZ9477][p2p1step] Questions for PTP support on KSZ9477 device Lukasz Majewski
2025-06-17  5:25 ` Oleksij Rempel
2025-06-17  9:53   ` Lukasz Majewski
2025-06-17 16:10   ` Vadim Fedorenko
2025-06-18  5:07     ` Richard Cochran
2025-06-18  6:27       ` Oleksij Rempel [this message]
2025-06-26 21:33         ` Lukasz Majewski
2025-06-27 21:58           ` Vladimir Oltean
2025-06-29  9:28             ` Lukasz Majewski
2025-06-30  4:36               ` Oleksij Rempel

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=aFJcP74s0xprhWLz@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=Tristram.Ha@microchip.com \
    --cc=arun.ramadoss@microchip.com \
    --cc=ceggers@arri.de \
    --cc=lukma@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    /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).