From: Richard Cochran <richardcochran@gmail.com>
To: Luwei Zhou <b45643@freescale.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
shawn.guo@linaro.org, bhutchings@solarflare.com,
R49496@freescale.com, b38611@freescale.com, b20596@freescale.com,
stephen@networkplumber.org
Subject: Re: [PATCH v2 3/4] ptp: Add PTP_PF_PPS enumeration to ptp_pin_function.
Date: Mon, 29 Sep 2014 10:56:14 +0200 [thread overview]
Message-ID: <20140929085613.GA9891@netboy> (raw)
In-Reply-To: <1411878011-21767-4-git-send-email-b45643@freescale.com>
On Sun, Sep 28, 2014 at 12:20:10PM +0800, Luwei Zhou wrote:
> diff --git a/include/linux/ptp_clock_kernel.h b/include/linux/ptp_clock_kernel.h
> index 0d8ff3f..2a5ad1c 100644
> --- a/include/linux/ptp_clock_kernel.h
> +++ b/include/linux/ptp_clock_kernel.h
> @@ -49,6 +49,7 @@ struct ptp_clock_request {
> * @n_alarm: The number of programmable alarms.
> * @n_ext_ts: The number of external time stamp channels.
> * @n_per_out: The number of programmable periodic signals.
> + * @n_pps_chan: The number of programmable channles for pps output.
> * @n_pins: The number of programmable pins.
> * @pps: Indicates whether the clock supports a PPS callback.
> * @pin_config: Array of length 'n_pins'. If the number of
> @@ -99,6 +100,7 @@ struct ptp_clock_info {
> int n_alarm;
> int n_ext_ts;
> int n_per_out;
> + int n_pps_chan;
We don't need this. There is only *one* PPS channel.
We only want to select which of 'n_pins' will be the PPS output.
> int n_pins;
> int pps;
> struct ptp_pin_desc *pin_config;
> diff --git a/include/uapi/linux/ptp_clock.h b/include/uapi/linux/ptp_clock.h
> index f0b7bfe..57ba7e7 100644
> --- a/include/uapi/linux/ptp_clock.h
> +++ b/include/uapi/linux/ptp_clock.h
> @@ -86,6 +86,7 @@ enum ptp_pin_function {
> PTP_PF_EXTTS,
> PTP_PF_PEROUT,
> PTP_PF_PHYSYNC,
> + PTP_PF_PPS,
> };
>
> struct ptp_pin_desc {
> --
> 1.9.1
>
Thanks,
Richard
next prev parent reply other threads:[~2014-09-29 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 4:20 [PATCH v2 0/4] net: fec: ptp: Add FEC PPS ouput support Luwei Zhou
2014-09-28 4:20 ` [PATCH v2 1/4] net: fec: ptp: Use the 31-bit ptp timer Luwei Zhou
2014-09-28 4:20 ` [PATCH v2 2/4] net: fec: ptp: Use hardware algorithm to adjust PTP counter Luwei Zhou
2014-09-29 2:13 ` fugang.duan
2014-09-28 4:20 ` [PATCH v2 3/4] ptp: Add PTP_PF_PPS enumeration to ptp_pin_function Luwei Zhou
2014-09-29 8:56 ` Richard Cochran [this message]
2014-09-29 9:38 ` luwei.zhou
2014-09-29 13:25 ` Richard Cochran
2014-09-28 4:20 ` [PATCH v2 4/4] net: fec: ptp: Enalbe PPS ouput based on ptp clock Luwei Zhou
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=20140929085613.GA9891@netboy \
--to=richardcochran@gmail.com \
--cc=R49496@freescale.com \
--cc=b20596@freescale.com \
--cc=b38611@freescale.com \
--cc=b45643@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stephen@networkplumber.org \
/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).