linux-kernel - Re: [PATCH 04/14] wifi: ath10k: snoc: support powering on the device via pwrseq

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: <CAMRc=MfSbzFOYOupbHqxgzzkB9QQWZes9Zwo9tekpgU7XSGNRQ@mail.gmail.com>
Date: Mon, 5 Jan 2026 13:46:40 +0100
From: Bartosz Golaszewski <brgl@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Marcel Holtmann <marcel@...tmann.org>, Luiz Augusto von Dentz <luiz.dentz@...il.com>, 
	Jeff Johnson <jjohnson@...nel.org>, Bjorn Andersson <andersson@...nel.org>, 
	Konrad Dybcio <konradybcio@...nel.org>, Manivannan Sadhasivam <mani@...nel.org>, Vinod Koul <vkoul@...nel.org>, 
	Balakrishna Godavarthi <quic_bgodavar@...cinc.com>, Matthias Kaehlcke <mka@...omium.org>, 
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-bluetooth@...r.kernel.org, 
	linux-wireless@...r.kernel.org, ath10k@...ts.infradead.org, 
	linux-pm@...r.kernel.org, Krzysztof Kozlowski <krzk@...nel.org>
Subject: Re: [PATCH 04/14] wifi: ath10k: snoc: support powering on the device
 via pwrseq

On Sat, Jan 3, 2026 at 12:24 AM Dmitry Baryshkov
<dmitry.baryshkov@....qualcomm.com> wrote:
>
rite that in a comment, if you think that it makes the code more obvious.
> > >
> >
> > Yes, please make it more descriptive. Ideally I'd like to improve the
> > API to avoid such confusion in the future.
>
> The prolem is that we can't (or I don't see a way to). Power sequencing
> core has no way to distinguish these two cases.
>

I know, it's by design, but if we ever make fw_devlink mandatory for
all types of drivers (there was a discussion about this during LPC),
we may be able to improve this.

And with this comment improved:

Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>

Bart