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>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
james.quinlan@broadcom.com
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
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)
Subject: [PATCH 0/3] PCI: brcmstb: Include cable-modem SoCs
Date: Mon, 9 Jun 2025 18:17:03 -0400 [thread overview]
Message-ID: <20250609221710.10315-1-james.quinlan@broadcom.com> (raw)
At Broadcom, the Cable Modem group and the Settop Box group use the same
PCIe RC driver for multiple chips. This series adds the CM SoCs to the
compatibility list as well as some CM-specific code.
Jim Quinlan (3):
dt bindings: PCI: brcmstb: Include cable-modem SoCs
PCI: brcmstb: Refactor indication of SSC status
PCI: brcmstb: Enable Broadcom Cable Modem SoCs
.../bindings/pci/brcm,stb-pcie.yaml | 4 +
drivers/pci/controller/pcie-brcmstb.c | 193 ++++++++++++++----
2 files changed, 159 insertions(+), 38 deletions(-)
base-commit: cfc4ca8986bb1f6182da6cd7bb57f228590b4643
--
2.43.0
next reply other threads:[~2025-06-09 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 22:17 Jim Quinlan [this message]
2025-06-09 22:17 ` [PATCH 1/3] dt bindings: PCI: brcmstb: Include cable-modem SoCs Jim Quinlan
2025-06-10 15:23 ` Conor Dooley
2025-06-12 20:33 ` Florian Fainelli
2025-06-09 22:17 ` [PATCH 2/3] PCI: brcmstb: Refactor indication of SSC status Jim Quinlan
2025-06-12 20:33 ` Florian Fainelli
2025-06-09 22:17 ` [PATCH 3/3] PCI: brcmstb: Enable Broadcom Cable Modem SoCs Jim Quinlan
2025-06-12 20:37 ` Florian Fainelli
2025-07-08 7:38 ` Manivannan Sadhasivam
2025-07-10 17:23 ` Manivannan Sadhasivam
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=20250609221710.10315-1-james.quinlan@broadcom.com \
--to=james.quinlan@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jim2101024@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).