linux-kernel - Re: [PATCH v2] power: sequencing: qcom-wcn: explain why we need the WLAN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <173675603573.10811.7947138895685941865.b4-ty@linaro.org>
Date: Mon, 13 Jan 2025 09:14:01 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Stephan Gerhold <stephan.gerhold@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] power: sequencing: qcom-wcn: explain why we need the WLAN_EN GPIO hack

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Thu, 02 Jan 2025 13:15:30 +0100, Bartosz Golaszewski wrote:
> With the recent rework of the PCI power control code, the workaround for
> the wlan-enable GPIO - where we don't set a default (low) state in the
> power sequencing driver, but instead request the pin as-is - should no
> longer be needed but some platforms still fail to probe the WLAN
> controller. This is caused by the Qcom PCIe controller and needs a
> workaround in the controller driver so add a FIXME to eventually remove
> the hack from this driver once this is done.
> 
> [...]

Applied, thanks!

[1/1] power: sequencing: qcom-wcn: explain why we need the WLAN_EN GPIO hack
      commit: 29da3e8748f97dcf01498b00d42a3e7574ece80b

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>