netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
	jakub.kicinski@netronome.com, davem@davemloft.net,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Unlock new potential in SJA1105 with PTP system timestamping
Date: Sat, 9 Nov 2019 07:19:42 -0800	[thread overview]
Message-ID: <20191109151942.GA1537@localhost> (raw)
In-Reply-To: <20191109113224.6495-1-olteanv@gmail.com>

On Sat, Nov 09, 2019 at 01:32:21PM +0200, Vladimir Oltean wrote:
> The SJA1105 being an automotive switch means it is designed to live in a
> set-and-forget environment, far from the configure-at-runtime nature of
> Linux. Frequently resetting the switch to change its static config means
> it loses track of its PTP time, which is not good.
> 
> This patch series implements PTP system timestamping for this switch
> (using the API introduced for SPI here:
> https://www.mail-archive.com/netdev@vger.kernel.org/msg316725.html),
> adding the following benefits to the driver:
> - When under control of a user space PTP servo loop (ptp4l, phc2sys),
>   the loss of sync during a switch reset is much more manageable, and
>   the switch still remains in the s2 (locked servo) state.
> - When synchronizing the switch using the software technique (based on
>   reading clock A and writing the value to clock B, as opposed to
>   relying on hardware timestamping), e.g. by using phc2sys, the sync
>   accuracy is vastly improved due to the fact that the actual switch PTP
>   time can now be more precisely correlated with something of better
>   precision (CLOCK_REALTIME). The issue is that SPI transfers are
>   inherently bad for measuring time with low jitter, but the newly
>   introduced API aims to alleviate that issue somewhat.
> 
> This series is also a requirement for a future patch set that adds full
> time-aware scheduling offload support for the switch.
> 
> Vladimir Oltean (3):
>   net: dsa: sja1105: Implement the .gettimex64 system call for PTP
>   net: dsa: sja1105: Restore PTP time after switch reset
>   net: dsa: sja1105: Disallow management xmit during switch reset

For the series:

Acked-by: Richard Cochran <richardcochran@gmail.com>

  parent reply	other threads:[~2019-11-09 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 11:32 [PATCH net-next 0/3] Unlock new potential in SJA1105 with PTP system timestamping Vladimir Oltean
2019-11-09 11:32 ` [PATCH net-next 1/3] net: dsa: sja1105: Implement the .gettimex64 system call for PTP Vladimir Oltean
2019-11-09 11:32 ` [PATCH net-next 2/3] net: dsa: sja1105: Restore PTP time after switch reset Vladimir Oltean
2019-11-09 11:32 ` [PATCH net-next 3/3] net: dsa: sja1105: Disallow management xmit during " Vladimir Oltean
2019-11-09 15:19 ` Richard Cochran [this message]
2019-11-11 13:19   ` [PATCH net-next 0/3] Unlock new potential in SJA1105 with PTP system timestamping Vladimir Oltean
2019-11-11 20:25     ` David Miller
2019-11-11 20:45 ` David Miller

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=20191109151942.GA1537@localhost \
    --to=richardcochran@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vivien.didelot@gmail.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).