From: "Yong, Jonathan" <jonathan.yong@intel.com>
To: Martin Mares <mj@ucw.cz>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH] lspci: Decode Precision Time Measurement capabiltity
Date: Tue, 17 May 2016 13:53:02 +0800 [thread overview]
Message-ID: <573AB1BE.6070809@intel.com> (raw)
In-Reply-To: <mj+md-20160514.092404.57632.camelot@ucw.cz>
On 05/14/2016 17:24, Martin Mares wrote:
> Hello!
>
>> Section 7.32 Precision Time Management (or Measurement) from the
>> PCI Express Base 3.1 specification is an optional Extended Capability
>> for discovering and controlling the distribution of a PTM Hierarchy.
>
> Thanks, applied.
>
> Could you please provide a test case, similar to those in tests/* ?
>
> Have a nice fortnight
>
Hi,
How do I generate those? Looks like a dump of lspci -vvnnxxxx against a
specific device.
next prev parent reply other threads:[~2016-05-17 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 3:15 [PATCH] lspci: Decode PTM Registers Yong, Jonathan
2016-05-10 3:15 ` [PATCH] lspci: Decode Precision Time Measurement capabiltity Yong, Jonathan
2016-05-14 9:24 ` Martin Mares
2016-05-17 5:53 ` Yong, Jonathan [this message]
2016-05-17 5:53 ` Martin Mares
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=573AB1BE.6070809@intel.com \
--to=jonathan.yong@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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).