From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, 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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
Casey Connolly <casey.connolly@linaro.org>
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sdm845-oneplus: Mark l14a regulator as boot-on
Date: Tue, 18 Nov 2025 15:32:32 +0100 [thread overview]
Message-ID: <47933d5d-65b7-42e9-bef8-c6e28c80b90d@oss.qualcomm.com> (raw)
In-Reply-To: <20251118-dts-oneplus-regulators-v1-3-79fb2f0f253b@ixit.cz>
On 11/18/25 3:11 PM, David Heidelberg via B4 Relay wrote:
> From: Casey Connolly <casey.connolly@linaro.org>
>
> This regulator is used only for the display, which is enabled by the
> bootloader and left on for continuous splash. Mark it as such.
>
> Signed-off-by: Casey Connolly <casey.connolly@linaro.org>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
Fixes?
Konrad
prev parent reply other threads:[~2025-11-18 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 14:11 [PATCH 0/3] Regulator adjustments for OnePlus 6 and 6T David Heidelberg via B4 Relay
2025-11-18 14:11 ` [PATCH 1/3] arm64: dts: qcom: sdm845-oneplus: Don't mark ts supply boot-on David Heidelberg via B4 Relay
2025-11-18 14:32 ` Konrad Dybcio
2025-11-18 14:11 ` [PATCH 2/3] arm64: dts: qcom: sdm845-oneplus: Don't keep panel regulator always on David Heidelberg via B4 Relay
2025-11-18 14:32 ` Konrad Dybcio
2025-11-18 14:44 ` David Heidelberg
2025-11-18 14:49 ` Konrad Dybcio
2025-11-18 14:11 ` [PATCH 3/3] arm64: dts: qcom: sdm845-oneplus: Mark l14a regulator as boot-on David Heidelberg via B4 Relay
2025-11-18 14:32 ` Konrad Dybcio [this message]
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=47933d5d-65b7-42e9-bef8-c6e28c80b90d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--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=phone-devel@vger.kernel.org \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®