linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yong, Jonathan" <jonathan.yong@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH v5] PCI: PTM preliminary implementation
Date: Tue, 14 Jun 2016 09:32:28 +0800	[thread overview]
Message-ID: <575F5EAC.2030904@intel.com> (raw)
In-Reply-To: <20160613185648.GA6901@localhost>

On 06/14/2016 02:56, Bjorn Helgaas wrote:
> I'm also a little confused about how Root Complex Integrated Endpoints
> are supposed to use PTM, since they don't have an upstream bridge.
> Maybe it has to do with an RCRB (Root Complex Register Block, spec
> r3.1, sec 7.2.3)?  I don't think Linux really has any support for that
> (yet).

The spec (7.32.3 PTM Control Register) says:

For Root Complex Integrated Endpoints, system software must set this 
field to the value reported in the Local Clock Granularity field by the 
associated PTM Time Source.

I'm not familiar with RC integrated endpoints either. I'm guessing 
whatever device 0, function 0 on the "bus"? Just copy the granularity 
value over?

  reply	other threads:[~2016-06-14  1:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  8:47 [PATCH v5] PCI: PTM Driver Yong, Jonathan
2016-05-11  8:47 ` [PATCH v5] PCI: PTM preliminary implementation Yong, Jonathan
2016-06-12 22:18   ` Bjorn Helgaas
2016-06-13  2:59     ` Yong, Jonathan
2016-06-13 13:45       ` Bjorn Helgaas
2016-06-13 18:56   ` Bjorn Helgaas
2016-06-14  1:32     ` Yong, Jonathan [this message]
2016-06-18 18:15       ` Bjorn Helgaas
2016-05-24  3:59 ` [PATCH v5] PCI: PTM Driver Yong, Jonathan
2016-05-31  0:17   ` Yong, Jonathan
2016-06-09  6:32     ` Yong, Jonathan

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=575F5EAC.2030904@intel.com \
    --to=jonathan.yong@intel.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).