[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200719.192401.1110272100468125745.davem@davemloft.net>
Date: Sun, 19 Jul 2020 19:24:01 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: olteanv@...il.com
Cc: kuba@...nel.org, netdev@...r.kernel.org, richardcochran@...il.com,
jacob.e.keller@...el.com, yangbo.lu@....com,
xiaoliang.yang_1@....com, po.liu@....com,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH v2 net-next 0/3] Fully describe the waveform for PTP
periodic output
From: Vladimir Oltean <olteanv@...il.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.
Powered by blists - more mailing lists