[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <95DC1AA8EC908B48939B72CF375AA5E3054AB528F1@alice.at.omicron.at>
Date: Fri, 7 Feb 2014 08:44:38 +0100
From: Manfred Rudigier <manfred.rudigier@...cron.at>
To: Richard Cochran <richardcochran@...il.com>,
Sørensen, Stefan
<Stefan.Sorensen@...ctralink.com>
CC: "ben@...adent.org.uk" <ben@...adent.org.uk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH] dp83640: Support a configurable number of periodic
outputs
>From: netdev-owner@...r.kernel.org [mailto:netdev-
>owner@...r.kernel.org] On Behalf Of Richard Cochran
>Sent: Friday, February 07, 2014 6:49 AM
>To: Sørensen, Stefan
>Cc: ben@...adent.org.uk; netdev@...r.kernel.org
>Subject: Re: [PATCH] dp83640: Support a configurable number of periodic
>outputs
>
>On Wed, Feb 05, 2014 at 07:40:17AM +0000, Sørensen, Stefan wrote:
>>
>> Will all PTP clocks be associated with an ethernet device? If not,
>> wouldn't a PTP ioctl be better than ethtool?
>
>Hm, maybe. I don't have a strong preference. I'll try and put together an idea
>of how the ioctl might look like.
At least on the Freescale P2020 CPU there is just one PTP clock for 3
Ethernet devices. But since the PTP registers are shared between all three
Ethernet ports, an ethtool approach would still work, but seems somehow strange
for me.
Regards,
Manfred
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists