netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Eugenia Emantayev <eugenia@mellanox.com>
Cc: Yevgeny Petrilin <yevgenyp@mellanox.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH 3/3] net/mlx4_en: Add HW timestamping (TS) support
Date: Thu, 4 Oct 2012 16:27:35 +0200	[thread overview]
Message-ID: <20121004142734.GA2810@netboy.at.omicron.at> (raw)
In-Reply-To: <74A0102445410646AFACC089FD94803A95ED92DD@MTLDAG01.mtl.com>

On Thu, Oct 04, 2012 at 02:08:29PM +0000, Eugenia Emantayev wrote:
> > Also, why not expose your device as a PTP Hardware Clock?
> 
> Hello Richard,
> Could you please clarify the above?
> What do you mean by expose your device as a PTP Hardware Clock?

You could register the driver as PHC class device, described in

   Documentation/ptp/ptp.txt

and then you device will work together along with a user space PTP
stack, like the one I wrote at

   http://linuxptp.sourceforge.net

Thanks,
Richard

  reply	other threads:[~2012-10-04 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 10:03 [PATCH 0/3] net/mlx4: HW Timestamp support Yevgeny Petrilin
2012-09-28 10:03 ` [PATCH 1/3] net/mlx4_core: Add timestamping device capability Yevgeny Petrilin
2012-09-28 10:03 ` [PATCH 2/3] net/mlx4_core: Read HCA frequency and map internal clock Yevgeny Petrilin
2012-09-28 10:03 ` [PATCH 3/3] net/mlx4_en: Add HW timestamping (TS) support Yevgeny Petrilin
2012-09-28 11:11   ` Richard Cochran
2012-09-28 14:10     ` Yevgeny Petrilin
2012-10-04 14:08     ` Eugenia Emantayev
2012-10-04 14:27       ` Richard Cochran [this message]
2012-10-04 20:58         ` Eugenia Emantayev
2012-10-05 10:38           ` Richard Cochran
2012-10-01 15:08   ` Ben Hutchings
2012-10-02  7:32     ` Yevgeny Petrilin

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=20121004142734.GA2810@netboy.at.omicron.at \
    --to=richardcochran@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eugenia@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=yevgenyp@mellanox.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).