From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: heiko@sntech.de, Kever Yang <kever.yang@rock-chips.com>
Cc: andersson@kernel.org, Kever Yang <kever.yang@rock-chips.com>,
Shawn Lin <Shawn.lin@rock-chips.com>,
Conor Dooley <conor+dt@kernel.org>,
Finley Xiao <finley.xiao@rock-chips.com>,
Frank Wang <frank.wang@rock-chips.com>,
Rob Herring <robh@kernel.org>,
Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Andy Yan <andy.yan@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 2/2] arm64: dts: rockchip: Add rk3576 pcie nodes
Date: Mon, 14 Apr 2025 20:30:38 +0200 [thread overview]
Message-ID: <5019259.31r3eYUQgx@workhorse> (raw)
In-Reply-To: <20250414145110.11275-3-kever.yang@rock-chips.com>
On Monday, 14 April 2025 16:51:10 Central European Summer Time Kever Yang wrote:
> rk3576 has two pcie controllers, both are pcie2x1 work with
> naneng-combphy.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> Tested-by: Shawn Lin <Shawn.lin@rock-chips.com>
> ---
>
> Changes in v9:
> - rebase on 6.15-rc1
> - Add test tag
>
> Changes in v8: None
> Changes in v7:
> - re-order the properties.
>
> Changes in v6: None
> Changes in v5: None
> Changes in v4: None
> Changes in v3:
> - Update the subject
>
> Changes in v2:
> - Update clock and reset names and sequence to pass DTB check
>
> arch/arm64/boot/dts/rockchip/rk3576.dtsi | 108 +++++++++++++++++++++++
> 1 file changed, 108 insertions(+)
>
Reviewed-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Tested-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Successfully used this on an ArmSoM Sige5 RK3576 board. PCIe works.
Properties look correct, though the `ranges = ` doesn't separate out the
different ranges into individual `<cells>` but this doesn't seem to make
any difference and doesn't cause any warnings either. The only added
warning is "simple-bus unit address format error" which seems like a
bug in the thing generating the warning and not the device-tree itself,
as it doesn't seem to notice that the address of the node is within the
regs array, just not as the first cell.
I think this looks good for merging, I'll also send out a Sige5 enablement
patch shortly.
Thank you!
Regards,
Nicolas Frattaroli
next prev parent reply other threads:[~2025-04-14 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:51 [PATCH v9 0/2] rockchip: Add rk3576 pcie dts nodes Kever Yang
2025-04-14 14:51 ` [PATCH v9 1/2] dt-bindings: PCI: dw: rockchip: Add rk3576 support Kever Yang
2025-04-19 9:49 ` Manivannan Sadhasivam
2025-04-14 14:51 ` [PATCH v9 2/2] arm64: dts: rockchip: Add rk3576 pcie nodes Kever Yang
2025-04-14 18:30 ` Nicolas Frattaroli [this message]
2025-04-22 11:44 ` (subset) [PATCH v9 0/2] rockchip: Add rk3576 pcie dts nodes Heiko Stuebner
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=5019259.31r3eYUQgx@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=Shawn.lin@rock-chips.com \
--cc=andersson@kernel.org \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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