From: Sai Teja Aluvala <quic_saluvala@quicinc.com>
To: agross@kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, johan.hedberg@gmail.com
Cc: mka@chromium.org, linux-bluetooth@vger.kernel.org,
quic_hemantg@quicinc.com, quic_bgodavar@quicinc.com,
quic_rjliao@quicinc.com, mcchou@chromium.org,
Sai Teja Aluvala <quic_saluvala@quicinc.com>
Subject: [RESEND v3] arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms
Date: Tue, 22 Mar 2022 14:01:04 +0530 [thread overview]
Message-ID: <1647937864-25661-1-git-send-email-quic_saluvala@quicinc.com> (raw)
Add IO regulator handler in SC7280 CRD based platforms.
As IO regulator varies in different SC7280 platforms
updating this handler in individual platform bluetooth node.
Signed-off-by: Sai Teja Aluvala <quic_saluvala@quicinc.com>
---
v3: Updated commit text to reflect the change
v2: updated reviewer comments.
v1: intial patch
---
---
arch/arm64/boot/dts/qcom/sc7280-crd.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7280-crd.dts b/arch/arm64/boot/dts/qcom/sc7280-crd.dts
index cd2755c..53ea3b4 100644
--- a/arch/arm64/boot/dts/qcom/sc7280-crd.dts
+++ b/arch/arm64/boot/dts/qcom/sc7280-crd.dts
@@ -23,6 +23,10 @@
};
};
+&bluetooth {
+ vddio-supply = <&vreg_l18b_1p8>;
+};
+
ap_tp_i2c: &i2c0 {
status = "okay";
clock-frequency = <400000>;
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc.
next reply other threads:[~2022-03-22 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:31 Sai Teja Aluvala [this message]
2022-03-22 9:01 ` [RESEND,v3] arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms bluez.test.bot
2022-04-11 21:04 ` [RESEND v3] " 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=1647937864-25661-1-git-send-email-quic_saluvala@quicinc.com \
--to=quic_saluvala@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=mka@chromium.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hemantg@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--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 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.