[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1391585274.7871.19.camel@e37108.spectralink.com>
Date: Wed, 5 Feb 2014 07:28:02 +0000
From: Sørensen, Stefan
<Stefan.Sorensen@...ctralink.com>
To: "ben@...adent.org.uk" <ben@...adent.org.uk>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mugunthanvnm@...com" <mugunthanvnm@...com>
Subject: Re: [PATCH] net:cpsw: Pass unhandled ioctl's on to generic phy ioctl
On Tue, 2014-02-04 at 21:51 +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?
The CPSW only supports timestamping which is only one part of the PTP
functionality. Some PHYs (like the dp83630 that we use with the CPSW)
also has external event generation and detection.
Stefan
Powered by blists - more mailing lists