From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v1 3/6] arm64: qcom: dts: ifc6560: correct firmware paths
Date: Mon, 19 Sep 2022 22:00:34 +0300 [thread overview]
Message-ID: <20220919190037.2122284-4-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20220919190037.2122284-1-dmitry.baryshkov@linaro.org>
Correct firmware paths for the Inforce IFC6560 to include the SoC name.
Do not include the platform name, since the board uses test-signed
firmware.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
arch/arm64/boot/dts/qcom/sda660-inforce-ifc6560.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sda660-inforce-ifc6560.dts b/arch/arm64/boot/dts/qcom/sda660-inforce-ifc6560.dts
index 28050bc5f081..cb009522b194 100644
--- a/arch/arm64/boot/dts/qcom/sda660-inforce-ifc6560.dts
+++ b/arch/arm64/boot/dts/qcom/sda660-inforce-ifc6560.dts
@@ -99,7 +99,7 @@ v5p0_boost: v5p0-boost-regulator {
};
&adsp_pil {
- firmware-name = "qcom/ifc6560/adsp.mbn";
+ firmware-name = "qcom/sda660/adsp.mbn";
};
&blsp_i2c6 {
--
2.35.1
next prev parent reply other threads:[~2022-09-19 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 19:00 [PATCH v1 0/6] arm64: qcom: dts: correct firmware paths Dmitry Baryshkov
2022-09-19 19:00 ` [PATCH v1 1/6] arm64: qcom: dts: w737: " Dmitry Baryshkov
2022-09-19 19:00 ` [PATCH v1 2/6] arm64: qcom: dts: miix-630: " Dmitry Baryshkov
2022-09-19 19:00 ` Dmitry Baryshkov [this message]
2022-09-19 19:00 ` [PATCH v1 4/6] arm64: qcom: dts: sagami: " Dmitry Baryshkov
2022-09-19 19:00 ` [PATCH v1 5/6] arm64: qcom: dts: pdx223: " Dmitry Baryshkov
2022-09-19 19:00 ` [PATCH v1 6/6] arm64: qcom: dts: nile: " Dmitry Baryshkov
2022-10-18 3:05 ` [PATCH v1 0/6] arm64: qcom: dts: " 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=20220919190037.2122284-4-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@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).