From: Sinan Kaya <okaya@codeaurora.org>
To: "Alex G." <mr.nuke.me@gmail.com>,
Alex_Gagniuc@Dellteam.com, bhelgaas@google.com
Cc: Austin.Bolen@dell.com, Shyam.Iyer@dell.com,
keith.busch@intel.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Check for PCIe downtraining conditions
Date: Thu, 31 May 2018 11:54:18 -0400 [thread overview]
Message-ID: <35563ce3-e235-096c-4b9b-5f3664d67d0f@codeaurora.org> (raw)
In-Reply-To: <3b8a895b-3080-7ddb-cbfd-5aa972e9bf65@gmail.com>
On 5/31/2018 11:46 AM, Alex G. wrote:
>> https://lkml.org/lkml/2018/3/30/553
> Oh, pcie_get_speed_cap()/pcie_get_width_cap() seems to handle the
> capability. Not seeing one for status and speed name.
>
>> are you working on linux-next?
> v4.17-rc7
>
I think everything you need is in the series. I don't know which linux
tree this landed or if it landed. Probably, it is shipping for 4.18.
Need some help from Bjorn where to locate these.
Fri, 30 Mar 2018 16:04:40 -0500
Bjorn Helgaas (6):
bnx2x: Report PCIe link properties with pcie_print_link_status()
bnxt_en: Report PCIe link properties with pcie_print_link_status()
cxgb4: Report PCIe link properties with pcie_print_link_status()
fm10k: Report PCIe link properties with pcie_print_link_status()
ixgbe: Report PCIe link properties with pcie_print_link_status()
PCI: Remove unused pcie_get_minimum_link()
Tal Gilboa (8):
PCI: Add pcie_get_speed_cap() to find max supported link speed
PCI: Add pcie_get_width_cap() to find max supported link width
PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth
PCI: Add pcie_bandwidth_available() to compute bandwidth available to device
PCI: Add pcie_print_link_status() to log link speed and whether it's limited
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-05-31 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 15:05 [PATCH] PCI: Check for PCIe downtraining conditions Alexandru Gagniuc
2018-05-31 15:28 ` Sinan Kaya
2018-05-31 15:29 ` Alex_Gagniuc
2018-05-31 15:38 ` Sinan Kaya
2018-05-31 15:46 ` Alex G.
2018-05-31 15:54 ` Sinan Kaya [this message]
2018-05-31 16:01 ` Alex G.
2018-05-31 16:13 ` Sinan Kaya
2018-05-31 16:49 ` Alex G.
2018-05-31 16:50 ` Alex G.
2018-05-31 17:11 ` Sinan Kaya
2018-05-31 17:27 ` Alex G.
2018-05-31 21:52 ` Alex G.
2018-05-31 15:30 ` Sinan Kaya
2018-05-31 21:44 ` Alex G.
2018-06-01 13:30 ` Sinan Kaya
2018-06-02 17:42 ` Pavel Machek
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=35563ce3-e235-096c-4b9b-5f3664d67d0f@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=Alex_Gagniuc@Dellteam.com \
--cc=Austin.Bolen@dell.com \
--cc=Shyam.Iyer@dell.com \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
/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).