From: David Miller <davem@davemloft.net>
To: olteanv@gmail.com
Cc: kuba@kernel.org, netdev@vger.kernel.org,
richardcochran@gmail.com, jacob.e.keller@intel.com,
yangbo.lu@nxp.com, xiaoliang.yang_1@nxp.com, po.liu@nxp.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v2 net-next 0/3] Fully describe the waveform for PTP periodic output
Date: Sun, 19 Jul 2020 19:24:01 -0700 (PDT) [thread overview]
Message-ID: <20200719.192401.1110272100468125745.davem@davemloft.net> (raw)
In-Reply-To: <20200716224531.1040140-1-olteanv@gmail.com>
From: Vladimir Oltean <olteanv@gmail.com>
Date: Fri, 17 Jul 2020 01:45:28 +0300
> While using the ancillary pin functionality of PTP hardware clocks to
> synchronize multiple DSA switches on a board, a need arised to be able
> to configure the duty cycle of the master of this PPS hierarchy.
>
> Also, the PPS master is not able to emit PPS starting from arbitrary
> absolute times, so a new flag is introduced to support such hardware
> without making guesses.
>
> With these patches, struct ptp_perout_request now basically describes a
> general-purpose square wave.
>
> Changes in v2:
> Made sure this applies to net-next.
Series applied, thank you.
next prev parent reply other threads:[~2020-07-20 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 22:45 [PATCH v2 net-next 0/3] Fully describe the waveform for PTP periodic output Vladimir Oltean
2020-07-16 22:45 ` [PATCH v2 net-next 1/3] ptp: add ability to configure duty cycle for " Vladimir Oltean
2020-07-16 22:45 ` [PATCH v2 net-next 2/3] ptp: introduce a phase offset in the periodic output request Vladimir Oltean
2020-07-16 22:45 ` [PATCH v2 net-next 3/3] net: mscc: ocelot: add support for PTP waveform configuration Vladimir Oltean
2020-07-17 13:43 ` Horatiu Vultur
2020-07-20 2:24 ` David Miller [this message]
2020-07-20 14:11 ` [PATCH v2 net-next 0/3] Fully describe the waveform for PTP periodic output Richard Cochran
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=20200719.192401.1110272100468125745.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=po.liu@nxp.com \
--cc=richardcochran@gmail.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yangbo.lu@nxp.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).