From: "Heiko Stübner" <heiko@sntech.de>
To: Florian Klink <flokli@flokli.de>, Dragan Simic <dsimic@manjaro.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Muhammed Efe Cetin" <efectn@protonmail.com>,
"FUKAUMI Naoki" <naoki@radxa.com>,
"Tamás Szűcs" <tszucs@protonmail.ch>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: add rfkill node for M.2 E wifi on orangepi-5-plus
Date: Wed, 07 Aug 2024 19:17:49 +0200 [thread overview]
Message-ID: <4364452.rE2NhlSrgm@diego> (raw)
In-Reply-To: <c1cd51655f783d9ec2f6f068590c2a35@manjaro.org>
Hi Florian,
Am Mittwoch, 7. August 2024, 19:15:03 CEST schrieb Dragan Simic:
> On 2024-08-07 19:00, Florian Klink wrote:
> > This follows the same logic as 82d40b141a4c ("arm64: dts: rockchip: add
> > rfkill node for M.2 Key E WiFi on rock-5b").
> >
> > On the orangepi-5-plus, there's also a GPIO pin connecting the WiFi
> > enable signal inside the M.2 Key E slot.
> >
> > The exact GPIO PIN can be validated in the Armbian rk-5.10-rkr4 kernel
> > rk3588-orangepi-5-plus.dtsi file [1], which contains a `wifi_disable`
> > node referencing RK_PC4 on &gpio0.
> >
> > Signed-off-by: Florian Klink <flokli@flokli.de>
> > Tested-by: Florian Klink <flokli@flokli.de>
> > Link:
> > https://github.com/armbian/linux-rockchip/blob/9fbe23c9da24f236c6009f42d3f02c1ffb84c169/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts
> > [1]
>
> Unfortunately, this isn't how the "Link: ..." tag is to be used, or how
> a reference is to be provided. Please see the patch submission linked
> below for a correct example of providing links as references.
>
> https://lore.kernel.org/linux-rockchip/4449f7d4eead787308300e2d1d37b88c9d1446b2.1717308862.git.dsimic@manjaro.org/T/#u
please also don't post v2 patches as replies to v1.
Instead start a new mail thread please.
A lot of tooling cannot really find the correct version in such
multiversion threads.
Heiko
next prev parent reply other threads:[~2024-08-07 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 16:20 [PATCH] arm64: dts: rockchip: add rfkill node for M.2 E wifi on orangepi-5-plus Florian Klink
2024-08-07 16:26 ` Dragan Simic
2024-08-07 17:00 ` [PATCH v2] " Florian Klink
2024-08-07 17:15 ` Dragan Simic
2024-08-07 17:17 ` Heiko Stübner [this message]
2024-08-07 17:28 ` Florian Klink
2024-08-07 17:32 ` Dragan Simic
2024-08-07 17:24 ` Dragan Simic
2024-08-07 18:14 ` Florian Klink
2024-08-07 18:24 ` Heiko Stübner
2024-08-07 18:32 ` Dragan Simic
2024-08-07 21:12 ` Alexey Charkov
2024-08-07 21:30 ` Dragan Simic
2024-08-08 10:31 ` Florian Klink
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=4364452.rE2NhlSrgm@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=efectn@protonmail.com \
--cc=flokli@flokli.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=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tszucs@protonmail.ch \
/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