From: "Yong, Jonathan" <jonathan.yong@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, "Yong,
Jonathan" <jonathan.yong@intel.com>
Subject: Re: [PATCH] PCI: PTM preliminary implementation
Date: Mon, 14 Mar 2016 15:44:51 +0800 [thread overview]
Message-ID: <56E66BF3.4080500@intel.com> (raw)
In-Reply-To: <20160311155332.GA31716@localhost>
On 03/11/2016 23:53, Bjorn Helgaas wrote:
> I haven't read the PTM spec yet so I don't know how it works. But in
> general, I don't like having to tweak a setting all the way up the
> hierarchy based on a leaf device. That makes it hard to handle
> hotplug correctly, because obviously there may be many leaf devices
> that share part of all of the upstream path.
>
This part in 6.22.3 in the PCIe 3.1 spec:
Software must not have the PTM Enable bit Set in the PTM Control
register on a Function associated with an Upstream Port unless the
associated Downstream Port on the Link already has the PTM Enable bit
Set in its associated PTM Control register.
Seems to suggest starting from the leaf device, I'm open to suggestions
on how to better do this.
next prev parent reply other threads:[~2016-03-14 7:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 7:26 [RFC] PCI: PTM Driver Yong, Jonathan
2016-03-11 7:26 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-03-11 15:53 ` Bjorn Helgaas
2016-03-14 7:44 ` Yong, Jonathan [this message]
2016-03-14 15:42 ` Bjorn Helgaas
2016-03-15 8:27 ` Yong, Jonathan
2016-03-15 13:36 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2016-03-23 2:47 [RFC v2] PCI: PTM Driver Yong, Jonathan
2016-03-23 2:47 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-03-23 3:11 ` kbuild test robot
2016-03-23 3:57 ` kbuild test robot
2016-03-23 4:04 [RFC v3] PCI: PTM Driver Yong, Jonathan
2016-03-23 4:04 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-04-12 4:23 ` Bjorn Helgaas
2016-04-12 4:48 ` Bjorn Helgaas
2016-04-19 6:24 [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-19 6:24 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-04-19 6:29 [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-19 6:29 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-04-29 16:20 ` Bjorn Helgaas
2016-04-30 12:19 ` Bjorn Helgaas
2016-05-10 3:52 ` Yong, Jonathan
2016-05-08 2:38 ` Bjorn Helgaas
2016-05-09 3:11 ` Yong, Jonathan
2016-05-09 13:35 ` Bjorn Helgaas
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=56E66BF3.4080500@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).