From: Richard Cochran <richardcochran@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Sørensen, Stefan" <Stefan.Sorensen@spectralink.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mugunthanvnm@ti.com" <mugunthanvnm@ti.com>
Subject: Re: [PATCH] net:cpsw: Pass unhandled ioctl's on to generic phy ioctl
Date: Wed, 5 Feb 2014 08:12:51 +0100 [thread overview]
Message-ID: <20140205071250.GA4071@netboy> (raw)
In-Reply-To: <1391550719.3003.33.camel@deadeye.wl.decadent.org.uk>
On Tue, Feb 04, 2014 at 09:51:59PM +0000, Ben Hutchings wrote:
>
> Right. If all versions of CPSW include hardware timestamping then
> bother with PHY timestamping at all? And why make CONFIG_TI_CPTS
> configurable?
On the one hand, PHY time stamping is more accurate and offers
synchronization performance that is measurably better than MAC time
stamping. On the other hand, when using a MAC the CPU usually has much
more direct access to the clock (for example, direct register access
or PCIe, versus MDIO).
I once worked on a project in which it was planned to have both kinds
of hardware in the design, in order to keep our options open in the
face of fluid requirements. So I think you can expect to see such
combinations in the wild, especially in the embedded area.
We cannot reasonably support both types in the kernel at the same
time, and so it makes sense to have compile time options in MAC
drivers to disable time stamping.
Thanks,
Richard
next prev parent reply other threads:[~2014-02-05 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 7:50 [PATCH] net:cpsw: Pass unhandled ioctl's on to generic phy ioctl Stefan Sørensen
2014-02-04 10:50 ` Ben Hutchings
2014-02-04 15:08 ` Sørensen, Stefan
2014-02-04 21:51 ` Ben Hutchings
2014-02-05 7:12 ` Richard Cochran [this message]
2014-02-05 10:23 ` Ben Hutchings
2014-02-05 11:06 ` Christian Riesch
2014-02-05 11:26 ` Richard Cochran
2014-02-05 7:28 ` Sørensen, Stefan
2014-02-05 8:18 ` Mugunthan V N
2014-02-05 10:49 ` Christian Riesch
2014-02-05 14:15 ` Mugunthan V N
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=20140205071250.GA4071@netboy \
--to=richardcochran@gmail.com \
--cc=Stefan.Sorensen@spectralink.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.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).