[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2dd9fa7-c6d2-d234-7652-53014672fe0a@enneenne.com>
Date: Fri, 26 Nov 2021 11:49:25 +0100
From: Rodolfo Giometti <giometti@...eenne.com>
To: Alexander Komrakov <alexander.komrakov@...adcom.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Calculate the monotonic clock from the timespec clock
to generate PPS elapsed real-time event value and stores the result into
/sys/class/pps/pps0/assert_elapsed.
On 18/11/21 04:22, Alexander Komrakov wrote:
> From: alexkom <alexander.komrakov@...adcom.com>
>
> Because we have requirements to make sure the delta between standard time, say the GPS Time, and elapsedRealtime < 1 millisecond, regular linux clock timestamp is not enough for our use case.
> The pin PPS will generate elapsedRealtime event at 1 sec boundary which is an exact value of the monotonic clock from the kernel PPS driver (/sys/class/pps/pps0/assert_elapsed).
>
> Whenever AP receives this pulse, kernel's pps driver timestamp this elapsedRealtime event and let this time available via sysfs node (/sys/class/pps/pps0/assert_elapsed).
>
> Signed-off-by: alexkom <alexander.komrakov@...adcom.com>
Acked-by: Rodolfo Giometti <giometti@...eenne.com>
--
GNU/Linux Solutions e-mail: giometti@...eenne.com
Linux Device Driver giometti@...ux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Powered by blists - more mailing lists