From: "Pali Rohár" <pali@kernel.org>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Marek Behún" <kabel@kernel.org>,
"Russell King" <rmk+kernel@armlinux.org.uk>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: mvebu: Slot support
Date: Tue, 8 Mar 2022 12:38:31 +0100 [thread overview]
Message-ID: <20220308113831.pmq4apsxjwzfbesk@pali> (raw)
In-Reply-To: <20220302145733.12606-1-pali@kernel.org>
Hello Bjorn! Could you look if v2 changes are now fine?
On Wednesday 02 March 2022 15:57:29 Pali Rohár wrote:
> This patch series add slot support to pci-mvebu.c driver.
>
> It is based on branch pci/mvebu of git repository:
> https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git
>
> Changes in v2:
> * Dropped patch with PCI_EXP_SLTCAP_*_SHIFT macros as it is not needed anymore
> * Dropped patch "ARM: dts: turris-omnia: Set PCIe slot-power-limit-milliwatt properties" which was applied
> * Added support for PCIe 6.0 slot power limit encodings
> * Round down slot power limit value
> * Fix handling of slot power limit with scale x1.0 (0x00 value)
> * Use FIELD_PREP instead of _SHIFT macros
> * Changed commit message to Bjorn's suggestion
> * Changed comments in the code to match PCIe spec
> * Preserve user settings of PCI_EXP_SLTCTL_ASPL_DISABLE bit
>
> Pali Rohár (4):
> PCI: Add PCI_EXP_SLTCTL_ASPL_DISABLE macro
> dt-bindings: Add 'slot-power-limit-milliwatt' PCIe port property
> PCI: Add function for parsing 'slot-power-limit-milliwatt' DT property
> PCI: mvebu: Add support for sending Set_Slot_Power_Limit message
>
> Documentation/devicetree/bindings/pci/pci.txt | 6 ++
> drivers/pci/controller/pci-mvebu.c | 96 ++++++++++++++++++-
> drivers/pci/of.c | 64 +++++++++++++
> drivers/pci/pci.h | 15 +++
> include/uapi/linux/pci_regs.h | 1 +
> 5 files changed, 177 insertions(+), 5 deletions(-)
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2022-03-08 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 14:57 [PATCH v2 0/4] PCI: mvebu: Slot support Pali Rohár
2022-03-02 14:57 ` [PATCH v2 1/4] PCI: Add PCI_EXP_SLTCTL_ASPL_DISABLE macro Pali Rohár
2022-03-02 14:57 ` [PATCH v2 2/4] dt-bindings: Add 'slot-power-limit-milliwatt' PCIe port property Pali Rohár
2022-03-24 20:47 ` Rob Herring
2022-03-02 14:57 ` [PATCH v2 3/4] PCI: Add function for parsing 'slot-power-limit-milliwatt' DT property Pali Rohár
2022-03-24 17:13 ` Bjorn Helgaas
2022-03-25 9:20 ` Pali Rohár
2022-03-02 14:57 ` [PATCH v2 4/4] PCI: mvebu: Add support for sending Set_Slot_Power_Limit message Pali Rohár
2022-03-24 17:15 ` Bjorn Helgaas
2022-03-24 20:50 ` Rob Herring
2022-03-08 11:38 ` Pali Rohár [this message]
2022-03-21 18:29 ` [PATCH v2 0/4] PCI: mvebu: Slot support Pali Rohár
2022-03-24 17:12 ` Bjorn Helgaas
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=20220308113831.pmq4apsxjwzfbesk@pali \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=kabel@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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).