From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh@kernel.org>,
"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
<linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
"open list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"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>,
Andrew Murray <amurray@thegoodpenguin.co.uk>
Subject: Re: [PATCH v3 0/4] PCI: brcmstb: Some minor fixes/features
Date: Mon, 11 May 2020 11:52:48 +0100 [thread overview]
Message-ID: <20200511105248.GB24954@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200507201544.43432-1-james.quinlan@broadcom.com>
On Thu, May 07, 2020 at 04:15:39PM -0400, Jim Quinlan wrote:
> v3 -- A change was submitted to [1] to make 'aspm-no-l0s' a general
> property for PCIe devices. As such, the STB PCIe YAML file
> merely notes that it may be used.
>
> v2 -- Dropped commit concerning CRS.
> -- Chanded new prop 'brcm,aspm-en-l0s' to 'aspm-no-l0s'.
> -- Capitalize first letter in commit subject line; spelling.
>
> v1 -- original
>
> [1] https://github.com/devicetree-org/dt-schema/blob/master/schemas/pci/pci-bus.yaml
>
> Jim Quinlan (4):
> PCI: brcmstb: Don't clk_put() a managed clock
> PCI: brcmstb: Fix window register offset from 4 to 8
> dt-bindings: PCI: brcmstb: New prop 'aspm-no-l0s'
> PCI: brcmstb: Disable L0s component of ASPM if requested
>
> .../bindings/pci/brcm,stb-pcie.yaml | 2 ++
> drivers/pci/controller/pcie-brcmstb.c | 19 +++++++++++++++----
> 2 files changed, 17 insertions(+), 4 deletions(-)
Applied to pci/brcmstb, thanks !
Lorenzo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-05-11 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 20:15 [PATCH v3 0/4] PCI: brcmstb: Some minor fixes/features Jim Quinlan
2020-05-07 20:15 ` [PATCH v3 1/4] PCI: brcmstb: Don't clk_put() a managed clock Jim Quinlan
2020-05-07 20:17 ` Florian Fainelli
2020-05-07 20:15 ` [PATCH v3 2/4] PCI: brcmstb: Fix window register offset from 4 to 8 Jim Quinlan
2020-05-07 20:15 ` [PATCH v3 3/4] dt-bindings: PCI: brcmstb: New prop 'aspm-no-l0s' Jim Quinlan
2020-05-08 1:11 ` Rob Herring
2020-05-07 20:15 ` [PATCH v3 4/4] PCI: brcmstb: Disable L0s component of ASPM if requested Jim Quinlan
2020-05-11 10:52 ` Lorenzo Pieralisi [this message]
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=20200511105248.GB24954@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=jeremy.linton@arm.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=nsaenzjulienne@suse.de \
--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).