From: Johan Hovold <johan@kernel.org>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Abel Vesa <abel.vesa@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 3/3] arm64: dts: qcom: x1e80100-qcp: Add WiFi/BT pwrseq
Date: Tue, 15 Oct 2024 14:27:56 +0200 [thread overview]
Message-ID: <Zw5fzNZ_xCwPyw4G@hovoldconsulting.com> (raw)
In-Reply-To: <Zwj539cN2DJ7nd3A@linaro.org>
On Fri, Oct 11, 2024 at 12:11:43PM +0200, Stephan Gerhold wrote:
> On Thu, Oct 10, 2024 at 11:34:44AM +0200, Johan Hovold wrote:
> > Based on our discussions it seems we do not really need to describe the
> > internal PMU at all for WCN7850 (as the bluetooth and wlan blocks can be
> > enabled indepdendently) so perhaps we can just restore the old binding
> > and drop most of this boilerplate for all boards.
> >
>
> I think there is no clear conclusion on that yet. The old bindings
> didn't describe any power supplies for WiFi at all. The pwrseq bindings
> are currently the only way to do that.
>
> We could potentially move all the "PMU supplies" to the WiFi/BT nodes
> and rely on reference counting to handle them. But I think it's better
> to wait how the M.2/generic PCI power control discussion turns out
> before investing any time to refactor the current solution.
>
> There are existing users of qcom,wcn7850-pmu already in 6.11, so I think
> it does not hurt to take this patch as-is for now. We can clean them up
> together later if needed.
Sounds good.
But can you please address the following warning that I see with this
series:
pwrseq-qcom_wcn wcn7850-pmu: supply vddio1p2 not found, using dummy regulator
Not sure if it's the dtsi that's missing a supply if it's the driver
that needs fixing.
Johan
next prev parent reply other threads:[~2024-10-15 12:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 18:22 [PATCH 0/3] arm64: dts: qcom: x1e80100-qcp: Add WiFi/BT pwrseq Stephan Gerhold
2024-10-07 18:22 ` [PATCH 1/3] arm64: dts: qcom: x1e80100: Add QUP power domains and OPPs Stephan Gerhold
2024-10-10 9:29 ` Johan Hovold
2024-10-07 18:22 ` [PATCH 2/3] arm64: dts: qcom: x1e80100: Add uart14 Stephan Gerhold
2024-10-10 9:31 ` Johan Hovold
2024-12-26 22:38 ` (subset) " Bjorn Andersson
2024-10-07 18:22 ` [PATCH 3/3] arm64: dts: qcom: x1e80100-qcp: Add WiFi/BT pwrseq Stephan Gerhold
2024-10-10 9:34 ` Johan Hovold
2024-10-11 10:11 ` Stephan Gerhold
2024-10-15 12:27 ` Johan Hovold [this message]
2024-10-16 15:34 ` Stephan Gerhold
2024-10-17 9:28 ` Bartosz Golaszewski
2024-10-17 10:59 ` Mark Brown
2024-10-17 11:28 ` Bartosz Golaszewski
2024-10-17 12:00 ` Mark Brown
2024-10-17 12:21 ` Bartosz Golaszewski
2024-10-17 13:22 ` Mark Brown
2024-12-26 22:38 ` (subset) [PATCH 0/3] " Bjorn Andersson
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=Zw5fzNZ_xCwPyw4G@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephan.gerhold@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.