[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120824061956.GA2212@netboy.at.omicron.at>
Date: Fri, 24 Aug 2012 08:19:57 +0200
From: Richard Cochran <richardcochran@...il.com>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@...el.com>, davem@...emloft.net,
Matthew Vick <matthew.vick@...el.com>, netdev@...r.kernel.org,
gospo@...hat.com, sassmann@...hat.com,
Stuart Hodgson <smhodgson@...arflare.com>
Subject: Re: [net-next 13/13] igb: Store the MAC address in the name in the
PTP struct.
On Thu, Aug 23, 2012 at 10:35:37PM +0100, Ben Hutchings wrote:
>
> The name field is described as 'A short name to identify the clock'. It
> is not stated whether this is meant to be the name of the clock *device*
> or the clock *driver*. If it's the name of the device then some unique
> ID such as the permanent MAC address is required.
In an ideal world, there is only one clock device per system, so the
original concept was to use the driver name. The hardware designers
have ignored or not understood the "one clock per system" model, and
so, unfortunately, we have to deal with it.
A clock device can and should be connected to more than one network
device (see gianfar, dp83640), and to give it a MAC address is
misleading.
The ethtool solution works perfectly to go from interface->clock,
which is all the information that a user space PTP stack needs.
I think for sysfs and the ioctl it is nicer to have the driver name,
since it is associated with the clock and its capabilities.
Thanks,
Richard
--
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