public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Komrakov <alexander.komrakov@broadcom.com>
Cc: linux-kernel@vger.kernel.org, giometti@enneenne.com
Subject: Re: [PATCH v5] [PATCH v5] pps: Add elapsed realtime timestamping
Date: Thu, 30 Mar 2023 09:32:02 +0200	[thread overview]
Message-ID: <ZCU68tMu10hhsHgB@kroah.com> (raw)
In-Reply-To: <20230330072013.393245-1-alexander.komrakov@broadcom.com>

On Thu, Mar 30, 2023 at 12:20:13AM -0700, Alexander Komrakov wrote:
> Some applications like Android needs elapsed realtime timestamping
> to PPS pulse for its clock management. Add sysfs node for this.

Where is the Android code that needs this?  Have a pointer to it
anywhere?

> 
> Signed-off-by: Alexander Komrakov <alexander.komrakov@broadcom.com>
> ---
>  Documentation/ABI/testing/sysfs-pps | 27 +++++++++++++++++++++++
>  Documentation/driver-api/pps.rst    | 19 ++++++++++++++++
>  drivers/pps/kapi.c                  | 24 +++++++++++++++++---
>  drivers/pps/sysfs.c                 | 34 +++++++++++++++++++++++++++++
>  include/linux/pps_kernel.h          |  2 ++
>  5 files changed, 103 insertions(+), 3 deletions(-)

My bot will remind you that you dropped the version information off :(

> diff --git a/Documentation/ABI/testing/sysfs-pps b/Documentation/ABI/testing/sysfs-pps
> index 25028c7bc37d..031ec89e1ed6 100644
> --- a/Documentation/ABI/testing/sysfs-pps
> +++ b/Documentation/ABI/testing/sysfs-pps
> @@ -1,3 +1,30 @@
> +What:		/sys/class/pps/pps0/assert_elapsed

That should be "ppsX" right?

> +Date:		October 2021
> +Contact:	Alexander Komrakov <alexander.komrakov@broadcom.com>
> +Description:
> +		The /sys/class/pps/ppsX/assert_elapsed file reports the
> +		elapsed real-time assert events and the elapsed
> +		real-time assert sequence number of the X-th source
> +		in the form:
> +
> +			<secs>.<nsec>#<sequence>
> +
> +		If the source has no elapsed real-time assert events
> +		the content of this file is empty.
> +
> +What:		/sys/class/pps/ppsX/clear_elapsed
> +Date:		October 2021
> +Contact:	Alexander Komrakov <alexander.komrakov@broadcom.com>
> +Description:
> +		The /sys/class/pps/ppsX/clear_elapsed file reports the elapsed
> +		real-time clear events and the elapsed real-time clear
> +		sequence number of the X-th source in the form:
> +
> +			<secs>.<nsec>#<sequence>
> +
> +		If the source has no elapsed real-time clear events the
> +		content of this file is empty.
> +
>  What:		/sys/class/pps/

Why are your new entries above the main pps entry?  Shouldn't they be
below it?

thanks,

greg k-h

  reply	other threads:[~2023-03-30  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:20 [PATCH v5] [PATCH v5] pps: Add elapsed realtime timestamping Alexander Komrakov
2023-03-30  7:32 ` Greg KH [this message]
     [not found]   ` <CAMedr-_xinpsmzWO4G265gU4ofvvmGLBdZJ21LZyrd_X7DjaFQ@mail.gmail.com>
2023-04-11  0:51     ` Alex Komrakov
2023-03-30  7:32 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-03-17  9:51 Alexander Komrakov
2023-03-17 11:43 ` Greg KH

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=ZCU68tMu10hhsHgB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.komrakov@broadcom.com \
    --cc=giometti@enneenne.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