From: Rob Herring <robh@kernel.org>
To: Jim Quinlan <jim2101024@gmail.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Mark Brown <broonie@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Saenz Julienne <nsaenzjulienne@suse.de>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 3/7] dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators
Date: Fri, 10 Dec 2021 12:23:09 -0600 [thread overview]
Message-ID: <YbObDXLXX5WR6qvp@robh.at.kernel.org> (raw)
In-Reply-To: <20211209211407.8102-4-jim2101024@gmail.com>
On Thu, Dec 09, 2021 at 04:14:01PM -0500, Jim Quinlan wrote:
> Add bindings for Brcmstb EP voltage regulators. A new mechanism is to be
> added to the Linux PCI subsystem that will allocate and turn on/off
> regulators. These are standard regulators -- vpcie12v, vpcie3v3, and
> vpcie3v3aux -- placed in the DT in the bridge node under the host bridge
> device.
>
> The use of a regulator property in the pcie EP subnode such as
> "vpcie12v-supply" depends on a pending pullreq to the pci-bus.yaml
> file at
>
> https://github.com/devicetree-org/dt-schema/pull/63
>
> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
> ---
> .../bindings/pci/brcm,stb-pcie.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-10 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 21:13 [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power Jim Quinlan
2021-12-09 21:13 ` [PATCH v10 1/7] PCI: brcmstb: Fix function return value handling Jim Quinlan
2021-12-09 21:34 ` Florian Fainelli
2021-12-09 21:14 ` [PATCH v10 2/7] dt-bindings: PCI: Correct brcmstb interrupts, interrupt-map Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 3/7] dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators Jim Quinlan
2021-12-10 18:23 ` Rob Herring [this message]
2021-12-09 21:14 ` [PATCH v10 5/7] PCI: brcmstb: Split brcm_pcie_setup() into two funcs Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 6/7] PCI: brcmstb: Add control of subdevice voltage regulators Jim Quinlan
2021-12-09 21:14 ` [PATCH v10 7/7] PCI: brcmstb: Do not turn off WOL regulators on suspend Jim Quinlan
2021-12-10 18:44 ` [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power Rob Herring
2021-12-10 20:31 ` Florian Fainelli
2022-01-04 14:17 ` Lorenzo Pieralisi
2022-01-04 23:01 ` 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=YbObDXLXX5WR6qvp@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--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=nsaenz@kernel.org \
--cc=nsaenzjulienne@suse.de \
/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).