[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<OS3PR01MB6593C29DA43E7C5E862ECD3EBAB2A@OS3PR01MB6593.jpnprd01.prod.outlook.com>
Date: Tue, 14 Nov 2023 16:39:54 +0000
From: Min Li <min.li.xe@...esas.com>
To: Richard Cochran <richardcochran@...il.com>, Jacob Keller
<jacob.e.keller@...el.com>
CC: Min Li <lnimi@...mail.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>
Subject: RE: [PATCH net-next RFC 1/1] ptp: use extts interface for the
measured external offset
>
> On Mon, Nov 13, 2023 at 03:00:15PM -0800, Jacob Keller wrote:
> > You mention GNSS, but is there an example or a link to a driver change
> > you could provide to show its use?
>
> Yes, the new option must wait for a driver that implements it. Can you make
> a patch series where the driver change appears in the second patch?
Hi Richard/Jacob
Thanks for the review. Unfortunately, I don't have the patch based on the
Existing PHC driver.
But I have a brand new PHC driver for our new timing HW that implements
the feature. The measurement is done by the HW using the
Time to Digital Converter (TDC) that performs the function of a stopwatch and
measures the elapsed time between a START pulse and STOP pulses. So I have
GNSS 1pps input to the HW and TDC will perform continuous measurement
between the input 1pps and the 1pps of the onboard PHC.
I also have the ts2phc patch ready along with the PHC change. I already
tested them on our HW and proved that ts2phc can align the 2 signal using
the existing PI filter.
Please let me know how you wanna proceed. Do you want me to attach the
new PHC with this patch?
Min
Powered by blists - more mailing lists