From: Jim Quinlan <james.quinlan@broadcom.com>
To: linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Cyril Brulebois <kibi@debian.org>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
james.quinlan@broadcom.com
Cc: linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM2711/BCM2835 ARM ARCHITECTURE),
linux-kernel@vger.kernel.org (open list),
linux-rpi-kernel@lists.infradead.org (moderated list:BROADCOM
BCM2711/BCM2835 ARM ARCHITECTURE), Rob Herring <robh@kernel.org>
Subject: [PATCH 0/2] PCI: brcmstb: Add panic/die handler to driver
Date: Fri, 13 Jun 2025 18:08:41 -0400 [thread overview]
Message-ID: <20250613220843.698227-1-james.quinlan@broadcom.com> (raw)
The first commit sets up a field variable and spinlock to indicate whether
the PCIe bridge is active. The second commit builds upon the first and
adds a "die" handler to the driver, which, when invoked, prints out a
summary of any pending PCIe errors. The "die" handler is careful not to
access any registers unless the bridge is active.
Jim Quinlan (2):
PCI: brcmstb: Add a way to indicate if PCIe bridge is active
PCI: brcmstb: Add panic/die handler to driver
drivers/pci/controller/pcie-brcmstb.c | 193 +++++++++++++++++++++++++-
1 file changed, 188 insertions(+), 5 deletions(-)
base-commit: 18531f4d1c8c47c4796289dbbc1ab657ffa063d2
--
2.34.1
next reply other threads:[~2025-06-13 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 22:08 Jim Quinlan [this message]
2025-06-13 22:08 ` [PATCH 1/2] PCI: brcmstb: Add a way to indicate if PCIe bridge is active Jim Quinlan
2025-06-13 23:23 ` Florian Fainelli
2025-08-06 19:14 ` Bjorn Helgaas
2025-08-07 18:03 ` Jim Quinlan
2025-06-13 22:08 ` [PATCH 2/2] PCI: brcmstb: Add panic/die handler to driver Jim Quinlan
2025-06-13 23:28 ` Florian Fainelli
2025-08-06 18:15 ` Bjorn Helgaas
2025-08-06 18:38 ` Jim Quinlan
2025-08-06 18:50 ` Bjorn Helgaas
2025-08-06 19:16 ` Jim Quinlan
2025-08-06 20:41 ` Florian Fainelli
2025-08-07 5:26 ` Manivannan Sadhasivam
2025-08-07 14:40 ` Jim Quinlan
2025-08-07 17:00 ` Florian Fainelli
2025-08-06 19:14 ` 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=20250613220843.698227-1-james.quinlan@broadcom.com \
--to=james.quinlan@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.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=robh@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
all inboxes | Powered by JetHome®