All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	davem@davemloft.net, Matthew Vick <matthew.vick@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
	Stuart Hodgson <smhodgson@solarflare.com>
Subject: Re: [net-next 13/13] igb: Store the MAC address in the name in the PTP struct.
Date: Fri, 24 Aug 2012 08:19:57 +0200	[thread overview]
Message-ID: <20120824061956.GA2212@netboy.at.omicron.at> (raw)
In-Reply-To: <1345757737.2579.22.camel@bwh-desktop.uk.solarflarecom.com>

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

  reply	other threads:[~2012-08-24  6:20 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23  9:56 [net-next 00/13][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2012-08-23  9:56 ` [net-next 01/13] e1000e: use correct type for read of 32-bit register Jeff Kirsher
2012-08-23  9:56 ` [net-next 02/13] e1000e: cleanup strict checkpatch check Jeff Kirsher
2012-08-23  9:56 ` [net-next 03/13] e1000e: cleanup - remove inapplicable comment Jeff Kirsher
2012-08-23  9:56 ` [net-next 04/13] e1000e: cleanup checkpatch PREFER_PR_LEVEL warning Jeff Kirsher
2012-08-23 14:01   ` Joe Perches
2012-08-24 18:02     ` Joe Perches
2012-08-24 21:19       ` Jeff Kirsher
2012-08-24 22:43         ` Joe Perches
2012-08-23  9:56 ` [net-next 05/13] e1000e: cleanup - remove unnecessary variable Jeff Kirsher
2012-08-23  9:56 ` [net-next 06/13] e1000e: update driver version number Jeff Kirsher
2012-08-23  9:56 ` [net-next 07/13] e1000e: cleanup strict checkpatch MEMORY_BARRIER checks Jeff Kirsher
2012-08-23  9:56 ` [net-next 08/13] igb: Add loopback test support for i210 Jeff Kirsher
2012-08-23  9:56 ` [net-next 09/13] igb: reduce Rx header size Jeff Kirsher
2012-08-23  9:56 ` [net-next 10/13] igb: Tidy up wrapping for CONFIG_IGB_PTP Jeff Kirsher
2012-08-23 11:03   ` Richard Cochran
2012-08-23 16:09     ` Vick, Matthew
2012-08-23 17:29       ` Richard Cochran
2012-08-23 17:40         ` Vick, Matthew
2012-08-23 18:03           ` Richard Cochran
2012-08-23 18:03         ` Keller, Jacob E
2012-08-23 18:40           ` Vick, Matthew
2012-08-24  7:04             ` Richard Cochran
2012-08-24 10:10             ` Richard Cochran
2012-08-24 16:51               ` Ben Hutchings
2012-08-24 19:38                 ` Keller, Jacob E
2012-08-25  6:20                   ` Richard Cochran
2012-08-26  1:33                     ` Keller, Jacob E
2012-08-26 13:01                       ` Richard Cochran
2012-08-23 11:28   ` Richard Cochran
2012-08-23 16:27     ` Vick, Matthew
2012-08-23  9:56 ` [net-next 11/13] igb: Update PTP function names/variables and locations Jeff Kirsher
2012-08-23 11:16   ` Richard Cochran
2012-08-23 16:22     ` Vick, Matthew
2012-08-23 17:53       ` Richard Cochran
2012-08-23 18:00         ` Keller, Jacob E
2012-08-23 18:11           ` Richard Cochran
2012-08-23 18:44             ` Vick, Matthew
2012-08-24  6:55               ` Richard Cochran
2012-08-24 15:52                 ` Vick, Matthew
2012-08-25  5:48                   ` Richard Cochran
2012-08-27 15:23                     ` Vick, Matthew
2012-08-27 16:44                       ` Richard Cochran
2012-08-27 17:39                         ` Vick, Matthew
2012-08-23 18:35         ` Vick, Matthew
2012-08-23 18:48           ` Keller, Jacob E
2012-08-23 18:58             ` Vick, Matthew
2012-08-24  3:02         ` Joe Perches
2012-08-24  6:32           ` Richard Cochran
2012-08-24  9:22             ` Joe Perches
2012-08-24 15:12               ` David Miller
2012-08-24 17:56                 ` Joe Perches
2012-08-23  9:56 ` [net-next 12/13] igb: Correct PTP support query from ethtool Jeff Kirsher
2012-08-23 11:24   ` Richard Cochran
2012-08-23 16:38     ` Vick, Matthew
2012-08-23  9:56 ` [net-next 13/13] igb: Store the MAC address in the name in the PTP struct Jeff Kirsher
2012-08-23 10:45   ` Richard Cochran
2012-08-23 16:05     ` Vick, Matthew
2012-08-23 21:35     ` Ben Hutchings
2012-08-24  6:19       ` Richard Cochran [this message]
2012-09-06 23:04         ` Keller, Jacob E

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=20120824061956.GA2212@netboy.at.omicron.at \
    --to=richardcochran@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=matthew.vick@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    --cc=smhodgson@solarflare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.