From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] arm64: dts: qcom: sm8350-mtp: Use mdt files for firmware
Date: Fri, 11 Jun 2021 10:38:08 +0530 [thread overview]
Message-ID: <20210611050808.2554431-1-vkoul@kernel.org> (raw)
As discussed in [1], it makes it easy for everyone to use mdt firmware file
name instead of mbn ones, so changes this for SM8350
[1]: http://lore.kernel.org/r/CALAqxLXn6wFBAxRkThxWg5RvTuFEX80kHPt8BVja1CpAB-qzGA@mail.gmail.com
Signed-off-by: Vinod Koul <vkoul@kernel.org>
---
arch/arm64/boot/dts/qcom/sm8350-mtp.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8350-mtp.dts b/arch/arm64/boot/dts/qcom/sm8350-mtp.dts
index 93740444dd1e..d859305f1f75 100644
--- a/arch/arm64/boot/dts/qcom/sm8350-mtp.dts
+++ b/arch/arm64/boot/dts/qcom/sm8350-mtp.dts
@@ -40,7 +40,7 @@ vph_pwr: vph-pwr-regulator {
&adsp {
status = "okay";
- firmware-name = "qcom/sm8350/adsp.mbn";
+ irmware-name = "qcom/sm8350/adsp.mdt";
};
&apps_rsc {
@@ -278,12 +278,12 @@ vreg_l13c_3p0: ldo13 {
&cdsp {
status = "okay";
- firmware-name = "qcom/sm8350/cdsp.mbn";
+ firmware-name = "qcom/sm8350/cdsp.mdt";
};
&mpss {
status = "okay";
- firmware-name = "qcom/sm8350/modem.mbn";
+ firmware-name = "qcom/sm8350/modem.mdt";
};
&qupv3_id_1 {
@@ -292,7 +292,7 @@ &qupv3_id_1 {
&slpi {
status = "okay";
- firmware-name = "qcom/sm8350/slpi.mbn";
+ firmware-name = "qcom/sm8350/slpi.mdt";
};
&tlmm {
--
2.31.1
next reply other threads:[~2021-06-11 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 5:08 Vinod Koul [this message]
2021-06-11 5:27 ` [PATCH] arm64: dts: qcom: sm8350-mtp: Use mdt files for firmware John Stultz
2021-06-11 5:45 ` Vinod Koul
2021-06-11 5:54 ` John Stultz
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=20210611050808.2554431-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=john.stultz@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).