linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Jonathan Yong <jonathan.yong@intel.com>
Cc: linux-pci@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/3] PCI: Precision Time Measurement support
Date: Mon, 13 Jun 2016 14:05:26 -0500	[thread overview]
Message-ID: <20160613185945.12503.32760.stgit@bhelgaas-glaptop2.roam.corp.google.com> (raw)

This is a slightly different proposal for the PTM support Jonathan
proposed here:

  http://lkml.kernel.org/r/1462956446-27361-2-git-send-email-jonathan.yong@intel.com

I split this into three pieces mostly for ease in reviewing.  They
could all be squashed:

  - Enable PTM in root ports and switches automatically at boot
  - Enable PTM in endpoints when requested by driver
  - Add clock granularity information

I have some open questions about how PTM works on Root Complex
Integrated Endpoints and whether we should enable it automatically
even without a driver request.  And I probably left out some details
of the clock granularity computation, so treat this as more of an RFC
than anything.

Bjorn

---

Bjorn Helgaas (2):
      PCI: Add pci_enable_ptm() for drivers to enable PTM on endpoints
      PCI: Add PTM clock granularity information

Jonathan Yong (1):
      PCI: Add Precision Time Measurement (PTM) support


 drivers/pci/pci.h             |    6 ++
 drivers/pci/pcie/Kconfig      |   12 ++++
 drivers/pci/pcie/Makefile     |    1 
 drivers/pci/pcie/ptm.c        |  140 +++++++++++++++++++++++++++++++++++++++++
 drivers/pci/probe.c           |    3 +
 include/linux/pci.h           |   13 ++++
 include/uapi/linux/pci_regs.h |   12 +++-
 7 files changed, 186 insertions(+), 1 deletion(-)
 create mode 100644 drivers/pci/pcie/ptm.c

             reply	other threads:[~2016-06-13 19:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 19:05 Bjorn Helgaas [this message]
2016-06-13 19:05 ` [PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support Bjorn Helgaas
2016-08-10  2:58   ` Yong, Jonathan
2016-08-15 18:59     ` Bjorn Helgaas
2016-08-16  8:04       ` Yong, Jonathan
2016-08-16 13:37         ` Bjorn Helgaas
2016-08-17  8:51           ` Yong, Jonathan
2016-08-22 17:01           ` Bjorn Helgaas
2016-08-23  0:13             ` Yong, Jonathan
2016-06-13 19:05 ` [PATCH v6 2/3] PCI: Add pci_enable_ptm() for drivers to enable PTM on endpoints Bjorn Helgaas
2016-06-13 19:05 ` [PATCH v6 3/3] PCI: Add PTM clock granularity information Bjorn Helgaas
2016-06-13 19:42   ` kbuild test robot
2016-07-19 21:19 ` [PATCH v6 0/3] PCI: Precision Time Measurement support Bjorn Helgaas
2016-07-19 23:49   ` Yong, Jonathan
2016-08-15 18:51     ` Bjorn Helgaas
2016-08-16  1:27       ` Yong, Jonathan
2016-08-23 21:42 ` Bjorn Helgaas
2016-08-24  1:09   ` 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=20160613185945.12503.32760.stgit@bhelgaas-glaptop2.roam.corp.google.com \
    --to=bhelgaas@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jonathan.yong@intel.com \
    --cc=linux-kernel@vger.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).