From: "Marek Behún" <kabel@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
pali@kernel.org, "Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Marek Behún" <kabel@kernel.org>
Subject: [PATCH v2 00/10] PCI: aardvark controller changes BATCH 6
Date: Tue, 27 Sep 2022 16:19:16 +0200 [thread overview]
Message-ID: <20220927141926.8895-1-kabel@kernel.org> (raw)
Hello Lorenzo,
here comes v2 of batch 6 of Aardvark patches.
The original version can be found on the mailing list archives [1].
Changes since v1:
- dropped first patch,
PCI: pciehp: Enable DLLSC interrupt only if supported
since it is not a dependency for this series and Lukas Wunner
considers the change without value
- added more explanation to patches 2 and 6 (previously 3 and 7)
Marek
[1] https://lore.kernel.org/linux-pci/20220818135140.5996-1-kabel@kernel.org/
Marek Behún (2):
PCI: aardvark: Don't write read-only bits explicitly in PCI_ERR_CAP
register
PCI: aardvark: Explicitly disable Marvell strict ordering
Miquel Raynal (2):
PCI: aardvark: Add clock support
PCI: aardvark: Add suspend to RAM support
Pali Rohár (6):
PCI: pciehp: Enable Command Completed Interrupt only if supported
PCI: aardvark: Add support for DLLSC and hotplug interrupt
PCI: aardvark: Send Set_Slot_Power_Limit message
arm64: dts: armada-3720-turris-mox: Define slot-power-limit-milliwatt
for PCIe
PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by
linux/pci_regs.h macros
PCI: aardvark: Cleanup some register macros
.../dts/marvell/armada-3720-turris-mox.dts | 1 +
drivers/pci/controller/Kconfig | 3 +
drivers/pci/controller/pci-aardvark.c | 258 +++++++++++++++---
drivers/pci/hotplug/pciehp_hpc.c | 4 +-
4 files changed, 232 insertions(+), 34 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-27 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 14:19 Marek Behún [this message]
2022-09-27 14:19 ` [PATCH v2 01/10] PCI: pciehp: Enable Command Completed Interrupt only if supported Marek Behún
2022-12-07 14:29 ` Bjorn Helgaas
2022-09-27 14:19 ` [PATCH v2 02/10] PCI: aardvark: Add support for DLLSC and hotplug interrupt Marek Behún
2022-09-27 14:19 ` [PATCH v2 03/10] PCI: aardvark: Send Set_Slot_Power_Limit message Marek Behún
2022-09-27 14:19 ` [PATCH v2 04/10] arm64: dts: armada-3720-turris-mox: Define slot-power-limit-milliwatt for PCIe Marek Behún
2022-11-27 23:36 ` Gregory CLEMENT
2022-09-27 14:19 ` [PATCH v2 05/10] PCI: aardvark: Add clock support Marek Behún
2022-09-27 14:19 ` [PATCH v2 06/10] PCI: aardvark: Add suspend to RAM support Marek Behún
2022-09-27 14:19 ` [PATCH v2 07/10] PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by linux/pci_regs.h macros Marek Behún
2022-09-27 14:19 ` [PATCH v2 08/10] PCI: aardvark: Don't write read-only bits explicitly in PCI_ERR_CAP register Marek Behún
2022-09-27 14:19 ` [PATCH v2 09/10] PCI: aardvark: Explicitly disable Marvell strict ordering Marek Behún
2022-09-27 14:19 ` [PATCH v2 10/10] PCI: aardvark: Cleanup some register macros Marek Behún
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=20220927141926.8895-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@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).