From: Heiko Stuebner <heiko@sntech.de>
To: Diederik de Haas <diederik@cknow-tech.com>,
Joachim Eastwood <joachim.eastwood@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, jonas@kwiboo.se
Subject: Re: [PATCH v3 03/12] arm64: dts: rockchip: rk3588s-nanopi-r6: fix missing pcie rst pinctrl
Date: Thu, 16 Jul 2026 20:25:02 +0200 [thread overview]
Message-ID: <2204997.bB369e8A3T@phil> (raw)
In-Reply-To: <CAPSPb=tTbdzBZFq9NE0PCiD8+7pbWhErauhOfjjkp0DnhDwvRA@mail.gmail.com>
Am Donnerstag, 16. Juli 2026, 11:02:47 Mitteleuropäische Sommerzeit schrieb Joachim Eastwood:
> Hi Diederik,
>
> On Tue, 14 Jul 2026 at 15:02, Diederik de Haas <diederik@cknow-tech.com> wrote:
> >
> > Hi Joachim,
> >
> > On Mon Jul 13, 2026 at 10:30 PM CEST, Joachim Eastwood via B4 Relay wrote:
> > > From: Joachim Eastwood <joachim.eastwood@gmail.com>
> > >
> > > The pins are used as reset-gpios but not reserved through pinctrl.
> > >
> > > Fixes: f3c6526d6fb2 ("arm64: dts: rockchip: Convert dts files used as parents to dtsi files")
> > > Signed-off-by: Joachim Eastwood <joachim.eastwood@gmail.com>
> > > ---
> > > arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6.dtsi | 14 ++++++++++++++
> > > 1 file changed, 14 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6.dtsi b/arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6.dtsi
> > > index 67e284a15c35..8df6e1a21180 100644
> > > --- a/arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6.dtsi
> > > +++ b/arch/arm64/boot/dts/rockchip/rk3588s-nanopi-r6.dtsi
> > > @@ -360,12 +360,16 @@ rgmii_phy1: ethernet-phy@1 {
> > > };
> > >
> > > &pcie2x1l1 {
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&pcie2_1_rst>;
> > > reset-gpios = <&gpio1 RK_PA7 GPIO_ACTIVE_HIGH>;
> > > vpcie3v3-supply = <&vcc_3v3_pcie20>;
> > > status = "okay";
> > > };
> > >
> > > &pcie2x1l2 {
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&pcie2_2_rst>;
> > > reset-gpios = <&gpio3 RK_PD1 GPIO_ACTIVE_HIGH>;
> > > vpcie3v3-supply = <&vcc_3v3_pcie20>;
> > > status = "okay";
> > > @@ -420,6 +424,16 @@ rtc_int: rtc-int {
> > > };
> > > };
> > >
> > > + pcie {
> > > + pcie2_1_rst: pcie2-1-rst {
> >
> > ``pcie20x1_1_perstn_m2`` to match the schematic name?
> >
> > > + rockchip,pins = <1 RK_PA7 RK_FUNC_GPIO &pcfg_pull_none>;
> > > + };
> > > +
> > > + pcie2_2_rst: pcie2-2-rst {
> >
> > And ``pcie20x1_2_perstn_m0`` here?
>
> Can do.
> I see this used on a couple of other boards as well.
It's always a per-board thing. Matching pin-names to schematic
strings makes it just easier to reference from one to the other.
So yeah, it's very likely that schematics might be similar, but those
board designers sometimes also get waaaaay creative in their naming :-).
Heiko
next prev parent reply other threads:[~2026-07-16 18:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 20:30 [PATCH v3 00/12] arm64: dts: rockchip: Add NanoPi M6 board Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 01/12] dt-bindings: arm: rockchip: add FriendlyElec NanoPi M6 Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 02/12] arm64: dts: rockchip: rk3588s-nanopi-r6: fix missing sdmmc cd pinctrl Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 03/12] arm64: dts: rockchip: rk3588s-nanopi-r6: fix missing pcie rst pinctrl Joachim Eastwood via B4 Relay
2026-07-14 13:02 ` Diederik de Haas
2026-07-16 9:02 ` Joachim Eastwood
2026-07-16 18:25 ` Heiko Stuebner [this message]
2026-07-13 20:30 ` [PATCH v3 04/12] arm64: dts: rockchip: rk3588s-nanopi-r6: remove pull up on rtc int pin Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 05/12] arm64: dts: rockchip: rk3588s-nanopi-r6: pcie2x1l2: add clkreq Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 06/12] arm64: dts: rockchip: rk3588s-nanopi-r6: remove always-on and boot-on from vdd_npu_s0 reg Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 07/12] arm64: dts: rockchip: rk3588s-nanopi-r6: remove useless vcc_3v3_pcie20 Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 08/12] arm64: dts: rockchip: rk3588s-nanopi-r6: add gmac1 add phy-supply Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 09/12] arm64: dts: rockchip: rk3588s-nanopi-r6: remove bogus vcc5v0_usb regulator Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 10/12] arm64: dts: rockchip: rk3588s-nanopi-r6: add comment to gmac phy-mode Joachim Eastwood via B4 Relay
2026-07-13 20:30 ` [PATCH v3 11/12] arm64: dts: rockchip: rk3588s-nanopi-r6: refactor to support M6 boards Joachim Eastwood via B4 Relay
[not found] ` <20260713204131.C58091F000E9@smtp.kernel.org>
2026-07-16 9:24 ` Joachim Eastwood
2026-07-16 18:31 ` Heiko Stuebner
2026-07-13 20:30 ` [PATCH v3 12/12] arm64: dts: rockchip: add support for NanoPi M6 board Joachim Eastwood via B4 Relay
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=2204997.bB369e8A3T@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=joachim.eastwood@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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