From: Jim Quinlan <jim2101024@gmail.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>,
Phil Elwell <phil@raspberrypi.com>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
james.quinlan@broadcom.com
Cc: 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), Rob Herring <robh@kernel.org>
Subject: [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device
Date: Thu, 6 Apr 2023 08:46:21 -0400 [thread overview]
Message-ID: <20230406124625.41325-1-jim2101024@gmail.com> (raw)
The current driver assumes the downstream devices can provide clkreq# for
ASPM. These commits accomodate devices w/ or w/o clkreq# and also handle
L1SS-capable devices.
The Raspian Linux folks have already been using a PCIe RC property
"brcm,enable-l1ss". These commits use the same property, in a
backward-compatible manner, and the implementaion adds more detail and also
automatically identifies devices w/o a clkreq# signal, i.e. most devices
plugged into an RPi CM4 IO board.
Jim Quinlan (3):
dt-bindings: PCI: brcmstb: Add two optional props
PCI: brcmstb: Clkreq# accomodations of downstream device
PCI: brcmstb: Allow setting the completion timeout
.../bindings/pci/brcm,stb-pcie.yaml | 12 +++
drivers/pci/controller/pcie-brcmstb.c | 93 +++++++++++++++++--
2 files changed, 95 insertions(+), 10 deletions(-)
base-commit: 99ddf2254febae9eab7fb0bcc02c5322243f5c49
--
2.17.1
next reply other threads:[~2023-04-06 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 12:46 Jim Quinlan [this message]
2023-04-06 12:46 ` [PATCH v1 1/3] dt-bindings: PCI: brcmstb: Add two optional props Jim Quinlan
2023-04-06 15:39 ` Stefan Wahren
2023-04-06 16:58 ` Jim Quinlan
2023-04-06 18:35 ` Krzysztof Kozlowski
2023-04-06 18:47 ` Florian Fainelli
2023-04-06 18:53 ` Krzysztof Kozlowski
2023-04-06 18:34 ` Krzysztof Kozlowski
2023-04-06 18:53 ` Florian Fainelli
2023-04-06 18:54 ` Krzysztof Kozlowski
2023-04-06 21:31 ` [PATCH v1 0/3] PCI: brcmstb: Clkreq# accomodations of downstream device Cyril Brulebois
2023-04-07 15:06 ` Hank Barta
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=20230406124625.41325-1-jim2101024@gmail.com \
--to=jim2101024@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=james.quinlan@broadcom.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=phil@raspberrypi.com \
--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