From: Richard Cochran <richardcochran@gmail.com>
To: Julien Beraud <julien.beraud@orolia.com>
Cc: Olivier Dautricourt <olivier.dautricourt@orolia.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Patch series for a PTP Grandmaster use case using stmmac/gmac3 ptp clock
Date: Tue, 26 May 2020 21:05:51 -0700 [thread overview]
Message-ID: <20200527040551.GB18483@localhost> (raw)
In-Reply-To: <3a14f417-1ae1-9434-5532-4b3387f25d18@orolia.com>
On Fri, May 15, 2020 at 03:26:47PM +0200, Julien Beraud wrote:
> The frequency adjustments of the mac's clock are done by changing the value of
> addend, so that the number of clock cycles that make the accumulator overflow
> slightly change.
This is typical.
> The value of sub-second-increment is set to 2 / ptp_clk_freq, because using an
> accumulator with the same number of bits as the addend register makes it
> impossible to overflow at every addition.
>
> This mode allows to implement a PTP Slave, constantly adjusting the clock's freq
> to match the master.
Right. And I would stick with this. With the ts2phc program
(linuxptp master branch) you can use the EXTTS to discipline the clock
to match the external time source.
> -> In coarse mode, the accumulator and the addend register are not used and the
> value of sub-second-increment is added to the clock at every ptp_ref_clock
> cycle.
That sounds like simply configuring a fixed rate.
> This mode allows to implement a Grand Master where we can feed the stmmac's ptp
> ref clock input with a frequency that's controlled externally, making it
> useless to do frequency adjustments with the MAC.
>
> We want our devices to be able to switch from Master to Slave at runtime.
If I understand correctly, what you are really asking for is the
ability to switch clock sources. This normally done through the
device tree, and changing the device tree at run time is done with
overlays (which I think is still a WIP).
> So the question is what interface could we use to configure a timestamping
> clock that has more than one functioning mode and which mode can be changed at
> runtime, but not while timestamping is running ?
I think this must be decided at boot time using the DTS. In any case,
the PHC time stamping API is not the right place for this. If you end
up making a custom method (via debugfs for example), then your PHC
should then return an error when user space attempts to adjust it.
Thanks,
Richard
next prev parent reply other threads:[~2020-05-27 4:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 10:28 [PATCH 0/3] Patch series for a PTP Grandmaster use case using stmmac/gmac3 ptp clock Olivier Dautricourt
2020-05-14 10:28 ` [PATCH 1/3] net: stmmac: gmac3: add auxiliary snapshot support Olivier Dautricourt
2020-05-14 10:28 ` [PATCH 2/3] net: uapi: Add HWTSTAMP_FLAGS_ADJ_FINE/ADJ_COARSE Olivier Dautricourt
2020-05-14 13:38 ` Richard Cochran
2020-05-14 15:20 ` Olivier Dautricourt
2020-05-15 0:29 ` Richard Cochran
2020-05-14 10:28 ` [PATCH 3/3] net: stmmac: Support coarse mode through ioctl Olivier Dautricourt
2020-05-27 3:55 ` Richard Cochran
2020-06-03 16:12 ` Olivier Dautricourt
2020-05-14 13:53 ` [PATCH 0/3] Patch series for a PTP Grandmaster use case using stmmac/gmac3 ptp clock Richard Cochran
2020-05-14 15:09 ` Olivier Dautricourt
2020-05-15 0:37 ` Richard Cochran
2020-05-15 13:26 ` Julien Beraud
2020-05-15 23:30 ` Richard Cochran
2020-05-25 10:00 ` Olivier Dautricourt
2020-05-27 4:05 ` Richard Cochran [this message]
2020-06-03 15:17 ` Olivier Dautricourt
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=20200527040551.GB18483@localhost \
--to=richardcochran@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=julien.beraud@orolia.com \
--cc=netdev@vger.kernel.org \
--cc=olivier.dautricourt@orolia.com \
--cc=peppe.cavallaro@st.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).