LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: linux-pci@vger.kernel.org
Cc: lorenzo.pieralisi@arm.com, nsaenz@kernel.org,
bhelgaas@google.com, rjw@rjwysocki.net, lenb@kernel.org,
robh@kernel.org, kw@linux.com, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jeremy Linton <jeremy.linton@arm.com>
Subject: [PATCH 0/3] CM4 ACPI PCIe quirk
Date: Thu, 5 Aug 2021 16:11:57 -0500 [thread overview]
Message-ID: <20210805211200.491275-1-jeremy.linton@arm.com> (raw)
The PFTF CM4 is an ACPI platform that is following the PCIe SMCCC
standard because its PCIe config space isn't ECAM compliant and is
split into two parts. One part for the root port registers and a
moveable window which points at a given device's 4K config space.
Thus it doesn't have a MCFG (and really any MCFG provided would be
nonsense anyway). As linux doesn't support the PCIe SMCCC standard
we key off a linux specific host bridge _DSD to add custom ECAM
ops and cfgres. The cfg op selects between those two regions, as
well as disallowing problematic accesses, particularly if the link
is down because there isn't an attached device.
Jeremy Linton (3):
PCI: brcmstb: Break register definitions into separate header
PCI: brcmstb: Add ACPI config space quirk
PCI/ACPI: Add new quirk detection, enable bcm2711
drivers/acpi/pci_mcfg.c | 14 ++
drivers/pci/controller/Makefile | 1 +
drivers/pci/controller/pcie-brcmstb-acpi.c | 77 +++++++++
drivers/pci/controller/pcie-brcmstb.c | 179 +-------------------
drivers/pci/controller/pcie-brcmstb.h | 182 +++++++++++++++++++++
include/linux/pci-ecam.h | 1 +
6 files changed, 276 insertions(+), 178 deletions(-)
create mode 100644 drivers/pci/controller/pcie-brcmstb-acpi.c
create mode 100644 drivers/pci/controller/pcie-brcmstb.h
--
2.31.1
next reply other threads:[~2021-08-05 21:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 21:11 Jeremy Linton [this message]
2021-08-05 21:11 ` [PATCH 1/3] PCI: brcmstb: Break register definitions into separate header Jeremy Linton
2021-08-10 10:07 ` Florian Fainelli
2021-08-10 15:10 ` Jeremy Linton
2021-08-11 8:39 ` Florian Fainelli
2021-08-05 21:11 ` [PATCH 2/3] PCI: brcmstb: Add ACPI config space quirk Jeremy Linton
2021-08-06 22:21 ` Bjorn Helgaas
2021-08-07 2:55 ` Jeremy Linton
2021-08-09 17:42 ` Bjorn Helgaas
2021-08-09 19:48 ` Jeremy Linton
2021-08-09 20:33 ` Bjorn Helgaas
2021-08-09 21:21 ` Jeremy Linton
2021-08-05 21:12 ` [PATCH 3/3] PCI/ACPI: Add new quirk detection, enable bcm2711 Jeremy Linton
2021-08-06 22:12 ` Bjorn Helgaas
2021-08-07 0:34 ` Jeremy Linton
2021-08-09 15:27 ` Rob Herring
2021-08-09 16:24 ` Jeremy Linton
2021-08-10 14:31 ` Shanker R Donthineni
2021-08-10 14:47 ` Jeremy Linton
2021-08-10 15:09 ` Shanker R Donthineni
2021-08-06 11:40 ` [PATCH 0/3] CM4 ACPI PCIe quirk Stefan Wahren
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=20210805211200.491275-1-jeremy.linton@arm.com \
--to=jeremy.linton@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--cc=kw@linux.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nsaenz@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--subject='Re: [PATCH 0/3] CM4 ACPI PCIe quirk' \
/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
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).