From: Johan Hovold <johan@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bjorn.andersson@linaro.org, konrad.dybcio@somainline.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
johan+linaro@kernel.org, steev@kali.org
Subject: Re: [PATCH] arm64: dts: qcom: thinkpad-x13s: Update firmware location
Date: Tue, 13 Sep 2022 12:00:52 +0200 [thread overview]
Message-ID: <YyBU1G9O1l4LqMF7@hovoldconsulting.com> (raw)
In-Reply-To: <20220913054030.3234-1-manivannan.sadhasivam@linaro.org>
On Tue, Sep 13, 2022 at 11:10:30AM +0530, Manivannan Sadhasivam wrote:
> The firmware location in linux-firmware has been changed to include the
> SoC name. So use the updated location in Thinkpad devicetree.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I guess we should pick a commit prefix that we stick to for changes to
this driver.
arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s:
is arguably unnecessarily long even if it follows the pattern of some
other qcom dts.
Shall we just use
arm64: dts: qcom: sc8280xp-x13s:
which matches sc8280xp-crd? Or stick "lenovo" in there as well? Or just
keep the whole thing unchanged?
> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> index c379650e52b1..3b7943d6e164 100644
> --- a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> @@ -554,13 +554,13 @@ keyboard@68 {
> };
>
> &remoteproc_adsp {
> - firmware-name = "qcom/LENOVO/21BX/qcadsp8280.mbn";
> + firmware-name = "qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn";
>
> status = "okay";
> };
>
> &remoteproc_nsp0 {
> - firmware-name = "qcom/LENOVO/21BX/qccdsp8280.mbn";
> + firmware-name = "qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn";
>
> status = "okay";
> };
Change itself looks good otherwise:
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
Johan
next prev parent reply other threads:[~2022-09-13 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:40 [PATCH] arm64: dts: qcom: thinkpad-x13s: Update firmware location Manivannan Sadhasivam
2022-09-13 10:00 ` Johan Hovold [this message]
2022-09-13 10:07 ` Johan Hovold
2022-09-13 10:57 ` Manivannan Sadhasivam
2022-09-13 20:13 ` Bjorn Andersson
2022-09-13 20:27 ` Steev Klimaszewski
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=YyBU1G9O1l4LqMF7@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=steev@kali.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).