From: Vladimir Oltean <olteanv@gmail.com>
To: Arun.Ramadoss@microchip.com
Cc: andrew@lunn.ch, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, vivien.didelot@gmail.com,
linux@armlinux.org.uk, Tristram.Ha@microchip.com,
f.fainelli@gmail.com, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, richardcochran@gmail.com,
netdev@vger.kernel.org, Woojung.Huh@microchip.com,
davem@davemloft.net
Subject: Re: [RFC Patch net-next 0/6] net: dsa: microchip: add gPTP support for LAN937x switch
Date: Tue, 18 Oct 2022 12:55:15 +0300 [thread overview]
Message-ID: <20221018095515.tnhqjlyvu3dmtn3q@skbuf> (raw)
In-Reply-To: <ce76fa72ad1dd9d4f86a0bdcbd2ae473e2f29262.camel@microchip.com>
On Tue, Oct 18, 2022 at 06:29:17AM +0000, Arun.Ramadoss@microchip.com wrote:
> > On Fri, Oct 14, 2022 at 08:58:51PM +0530, Arun Ramadoss wrote:
> > > The LAN937x switch has capable for supporting IEEE 1588 PTP protocol. This
> > > patch series add gPTP profile support and tested using the ptp4l application.
> > > LAN937x has the same PTP register set similar to KSZ9563, hence the
> > > implementation has been made common for the ksz switches. But the testing is
> > > done only for lan937x switch.
> >
> > Unrelated to the proposed implementation. What user space stack do you
> > use for gPTP bridging?
>
> I had used LinuxPTP stack for testing this patch set and in specific
> linuxptp/configs/gptp.cfg
>
> Test Setup is of
> LAN9370 DUT1 <LAN1> --- LAN9370 DUT2 <LAN1>
>
> Ran the below command in both DUTS
> #ptp4l -f ~/linuxptp/configs/gptp.cfg -i lan1
gPTP bridges are when you specify "-i" more than once, similar to how
1588 boundary clocks are created in ptp4l. Linuxptp does not support
gPTP bridges; the time information needs to be relayed differently
compared to both a BC and a TC, and there is also a Follow_Up information
TLV which needs to be updated.
So I guess the answer is, you don't test gPTP bridging, ok.
prev parent reply other threads:[~2022-10-18 9:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 15:28 [RFC Patch net-next 0/6] net: dsa: microchip: add gPTP support for LAN937x switch Arun Ramadoss
2022-10-14 15:28 ` [RFC Patch net-next 1/6] net: dsa: microchip: adding the posix clock support Arun Ramadoss
2022-10-14 15:28 ` [RFC Patch net-next 2/6] net: dsa: microchip: Initial hardware time stamping support Arun Ramadoss
2022-10-14 15:28 ` [RFC Patch net-next 3/6] net: dsa: microchip: Manipulating absolute time using ptp hw clock Arun Ramadoss
2022-10-14 15:28 ` [RFC Patch net-next 4/6] net: dsa: microchip: enable the ptp interrupt for timestamping Arun Ramadoss
2022-10-14 15:28 ` [RFC Patch net-next 5/6] net: dsa: microchip: Adding the ptp packet reception logic Arun Ramadoss
2022-10-25 6:17 ` Christian Eggers
2022-10-26 20:13 ` Vladimir Oltean
2022-10-14 15:28 ` [RFC Patch net-next 6/6] net: dsa: microchip: add the transmission tstamp logic Arun Ramadoss
2022-10-17 17:19 ` [RFC Patch net-next 0/6] net: dsa: microchip: add gPTP support for LAN937x switch Vladimir Oltean
2022-10-18 6:44 ` Arun.Ramadoss
2022-10-18 10:29 ` Vladimir Oltean
2022-10-18 13:42 ` Arun.Ramadoss
2022-10-23 20:15 ` Christian Eggers
2022-10-25 3:41 ` Arun.Ramadoss
2022-10-26 20:07 ` Vladimir Oltean
2022-10-26 16:47 ` Christian Eggers
2022-10-26 21:44 ` Vladimir Oltean
2022-10-27 15:51 ` Arun.Ramadoss
2022-11-02 13:12 ` Christian Eggers
2022-11-02 13:11 ` Christian Eggers
2022-11-04 10:36 ` Arun.Ramadoss
2022-10-17 18:46 ` Vladimir Oltean
2022-10-18 6:29 ` Arun.Ramadoss
2022-10-18 9:55 ` Vladimir Oltean [this message]
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=20221018095515.tnhqjlyvu3dmtn3q@skbuf \
--to=olteanv@gmail.com \
--cc=Arun.Ramadoss@microchip.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--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 \
/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