From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marc Dietrich <marvin24@gmx.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Arnd Bergmann <arnd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: tegra: paz00: configure WiFi rfkill switch through device tree
Date: Sun, 22 Feb 2026 20:57:51 -0800 [thread overview]
Message-ID: <aZvdDIYlCjg8sVGT@google.com> (raw)
In-Reply-To: <07c024a6-d2f9-5805-4ae7-cbc89cda53bf@gmx.de>
Hi Marc,
On Sat, Feb 21, 2026 at 03:24:35PM +0100, Marc Dietrich wrote:
> Hi Dmitry,
>
> On Sat, 14 Feb 2026, Marc Dietrich wrote:
>
> > Hi Dmitry,
> >
> > On Fri, 13 Feb 2026, Dmitry Torokhov wrote:
> >
> > > As of d64c732dfc9e ("net: rfkill: gpio: add DT support") rfkill-gpio
> > > device can be instantiated via device tree.
> > >
> > > Add the declaration there and drop board-paz00.c file and relevant
> > > Makefile fragments.
> > >
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > ---
> > >
> > > This is not tested on real hardware, compile tested only...
> > >
> > > arch/arm/boot/dts/nvidia/tegra20-paz00.dts | 8 ++++
> > > arch/arm/mach-tegra/Makefile | 2 -
> > > arch/arm/mach-tegra/board-paz00.c | 56 ----------------------
> > > arch/arm/mach-tegra/board.h | 2 -
> > > arch/arm/mach-tegra/tegra.c | 4 --
> > > 5 files changed, 8 insertions(+), 64 deletions(-)
> > >
> > > diff --git a/arch/arm/boot/dts/nvidia/tegra20-paz00.dts
> > > b/arch/arm/boot/dts/nvidia/tegra20-paz00.dts
> > > index 1408e1e00759..d1093ad569e6 100644
> > > --- a/arch/arm/boot/dts/nvidia/tegra20-paz00.dts
> > > +++ b/arch/arm/boot/dts/nvidia/tegra20-paz00.dts
> > > @@ -706,6 +706,14 @@ vdd_pnl_reg: regulator-3v0 {
> > > enable-active-high;
> > > };
> > >
> > > + rfkill {
> > > + compatible = "rfkill-gpio";
> > > + label = "wifi_rfkill";
> > > + radio-type = "wlan";
> > > + reset-gpios = <&gpio TEGRA_GPIO(D, 1) GPIO_ACTIVE_HIGH>;
> >
> > I guess this can be removed, as it should trigger the LED, which is
> > already included elsewhere ....
> >
> > > + shutdown-gpios = <&gpio TEGRA_GPIO(K, 5) GPIO_ACTIVE_HIGH>;
> > > + };
> > > +
> > > sound {
> > > compatible = "nvidia,tegra-audio-alc5632-paz00",
> > > "nvidia,tegra-audio-alc5632";
> >
> > I'll give it a try and report back.
>
> rfkill (and LED) works as expected. With the reset-gpio line mentioned above
> removed, you can add my Tested-By.
Thank you Marc.
I am still a bit confused about the reset gpio. As far as I understand
looking through old commits reset gpio (PD1) is distinct from the LED
gpio (PD0) that is currently being controlled by "gpio-leds".
I guess the rfkill driver needs at least one of "reset" or "shutdown"
gpios, and that is why it continues to work with only shutdown, but I am
trying to understand if PD1 was never connected to the WiFi chip reset
line and instead is used for something else, or if it is indeed a reset
line...
Was the patch not working with reset-gpios present? I am trying to
gather data to craft a proper commit message.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-02-23 4:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 0:35 [PATCH] ARM: tegra: paz00: configure WiFi rfkill switch through device tree Dmitry Torokhov
2026-02-14 20:43 ` Marc Dietrich
2026-02-21 14:24 ` Marc Dietrich
2026-02-23 4:57 ` Dmitry Torokhov [this message]
2026-02-28 10:25 ` Marc Dietrich
2026-03-01 20:55 ` Marc Dietrich
2026-03-01 21:56 ` Dmitry Torokhov
2026-03-07 21:13 ` Marc Dietrich
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=aZvdDIYlCjg8sVGT@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=robh@kernel.org \
--cc=thierry.reding@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