From: Richard Cochran <richardcochran@gmail.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
jacob.e.keller@intel.com, yangbo.lu@nxp.com,
xiaoliang.yang_1@nxp.com, po.liu@nxp.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next 2/2] testptp: add new options for perout phase and pulse width
Date: Mon, 20 Jul 2020 17:29:22 -0700 [thread overview]
Message-ID: <20200721002922.GD21585@hoboy> (raw)
In-Reply-To: <20200720175559.1234818-3-olteanv@gmail.com>
On Mon, Jul 20, 2020 at 08:55:59PM +0300, Vladimir Oltean wrote:
> Extend the example program for PTP ancillary functionality with the
> ability to configure not only the periodic output's period (frequency),
> but also the phase and duty cycle (pulse width) which were newly
> introduced.
>
> The ioctl level also needs to be updated to the new PTP_PEROUT_REQUEST2,
> since the original PTP_PEROUT_REQUEST doesn't support this
> functionality. For an in-tree testing program, not having explicit
> backwards compatibility is fine, as it should always be tested with the
> current kernel headers and sources.
>
> Tested with an oscilloscope on the felix switch PHC:
>
> echo '2 0' > /sys/class/ptp/ptp1/pins/switch_1588_dat0
> ./testptp -d /dev/ptp1 -p 1000000000 -w 100000000 -H 1000 -i 0
>
> Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
Thanks for following up with this!
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2020-07-21 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:55 [PATCH net-next 0/2] Extend testptp with PTP perout waveform Vladimir Oltean
2020-07-20 17:55 ` [PATCH net-next 1/2] testptp: promote 'perout' variable to int64_t Vladimir Oltean
2020-07-21 0:27 ` Richard Cochran
2020-07-20 17:55 ` [PATCH net-next 2/2] testptp: add new options for perout phase and pulse width Vladimir Oltean
2020-07-21 0:29 ` Richard Cochran [this message]
2020-07-21 1:05 ` [PATCH net-next 0/2] Extend testptp with PTP perout waveform 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=20200721002922.GD21585@hoboy \
--to=richardcochran@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--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=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).