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 v3 0/3] Enable FEC pps feather
Date: Fri, 10 Oct 2014 09:44:31 +0200 [thread overview]
Message-ID: <20141010074431.GA4181@localhost.localdomain> (raw)
In-Reply-To: <1412918130-18830-1-git-send-email-b45643@freescale.com>
On Fri, Oct 10, 2014 at 01:15:27PM +0800, Luwei Zhou wrote:
> Change from v2 to v3:
> -Using the default channel 0 to be PPS channel not PTP_PIN_SET/GETFUNC interface.
> -Using the linux definition of NSEC_PER_SEC.
>
> Change from v1 to v2:
> - Fix the potential 32-bit multiplication overflow issue.
> - Optimize the hareware adjustment code to improve efficiency as Richard suggested
> - Use ptp PTP_PIN_SET/GETFUNC interface to set PPS channel not device tree
> and add PTP_PF_PPS enumeration
> - Modify comments style
>
>
> Luwei Zhou (3):
> net: fec: ptp: Use the 31-bit ptp timer.
> net: fec: ptp: Use hardware algorithm to adjust PTP counter.
> net: fec: ptp: Enable PPS output based on ptp clock
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2014-10-10 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 5:15 [PATCH v3 0/3] Enable FEC pps feather Luwei Zhou
2014-10-10 5:15 ` [PATCH v3 1/3] net: fec: ptp: Use the 31-bit ptp timer Luwei Zhou
2014-10-10 5:15 ` [PATCH v3 2/3] net: fec: ptp: Use hardware algorithm to adjust PTP counter Luwei Zhou
2014-10-10 5:15 ` [PATCH v3 3/3] net: fec: ptp: Enable PPS output based on ptp clock Luwei Zhou
2014-10-10 7:44 ` Richard Cochran [this message]
2014-10-14 18:45 ` [PATCH v3 0/3] Enable FEC pps feather Richard Cochran
2014-10-14 18:45 ` 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=20141010074431.GA4181@localhost.localdomain \
--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).