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/2] PCI: brcmstb: Use "num-lanes" DT property if present
Date: Fri, 30 May 2025 18:40:31 -0400 [thread overview]
Message-ID: <20250530224035.41886-1-james.quinlan@broadcom.com> (raw)
v2:
-- DT bindings: Add default, maximum values for 'num-lanes' (Rob)
-- Add 'if' clause to clamp maximum requested num-lanes
v1: original
Jim Quinlan (2):
dt-bindings: PCI: brcm,stb-pcie: Add num-lanes property
PCI: brcmstb: Use "num-lanes" DT property if present
.../bindings/pci/brcm,stb-pcie.yaml | 4 +++
drivers/pci/controller/pcie-brcmstb.c | 26 ++++++++++++++++++-
2 files changed, 29 insertions(+), 1 deletion(-)
base-commit: 01f95500a162fca88cefab9ed64ceded5afabc12
--
2.43.0
next reply other threads:[~2025-05-30 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 22:40 Jim Quinlan [this message]
2025-05-30 22:40 ` [PATCH 1/2] dt-bindings: PCI: brcm,stb-pcie: Add num-lanes property Jim Quinlan
2025-05-30 23:32 ` Florian Fainelli
2025-06-03 16:24 ` Florian Fainelli
2025-06-03 17:16 ` Jim Quinlan
2025-06-03 17:17 ` Florian Fainelli
2025-06-03 17:24 ` Jim Quinlan
2025-06-05 22:36 ` Rob Herring
2025-06-05 22:42 ` Florian Fainelli
2025-06-05 22:41 ` Rob Herring (Arm)
2025-05-30 22:40 ` [PATCH 2/2] PCI: brcmstb: Use "num-lanes" DT property if present Jim Quinlan
2025-05-30 23:33 ` Florian Fainelli
2025-05-31 6:34 ` Manivannan Sadhasivam
2025-06-02 15:36 ` Jim Quinlan
2025-06-24 22:01 ` Bjorn Helgaas
2025-06-25 19:46 ` Jim Quinlan
2025-05-30 23:34 ` [PATCH 0/2] " Florian Fainelli
2025-06-23 11:53 ` Manivannan Sadhasivam
-- strict thread matches above, loose matches on Subject: below --
2025-05-09 22:28 Jim Quinlan
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=20250530224035.41886-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