From: "Pali Rohár" <pali@kernel.org>
To: Gregory Clement <gregory.clement@bootlin.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "Marek Behún" <kabel@kernel.org>
Subject: Re: [PATCH 0/6] ARM: dts: pci-mvebu: Fix assigned-addresses for every PCIe Root Port
Date: Tue, 1 Nov 2022 23:19:41 +0100 [thread overview]
Message-ID: <20221101221941.ttrh3zgepqu6v2nn@pali> (raw)
In-Reply-To: <20221009111529.2eo2mwca3ywfkajy@pali>
ping?
On Sunday 09 October 2022 13:15:29 Pali Rohár wrote:
> Gregory, ping?
>
> On Thursday 18 August 2022 00:30:47 Pali Rohár wrote:
> > Per IEEE Std 1275-1994 bindings documentation (to which kernel DT
> > bindings refers), DT property assigned-addresses contains BDF address
> > of resource. Currently more PCIe Root Port nodes have BDF address in
> > assigned-addresses which points to different PCIe Root Port nodes. This
> > obviously does not make sense as the address resource specified in
> > assigned-addresses of every PCIe Root Port describes address range of
> > internal registers which are specific for corresponding Marvell PCIe
> > Root Port. Fix this issue and align all BDF addresses in
> > assigned-addresses DT property to specify correct BDF address of the
> > current PCIe Root Port.
> >
> > Note that current version of pci-mvebu.c controller driver, which
> > registers Marvell PCIe Root Ports, ignores BDF value in DT property
> > assigned-addresses. It expects that Root Port's assigned-addresses
> > contains address range of that root port. That is why driver currently
> > works without any issue and nobody spotted it. But if driver or
> > something else would do device tree validation then this issue should be
> > spotted and throws error. Also device tree files may be used by other
> > projects where drivers may require correct values.
> >
> > This patch series aligns BDF address of every Marvell PCIe Root Port in
> > node name, config space in reg property and mem in assigned-address
> > property of internal registers resource.
> >
> > Pali Rohár (6):
> > ARM: dts: dove: Fix assigned-addresses for every PCIe Root Port
> > ARM: dts: armada-370: Fix assigned-addresses for every PCIe Root Port
> > ARM: dts: armada-xp: Fix assigned-addresses for every PCIe Root Port
> > ARM: dts: armada-375: Fix assigned-addresses for every PCIe Root Port
> > ARM: dts: armada-38x: Fix assigned-addresses for every PCIe Root Port
> > ARM: dts: armada-39x: Fix assigned-addresses for every PCIe Root Port
> >
> > arch/arm/boot/dts/armada-370.dtsi | 2 +-
> > arch/arm/boot/dts/armada-375.dtsi | 2 +-
> > arch/arm/boot/dts/armada-380.dtsi | 4 ++--
> > arch/arm/boot/dts/armada-385.dtsi | 6 +++---
> > arch/arm/boot/dts/armada-39x.dtsi | 6 +++---
> > arch/arm/boot/dts/armada-xp-mv78230.dtsi | 8 ++++----
> > arch/arm/boot/dts/armada-xp-mv78260.dtsi | 16 ++++++++--------
> > arch/arm/boot/dts/dove.dtsi | 2 +-
> > 8 files changed, 23 insertions(+), 23 deletions(-)
> >
> > --
> > 2.20.1
> >
_______________________________________________
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:[~2022-11-01 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 22:30 [PATCH 0/6] ARM: dts: pci-mvebu: Fix assigned-addresses for every PCIe Root Port Pali Rohár
2022-08-17 22:30 ` [PATCH 1/6] ARM: dts: dove: " Pali Rohár
2022-08-17 22:30 ` [PATCH 2/6] ARM: dts: armada-370: " Pali Rohár
2022-08-17 22:30 ` [PATCH 3/6] ARM: dts: armada-xp: " Pali Rohár
2022-08-17 22:30 ` [PATCH 4/6] ARM: dts: armada-375: " Pali Rohár
2022-08-17 22:30 ` [PATCH 5/6] ARM: dts: armada-38x: " Pali Rohár
2022-08-17 22:30 ` [PATCH 6/6] ARM: dts: armada-39x: " Pali Rohár
2022-10-09 11:15 ` [PATCH 0/6] ARM: dts: pci-mvebu: " Pali Rohár
2022-11-01 22:19 ` Pali Rohár [this message]
2022-11-27 23:56 ` Gregory CLEMENT
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=20221101221941.ttrh3zgepqu6v2nn@pali \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@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