All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linux-net-drivers <linux-net-drivers@solarflare.com>,
	netdev <netdev@vger.kernel.org>,
	Laurence Evans <levans@solarflare.com>
Subject: Re: PHC device sharing between PCI functions
Date: Thu, 4 Jul 2013 07:36:05 +0200	[thread overview]
Message-ID: <20130704053605.GC4457@netboy> (raw)
In-Reply-To: <1372881153.1919.49.camel@bwh-desktop.uk.level5networks.com>

On Wed, Jul 03, 2013 at 08:52:33PM +0100, Ben Hutchings wrote:
> 
> So you think each function should have its own clock device, but it's
> only writable on one?  I think that would work, but I thought it would
> be undesirable to have multiple aliases for the same physical clock.

The aliases would not bother me, as long as the ethtool interface-to-phc
association works properly. Of course, if there is a way to suppress
the aliases in the non-VM case, that would be ideal.

Thanks,
Richard

  reply	other threads:[~2013-07-04  5:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 16:56 PHC device sharing between PCI functions Ben Hutchings
2013-07-02 14:24 ` Richard Cochran
2013-07-02 15:17   ` Ben Hutchings
2013-07-03 18:30     ` Richard Cochran
2013-07-03 19:52       ` Ben Hutchings
2013-07-04  5:36         ` Richard Cochran [this message]
2013-07-04 14:34           ` Ben Hutchings
2013-07-04 15:53             ` Richard Cochran
2013-07-04 16:21               ` Ben Hutchings
2013-07-04 17:39                 ` Richard Cochran
2013-07-04 18:19                   ` Ben Hutchings
2013-07-05  5:25                     ` Richard Cochran

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=20130704053605.GC4457@netboy \
    --to=richardcochran@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=levans@solarflare.com \
    --cc=linux-net-drivers@solarflare.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 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.