From: Mahesh Bandewar <maheshb@google.com>
To: Netdev <netdev@vger.kernel.org>,
Linux <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Don Hatchett <hatch@google.com>,
Yuliang Li <yuliangli@google.com>,
Mahesh Bandewar <mahesh@bandewar.net>,
Mahesh Bandewar <maheshb@google.com>
Subject: [PATCH 0/4] add ptp_gettimex64any() API
Date: Thu, 28 Sep 2023 19:37:21 -0700 [thread overview]
Message-ID: <20230929023721.1610484-1-maheshb@google.com> (raw)
The current API to get the sandwich TS for the master-PTP clock read
supports only the sys-time sandwich. This is not really suitable for
all the use cases of sandwich TS needs. Ideally it should
allow a choice of a timebase to use for ts-sandwich need. Updating
the existing API [gettimex64()] is not an option since it would
break compatibility.
About the name - This is a superset of current gettimex64. Since
the timebase for gettimex64 is fixed and is only 'sys-time / real-time'.
I'm appending "any" to add the choice factor. so gettimex64any() would
give you eXtended time with sandwitch TS of a timebase of your choice.
If there is a better name, I won't mind changing.
The timebase options are -
CLOCK_REALTIME, CLOCK_MONOTONIC, CLOCK_MONOTONIC_RAW, & RAW_CYCLES
Since the ioctl() returns 'stuct ptp_clock_time *', the RAW_CYCLES are
converted into sec = 10^9 cycles, nsec = remainder-cycles basically
ns_to_timespec64. Caller can convert the value into raw-cycles
by using calculations similar to timespec64_to_ns()
The CLOCK_REALTIME option is equivalent of using current gettimex64()
method.
The first patch adds the ktime_get_cycles64() method to support
RAW-CYCLES option. The other timebases already have supporting
methods available.
The second patch adds this new PTP method while the third patch adds the
ioctl support for this method.
The last patch in the series updates the selftest to exercise this new
method.
Mahesh Bandewar (4):
time: add ktime_get_cycles64() api
ptp: add ptp_gettimex64any() support
ptp: add ioctl interface for ptp_gettimex64any()
selftes/ptp: extend test to include ptp_gettimex64any()
drivers/ptp/ptp_chardev.c | 34 ++++++++++++
include/linux/ptp_clock_kernel.h | 57 +++++++++++++++++++
include/linux/timekeeping.h | 1 +
include/uapi/linux/ptp_clock.h | 22 ++++++++
kernel/time/timekeeping.c | 24 ++++++++
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/ptp/testptp.c | 79 ++++++++++++++++++++++++++-
7 files changed, 216 insertions(+), 2 deletions(-)
--
2.42.0.582.g8ccd20d70d-goog
reply other threads:[~2023-09-29 2:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230929023721.1610484-1-maheshb@google.com \
--to=maheshb@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hatch@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuliangli@google.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;
as well as URLs for NNTP newsgroup(s).