Re: [REGRESSION][BISECTED] wireless networking broken on Pinephone Pro

From: "Heiko Stübner" <heiko@sntech.de>
To: Oren Klopfer <oklopfer37@gmail.com>,
	linux-rockchip@lists.infradead.org,
	Thorsten Leemhuis <regressions@leemhuis.info>
Cc: regressions@lists.linux.dev, pbrobinson@gmail.com,
	guptarud@gmail.com, megi@xff.cz
Subject: Re: [REGRESSION][BISECTED] wireless networking broken on Pinephone Pro
Date: Wed, 10 Jun 2026 12:21:50 +0200	[thread overview]
Message-ID: <3761289.R56niFO833@diego> (raw)
In-Reply-To: <b68dc2ab-ab54-435f-a4e5-05b1b8397505@leemhuis.info>

Am Mittwoch, 10. Juni 2026, 11:28:03 Mitteleuropäische Sommerzeit schrieb Thorsten Leemhuis:
> On 6/8/26 00:59, Oren Klopfer wrote:
> > Apologies if this is not formatted properly, this is my first
> > submission to the kernel mailing list. WiFi specifications were
> > introduced into the Pinephone Pro device tree in
> > 096bd8c679185f898cae9933c6a68650fa26ea4f, but this causes complete
> > networking failure on some devices. The regression affects all
> > versions v6.18-rc1..v7.1-rc6.
> > 
> > An identical issue was reported for the Pinebook Pro at https://
> > lore.kernel.org/all/aUKOlj-RvTYlrpiS@rock.grzadka/; the regression
> > was reverted in 29d1f56c4f3001b7f547123e0a307c009ac717f8. The errors
> > faced on the Pinephone Pro are exactly the same as were reported for
> > the Pinebook Pro regression.
> > 
> > A previous patch at https://lore.kernel.org/all/20260112-
> > ppp_connectivity-v1-3-284d6e83b212@gmail.com/ attempted to resolve
> > this issue but never ended up being merged.
> > 
> > 096bd8c679185f898cae9933c6a68650fa26ea4f is the first bad commit
> > commit 096bd8c679185f898cae9933c6a68650fa26ea4f
> > Author: Peter Robinson <pbrobinson@gmail.com>
> > Date:   Fri Aug 29 12:38:24 2025 +0100
> > 
> >     arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro
> > [...]
> > 
> > Reverting the commit allows wireless connection to function again. I
> > am not really familiar with the process of submitting a revert
> > patch, but I'd request that this be done on all of 6.18 (LTS), 7.0
> > (Stable), 7.1 (Mainline). Thanks!
> Thx for the report. Sounds like a revert is the right course of action
> here. Could you submit one with a stable tag to ensure backporting? That
> might be the fastest way to resolve this, as that makes it easy to
> process for the maintainers to process this.

Was confused for like 5 minutes because "didn't we do that just recently",
until realizing, that it's the Pinephone this time, not the Pinebook.

So we'd need a similar one to
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?h=for-next&id=29d1f56c4f3001b7f547123e0a307c009ac717f8

Heiko

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip