devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [RFC PATCH 5/7] arm64: qcom: dts: sagami: correct firmware paths
Date: Thu, 15 Sep 2022 18:26:28 +0300	[thread overview]
Message-ID: <20220915152630.133528-6-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20220915152630.133528-1-dmitry.baryshkov@linaro.org>

Correct firmware paths for the Sony Xperia Sagami devices to include the
SoC name.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
 .../arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi b/arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi
index b3c9952ac173..e0940cb58681 100644
--- a/arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi
+++ b/arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi
@@ -77,12 +77,12 @@ ramoops@ffc00000 {
 
 &adsp {
 	status = "okay";
-	firmware-name = "qcom/adsp.mbn";
+	firmware-name = "qcom/sdm8350/sagami/adsp.mbn";
 };
 
 &cdsp {
 	status = "okay";
-	firmware-name = "qcom/cdsp.mbn";
+	firmware-name = "qcom/sdm8350/sagami/cdsp.mbn";
 };
 
 &i2c1 {
@@ -175,12 +175,12 @@ &i2c17 {
 &ipa {
 	status = "okay";
 	memory-region = <&pil_ipa_fw_mem>;
-	firmware-name = "qcom/ipa_fws.mbn";
+	firmware-name = "qcom/sdm8350/sagami/ipa_fws.mbn";
 };
 
 &mpss {
 	status = "okay";
-	firmware-name = "qcom/modem.mbn";
+	firmware-name = "qcom/sdm8350/sagami/modem.mbn";
 };
 
 &pmk8350_rtc {
@@ -210,7 +210,7 @@ &qupv3_id_2 {
 
 &slpi {
 	status = "okay";
-	firmware-name = "qcom/slpi.mbn";
+	firmware-name = "qcom/sdm8350/sagami/slpi.mbn";
 };
 
 &spi14 {
-- 
2.35.1


  parent reply	other threads:[~2022-09-15 15:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 15:26 [RFC PATCH 0/7] arm64: qcom: dts: correct firmware paths Dmitry Baryshkov
2022-09-15 15:26 ` [RFC PATCH 1/7] arm64: qcom: dts: c630: " Dmitry Baryshkov
2022-09-19  5:39   ` Steev Klimaszewski
2022-09-15 15:26 ` [RFC PATCH 2/7] arm64: qcom: dts: w737: " Dmitry Baryshkov
2022-09-15 15:26 ` [RFC PATCH 3/7] arm64: qcom: dts: miix-630: " Dmitry Baryshkov
2022-09-15 15:26 ` [RFC PATCH 4/7] arm64: qcom: dts: ifc6560: " Dmitry Baryshkov
2022-09-15 15:26 ` Dmitry Baryshkov [this message]
2022-09-17 13:07   ` [RFC PATCH 5/7] arm64: qcom: dts: sagami: " Konrad Dybcio
2022-09-17 20:33     ` Dmitry Baryshkov
2022-09-19 14:53       ` Konrad Dybcio
2022-09-15 15:26 ` [RFC PATCH 6/7] arm64: qcom: dts: pdx223: " Dmitry Baryshkov
2022-09-17 13:12   ` Konrad Dybcio
2022-09-15 15:26 ` [RFC PATCH 7/7] arm64: qcom: dts: nile: " Dmitry Baryshkov
2022-09-17 13:13   ` 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=20220915152630.133528-6-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).