public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Christian Zigotzky" <chzigotzky@xenosoft.de>,
	"Lukas Wunner" <lukas@wunner.de>,
	hypexed@yahoo.com.au, linuxppc-dev@lists.ozlabs.org,
	debian-powerpc@lists.debian.org,
	"mad skateman" <madskateman@gmail.com>
Subject: [GIT PULL] PCI fixes for v6.18
Date: Fri, 14 Nov 2025 16:24:20 -0600	[thread overview]
Message-ID: <20251114222420.GA2346148@bhelgaas> (raw)

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.18-fixes-5

for you to fetch changes up to 921b3f59b7b00cd7067ab775b0e0ca4eca436c2f:

  PCI/ASPM: Avoid L0s and L1 on Hi1105 [19e5:1105] Wi-Fi (2025-11-13 06:17:23 -0600)

----------------------------------------------------------------

- Cache the ASPM L0s/L1 Supported bits early so quirks can override them if
  necessary (Bjorn Helgaas)

- Add quirks for PA Semi and Freescale Root Ports and a HiSilicon Wi-Fi
  device that are reported to have broken L0s and L1 (Shawn Lin, Bjorn
  Helgaas)

----------------------------------------------------------------
Bjorn Helgaas (5):
      PCI/ASPM: Cache L0s/L1 Supported so advertised link states can be overridden
      PCI/ASPM: Add pcie_aspm_remove_cap() to override advertised link states
      PCI/ASPM: Convert quirks to override advertised link states
      PCI/ASPM: Avoid L0s and L1 on Freescale [1957:0451] Root Ports
      PCI/ASPM: Avoid L0s and L1 on PA Semi [1959:a002] Root Ports

Shawn Lin (1):
      PCI/ASPM: Avoid L0s and L1 on Hi1105 [19e5:1105] Wi-Fi

 drivers/pci/pci.h       |  2 ++
 drivers/pci/pcie/aspm.c | 25 +++++++++++++++++--------
 drivers/pci/probe.c     |  7 +++++++
 drivers/pci/quirks.c    | 40 +++++++++++++++++++++-------------------
 include/linux/pci.h     |  2 ++
 5 files changed, 49 insertions(+), 27 deletions(-)

             reply	other threads:[~2025-11-14 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 22:24 Bjorn Helgaas [this message]
2025-11-14 23:53 ` [GIT PULL] PCI fixes for v6.18 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-10-31 20:19 Bjorn Helgaas
2025-10-31 21:29 ` pr-tracker-bot
2025-10-24 19:29 Bjorn Helgaas
2025-10-24 23:48 ` pr-tracker-bot
2025-10-17 17:18 Bjorn Helgaas
2025-10-18 19:23 ` pr-tracker-bot
2025-10-08 22:25 Bjorn Helgaas
2025-10-09  2:40 ` 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=20251114222420.GA2346148@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=chzigotzky@xenosoft.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=hypexed@yahoo.com.au \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lukas@wunner.de \
    --cc=madskateman@gmail.com \
    --cc=mani@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --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