From: Rodolfo Giometti <giometti@enneenne.com>
To: Alexander Komrakov <alexander.komrakov@broadcom.com>,
linux-kernel@vger.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.
Date: Fri, 26 Nov 2021 11:49:25 +0100 [thread overview]
Message-ID: <a2dd9fa7-c6d2-d234-7652-53014672fe0a@enneenne.com> (raw)
In-Reply-To: <20211118032217.244985-2-alexander.komrakov@broadcom.com>
On 18/11/21 04:22, Alexander Komrakov wrote:
> From: alexkom <alexander.komrakov@broadcom.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@broadcom.com>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
next prev parent reply other threads:[~2021-11-26 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 3:22 [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 Alexander Komrakov
2021-11-18 3:22 ` Alexander Komrakov
2021-11-26 10:49 ` Rodolfo Giometti [this message]
2022-02-07 14:08 ` Greg KH
2022-02-07 14:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-01-10 4:22 Alexander Komrakov
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=a2dd9fa7-c6d2-d234-7652-53014672fe0a@enneenne.com \
--to=giometti@enneenne.com \
--cc=alexander.komrakov@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
/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