From: Richard Cochran <richardcochran@gmail.com>
To: Min Li <lnimi@hotmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Min Li <min.li.xe@renesas.com>
Subject: Re: [PATCH net-next RFC 1/1] ptp: use extts interface for the measured external offset
Date: Mon, 13 Nov 2023 20:14:12 -0800 [thread overview]
Message-ID: <ZVL0FDZ4Dn4qo7hn@hoboy.vegasvil.org> (raw)
In-Reply-To: <MW5PR03MB6932F6DB45F5ED179DF0BA4DA0B3A@MW5PR03MB6932.namprd03.prod.outlook.com>
On Mon, Nov 13, 2023 at 04:50:25PM -0500, Min Li wrote:
> From: Min Li <min.li.xe@renesas.com>
>
> This change is for the PHC devices that can measure the
> phase offset between PHC signal and the external signal, such
> as GNSS. With this change, ts2phc can use the existing extts
> interface to retrieve measurement offset so that the alignment
> between PHC and the external signal can be achieved.
>
> Signed-off-by: Min Li <min.li.xe@renesas.com>
> ---
> drivers/ptp/ptp_clock.c | 12 +++++++++---
> include/linux/ptp_clock_kernel.h | 2 ++
> include/uapi/linux/ptp_clock.h | 9 +++++++--
> 3 files changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ptp/ptp_clock.c b/drivers/ptp/ptp_clock.c
> index 3134568af622..c87954c8642f 100644
> --- a/drivers/ptp/ptp_clock.c
> +++ b/drivers/ptp/ptp_clock.c
> @@ -48,14 +48,19 @@ static void enqueue_external_timestamp(struct timestamp_event_queue *queue,
> s64 seconds;
> u32 remainder;
>
> - seconds = div_u64_rem(src->timestamp, 1000000000, &remainder);
> + if(src->type != PTP_CLOCK_EXTOFF)
Space after 'if' keyword please.
> + seconds = div_u64_rem(src->timestamp, 1000000000, &remainder);
>
> spin_lock_irqsave(&queue->lock, flags);
>
> dst = &queue->buf[queue->tail];
> dst->index = src->index;
> - dst->t.sec = seconds;
> - dst->t.nsec = remainder;
> + if(src->type != PTP_CLOCK_EXTOFF) {
ditto.
> + dst->t.sec = seconds;
> + dst->t.nsec = remainder;
> + } else {
> + dst->o = src->offset;
> + }
>
> if (!queue_free(queue))
> queue->head = (queue->head + 1) % PTP_MAX_TIMESTAMPS;
> @@ -416,6 +421,7 @@ void ptp_clock_event(struct ptp_clock *ptp, struct ptp_clock_event *event)
> break;
>
> case PTP_CLOCK_EXTTS:
> + case PTP_CLOCK_EXTOFF:
> /* Enqueue timestamp on selected queues */
> spin_lock_irqsave(&ptp->tsevqs_lock, flags);
> list_for_each_entry(tsevq, &ptp->tsevqs, qlist) {
> diff --git a/include/linux/ptp_clock_kernel.h b/include/linux/ptp_clock_kernel.h
> index 1ef4e0f9bd2a..7f2d1e1cc185 100644
> --- a/include/linux/ptp_clock_kernel.h
> +++ b/include/linux/ptp_clock_kernel.h
> @@ -200,6 +200,7 @@ struct ptp_clock;
> enum ptp_clock_events {
> PTP_CLOCK_ALARM,
> PTP_CLOCK_EXTTS,
> + PTP_CLOCK_EXTOFF,
> PTP_CLOCK_PPS,
> PTP_CLOCK_PPSUSR,
> };
> @@ -218,6 +219,7 @@ struct ptp_clock_event {
> int index;
> union {
> u64 timestamp;
> + s64 offset;
> struct pps_event_time pps_times;
> };
> };
> diff --git a/include/uapi/linux/ptp_clock.h b/include/uapi/linux/ptp_clock.h
> index da700999cad4..61e0473cdf53 100644
> --- a/include/uapi/linux/ptp_clock.h
> +++ b/include/uapi/linux/ptp_clock.h
> @@ -32,6 +32,7 @@
> #define PTP_RISING_EDGE (1<<1)
> #define PTP_FALLING_EDGE (1<<2)
> #define PTP_STRICT_FLAGS (1<<3)
> +#define PTP_EXT_OFFSET (1<<4)
> #define PTP_EXTTS_EDGES (PTP_RISING_EDGE | PTP_FALLING_EDGE)
>
> /*
> @@ -40,7 +41,8 @@
> #define PTP_EXTTS_VALID_FLAGS (PTP_ENABLE_FEATURE | \
> PTP_RISING_EDGE | \
> PTP_FALLING_EDGE | \
> - PTP_STRICT_FLAGS)
> + PTP_STRICT_FLAGS | \
> + PTP_EXT_OFFSET)
>
> /*
> * flag fields valid for the original PTP_EXTTS_REQUEST ioctl.
> @@ -228,7 +230,10 @@ struct ptp_pin_desc {
> #define PTP_MASK_EN_SINGLE _IOW(PTP_CLK_MAGIC, 20, unsigned int)
>
> struct ptp_extts_event {
> - struct ptp_clock_time t; /* Time event occured. */
> + union {
> + struct ptp_clock_time t; /* Time event occured. */
> + __s64 o; /* measured offset */
How about calling it offset_ns so that the unit is clear?
> + };
> unsigned int index; /* Which channel produced the event. */
> unsigned int flags; /* Reserved for future use. */
> unsigned int rsv[2]; /* Reserved for future use. */
> --
> 2.39.2
>
prev parent reply other threads:[~2023-11-14 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 21:50 [PATCH net-next RFC 1/1] ptp: use extts interface for the measured external offset Min Li
2023-11-13 23:00 ` Jacob Keller
2023-11-14 4:15 ` Richard Cochran
2023-11-14 16:39 ` Min Li
2023-11-14 4:14 ` Richard Cochran [this message]
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=ZVL0FDZ4Dn4qo7hn@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lnimi@hotmail.com \
--cc=min.li.xe@renesas.com \
--cc=netdev@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