From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: Varadarajan Narayanan <quic_varada@quicinc.com>
Subject: [PATCH v1 0/2] Add LDO5 MP5496 regulator
Date: Fri, 15 Dec 2023 11:07:02 +0530 [thread overview]
Message-ID: <cover.1702618483.git.quic_varada@quicinc.com> (raw)
Splitting the earlier patchset https://lore.kernel.org/linux-arm-msm/cover.1701160842.git.varada@hu-varada-blr.qualcomm.com/
and including the dt-bindings update (per https://lore.kernel.org/linux-arm-msm/e6f77480-749b-4ffb-93dd-764451e3f5fb@linaro.org/).
Had to split since the regulator driver change and the USB driver
change were dependent. If the USB driver change gets merged before
the regulator driver change it could break the kernel boot up.
The earlier patch ec4f047679d5, incorrectly used 'l2'
as the vdda-pll-supply. However, 'l5' is the correct
ldo that supplies power to the USB PHY.
Following checks passed:
make W=1 ARCH=arm64 -j 16 CHECK_DTBS=y DT_SCHEMA_FILES=qcom dtbs_check
make W=1 ARCH=arm64 -j 16 DT_CHECKER_FLAGS='-v -m' dt_binding_check DT_SCHEMA_FILES=qcom
Varadarajan Narayanan (2):
regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator
regulator: qcom_smd: Add LDO5 MP5496 regulator
.../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 2 +-
drivers/regulator/qcom_smd-regulator.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2023-12-15 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 5:37 Varadarajan Narayanan [this message]
2023-12-15 5:37 ` [PATCH v1 1/2] regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator Varadarajan Narayanan
2023-12-15 19:52 ` Rob Herring
2023-12-15 5:37 ` [PATCH v1 2/2] regulator: qcom_smd: Add LDO5 MP5496 regulator Varadarajan Narayanan
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=cover.1702618483.git.quic_varada@quicinc.com \
--to=quic_varada@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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