From: "Pali Rohár" <pali@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh@kernel.org>,
Gregory Clement <gregory.clement@bootlin.com>
Cc: "Marek Behún" <kabel@kernel.org>,
"Remi Pommarel" <repk@triplefau.lt>, Xogium <contact@xogium.me>,
"Tomasz Maciej Nowak" <tmn505@gmail.com>,
"Marc Zyngier" <maz@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] PCI: aardvark: Resource fixes
Date: Thu, 24 Jun 2021 23:55:44 +0200 [thread overview]
Message-ID: <20210624215546.4015-1-pali@kernel.org> (raw)
This patch series fixes configuring PCIe resources (IO and MEM) in
aardvark controller driver. It is required to initialize BARs on systems
with more cards, e.g. NVMe disks and WiFi AX cards.
Pali Rohár (2):
PCI: aardvark: Configure PCIe resources from 'ranges' DT property
arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
.../dts/marvell/armada-3720-turris-mox.dts | 17 ++
arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 11 +-
drivers/pci/controller/pci-aardvark.c | 195 +++++++++++++++++-
3 files changed, 220 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2021-06-24 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 21:55 Pali Rohár [this message]
2021-06-24 21:55 ` [PATCH 1/2] PCI: aardvark: Configure PCIe resources from 'ranges' DT property Pali Rohár
2021-06-24 21:55 ` [PATCH 2/2] arm64: dts: marvell: armada-37xx: Extend PCIe MEM space Pali Rohár
2021-07-23 12:52 ` Gregory CLEMENT
2021-07-23 14:12 ` Pali Rohár
2021-07-23 15:52 ` Lorenzo Pieralisi
2021-07-23 16:45 ` Pali Rohár
2021-08-07 11:35 ` Pali Rohár
2021-08-15 20:30 ` Pali Rohár
2021-08-17 16:39 ` Gregory CLEMENT
2021-08-20 12:41 ` [PATCH 0/2] PCI: aardvark: Resource fixes Lorenzo Pieralisi
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=20210624215546.4015-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=bhelgaas@google.com \
--cc=contact@xogium.me \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--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=maz@kernel.org \
--cc=repk@triplefau.lt \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tmn505@gmail.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).