All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.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: Re: [RFC PATCH 6/7] arm64: qcom: dts: pdx223: correct firmware paths
Date: Sat, 17 Sep 2022 15:12:22 +0200	[thread overview]
Message-ID: <8cd3c0c3-41c4-79f1-9419-6859f126f087@somainline.org> (raw)
In-Reply-To: <20220915152630.133528-7-dmitry.baryshkov@linaro.org>



On 15.09.2022 17:26, Dmitry Baryshkov wrote:
> Correct firmware paths for the Sony Xperia 1 IV to include the SoC name.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
SONY/not-SONY discussion from my Sagami email aside, it's fine to
change pdx223 to nagara here, as its cousin, the 5 IV was announced
like 2 weeks ago and looking at the fw that was uploaded to their
OTA servers, I can tell they are still using a single key for
devices sharing the same SoC, as they always has been.

Konrad
>  .../boot/dts/qcom/sm8450-sony-xperia-nagara-pdx223.dts      | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sm8450-sony-xperia-nagara-pdx223.dts b/arch/arm64/boot/dts/qcom/sm8450-sony-xperia-nagara-pdx223.dts
> index d68765eb6d4f..ae867dbe4762 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450-sony-xperia-nagara-pdx223.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8450-sony-xperia-nagara-pdx223.dts
> @@ -523,17 +523,17 @@ &pcie0_phy {
>  };
>  
>  &remoteproc_adsp {
> -	firmware-name = "qcom/adsp.mbn";
> +	firmware-name = "qcom/sdm8450/pdx223/adsp.mbn";
>  	status = "okay";
>  };
>  
>  &remoteproc_cdsp {
> -	firmware-name = "qcom/cdsp.mbn";
> +	firmware-name = "qcom/sdm8450/pdx223/cdsp.mbn";
>  	status = "okay";
>  };
>  
>  &remoteproc_slpi {
> -	firmware-name = "qcom/slpi.mbn";
> +	firmware-name = "qcom/sdm8450/pdx223/slpi.mbn";
>  	status = "okay";
>  };
>  

  reply	other threads:[~2022-09-17 13:12 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 ` [RFC PATCH 5/7] arm64: qcom: dts: sagami: " Dmitry Baryshkov
2022-09-17 13:07   ` 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 [this message]
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=8cd3c0c3-41c4-79f1-9419-6859f126f087@somainline.org \
    --to=konrad.dybcio@somainline.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.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 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.