From: "Krzysztof Wilczyński" <kw@linux.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Lukas Wunner <lukas@wunner.de>, Niklas Schnelle <niks@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] PCI fixes for v6.13
Date: Sat, 21 Dec 2024 22:12:51 +0900 [thread overview]
Message-ID: <20241221131251.GA1086543@rocinante> (raw)
Hello Linus,
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.13-fixes-2
for you to fetch changes up to 774c71c52aa487001c7da9f93b10cedc9985c371:
PCI/bwctrl: Enable only if more than one speed is supported (2024-12-19 16:36:36 +0000)
----------------------------------------------------------------
PCI fixes for Linux 6.13
Two small patches that are important for fixing boot time hang on Intel JHL7540
"Titan Ridge" platforms equipped with a Thunderbolt controller.
The boot time issue manifests itself when a PCI Express bandwidth control is
unnecessarily enabled on the Thunderbolt controller downstream ports, which
only supports a link speed of 2.5 GT/s in accordance with USB4 v2 specification
(p. 671, sec. 11.2.1, "PCIe Physical Layer Logical Sub-block").
As such, there is no need to enable bandwidth control on such downstream port
links, which also works around the issue.
Both patches were tested by the original reporter on the hardware on which the
failure origin golly manifested itself. Both fixes were proven to resolve the
reported boot hang issue, and both patches have been in linux-next this week
with no reported problems.
Signed-off-by: Krzysztof Wilczyński <kwilczynski@kernel.org>
----------------------------------------------------------------
Lukas Wunner (2):
PCI: Honor Max Link Speed when determining supported speeds
PCI/bwctrl: Enable only if more than one speed is supported
drivers/pci/pci.c | 6 ++++--
drivers/pci/pcie/portdrv.c | 4 +++-
2 files changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2024-12-21 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 13:12 Krzysztof Wilczyński [this message]
2024-12-21 18:56 ` [GIT PULL] PCI fixes for v6.13 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 18:56 Bjorn Helgaas
2025-01-14 19:55 ` pr-tracker-bot
2024-12-01 0:14 Bjorn Helgaas
2024-12-01 2:41 ` pr-tracker-bot
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=20241221131251.GA1086543@rocinante \
--to=kw@linux.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=niks@kernel.org \
--cc=torvalds@linux-foundation.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