[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21674031.EfDdHjke4D@n95hx1g2>
Date: Wed, 2 Nov 2022 14:12:25 +0100
From: Christian Eggers <ceggers@...i.de>
To: <olteanv@...il.com>, <Arun.Ramadoss@...rochip.com>
CC: <andrew@...n.ch>, <linux-kernel@...r.kernel.org>,
<UNGLinuxDriver@...rochip.com>, <vivien.didelot@...il.com>,
<linux@...linux.org.uk>, <Tristram.Ha@...rochip.com>,
<f.fainelli@...il.com>, <kuba@...nel.org>, <edumazet@...gle.com>,
<pabeni@...hat.com>, <richardcochran@...il.com>,
<netdev@...r.kernel.org>, <Woojung.Huh@...rochip.com>,
<davem@...emloft.net>, <b.hutchman@...il.com>
Subject: Re: [RFC Patch net-next 0/6] net: dsa: microchip: add gPTP support for LAN937x switch
Hi Arun,
On Thursday, 27 October 2022, 17:51:54 CEST, Arun.Ramadoss@...rochip.com wrote:
> I tried to bring up the KSZ9563 setup following are my observation
> - With this patch series, I am getting the Null pointer exception.
> - After applying the patch provided by you, switch probe is successful.
>
> Usually I test the gPTP using the following command
> # ptp4l -f ~/ptp4l/gPTP.cfg -i lan1
>
> How did you test this PTP in your setup, so that I can also get the
> same result as below.
as the KSZ9563 supports no 2-step time stamping, I use 1-step with E2E.
The problem with E2E is, that the "master/slave" filter
on the KSZ9563 filters out some message types. In order to circumvent
this, I use the KSZ as slave_only for the first tests. Later I would like
to use P2P, but this requires additional implementation in the driver.
> > > Maybe this could be mentioned somewhere (e.g. extra line in file
> > > header of
> > > ksz_ptp.c).
>
> Sure, I will add it in the File Header in the next version.
thanks.
>
> I thought 1PPS and periodic output are same, So I sent the 1PPS patch.
> I need to look into periodic output.
I fell the same when I first started with PTP... But maybe you can use
same code for periodic output from my original patches.
regards,
Christian
Powered by blists - more mailing lists