From: "James A. MacInnes" <james.a.macinnes@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
quic_wcheng@quicinc.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, lgirdwood@gmail.com, broonie@kernel.org,
"James A. MacInnes" <james.a.macinnes@gmail.com>
Subject: [PATCH 0/3] Add PMI8998 VBUS Regulator Support v2
Date: Tue, 11 Feb 2025 17:07:41 -0800 [thread overview]
Message-ID: <20250212010744.2554574-1-james.a.macinnes@gmail.com> (raw)
Greetings,
Thank you all for your feedback. I have integrated your recommendations
into this revised patch series (v2); please disregard the previous thread.
Summary of Changes:
- Patch 1/3: Updates the Device Tree Schema bindings to include
"qcom,pmi8998-vbus-reg" for PMI8998 support.
- Patch 2/3: Extends the Qualcomm USB VBUS regulator driver to support
PMI8998, dynamically configuring the regulator based on the PMIC type.
- Patch 3/3: Adds the VBUS regulator node to pmi8998.dtsi, enabling
USB Type-C VBUS support.
Motivation:
To enable VBUS operation on the SDM845 platform PMI8998 PMIC.
Kernel Version & Testing:
- These patches were developed and tested on Linux 6.13.
- Attempting to run Linux 6.14-rc2 on our Lantronix SOM resulted in a
hard crash, making it unsuitable for validation.
- Validation was performed using a modified device tree, confirming proper
regulator configuration.
- No regressions were observed on existing PMIC configurations.
Next Steps:
If there are any suggestions or required changes, please let me know.
I will be happy to revise and address any concerns.
Thanks again,
James A. MacInnes
james.a.macinnes@gmail.com
James A. MacInnes (3):
regulator: qcom_usb_vbus: Update DTS binding for PMI8998 support
regulator: qcom_usb_vbus: Add support for PMI8998 VBUS
arm64: boot: dts: pmi8998.dtsi: Add VBUS regulator node
.../regulator/qcom,usb-vbus-regulator.yaml | 1 +
arch/arm64/boot/dts/qcom/pmi8998.dtsi | 6 +++
drivers/regulator/qcom_usb_vbus-regulator.c | 38 ++++++++++++++++---
3 files changed, 40 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2025-02-12 1:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:07 James A. MacInnes [this message]
2025-02-12 1:07 ` [PATCH 1/3] regulator: qcom_usb_vbus: Update DTS binding for PMI8998 support James A. MacInnes
2025-02-12 2:04 ` Dmitry Baryshkov
2025-02-12 1:07 ` [PATCH 2/3] regulator: qcom_usb_vbus: Add support for PMI8998 VBUS James A. MacInnes
2025-02-12 3:48 ` Dmitry Baryshkov
2025-02-12 12:55 ` Konrad Dybcio
2025-02-12 16:46 ` James A. MacInnes
2025-02-12 15:29 ` Caleb Connolly
2025-02-12 15:37 ` Mark Brown
2025-02-12 16:09 ` Caleb Connolly
2025-02-12 19:25 ` James A. MacInnes
2025-02-12 16:56 ` James A. MacInnes
2025-02-12 17:12 ` Caleb Connolly
2025-02-12 1:07 ` [PATCH 3/3] arm64: boot: dts: pmi8998.dtsi: Add VBUS regulator node James A. MacInnes
2025-02-12 12:49 ` [PATCH 0/3] Add PMI8998 VBUS Regulator Support v2 Konrad Dybcio
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=20250212010744.2554574-1-james.a.macinnes@gmail.com \
--to=james.a.macinnes@gmail.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_wcheng@quicinc.com \
--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