From: sashiko-bot@kernel.org
To: erebion <erebion@erebion.eu>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 04/12] arm64: dts: qcom: sm6350-lena: Enable ADSP, CDSP, IPA & MPSS
Date: Fri, 13 Nov 2026 01:40:46 +0000 [thread overview]
Message-ID: <sashiko-outbox-212072@kernel.org> (raw)
In-Reply-To: <20261113-pdx213-upstream-3-v4-4-4b01c50a821c@erebion.eu>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [High] arm64: dts: qcom: Signed-off-by uses handle erebion instead of
real name
- [Low] arm64: dts: qcom: sm6350-lena: inconsistent Sony firmware-name
path
--
commit 242b8f170866c87626f6fca5aa977fc4b21bc731
Author: erebion <erebion@erebion@erebion.eu>
> arm64: dts: qcom: sm6350-lena: Enable ADSP, CDSP, IPA & MPSS
>
> Enable the ADSP, CDSP, IPA and MPSS (Modem) nodes for the Xperia 10 III.
>
> Signed-off-by: erebion <erebion@erebion.eu>
[Severity: High]
The Author and Signed-off-by lines use a handle ("erebion") instead of a
real human name, which does not meet the Developer's Certificate of Origin
requirements in Documentation/process/submitting-patches.rst.
> diff --git a/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts b/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> index a393b7533ccbf..4066de20ea23a 100644
> --- a/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> +++ b/arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dts
> @@ -68,6 +68,12 @@ memory@fe901000 {
> };
> };
>
> +&adsp {
> + firmware-name = "qcom/sm6350/Sony/pdx213/adsp.mbn";
> +
> + status = "okay";
> +};
> +
> &apps_rsc {
> regulators-0 {
> compatible = "qcom,pm6350-rpmh-regulators";
> @@ -291,6 +297,12 @@ pm6150l_bob: bob {
> };
> };
>
> +&cdsp {
> + firmware-name = "qcom/sm6350/Sony/pdx213/cdsp.mbn";
> +
> + status = "okay";
> +};
> +
> &gpi_dma0 {
> status = "okay";
> };
> @@ -316,6 +328,18 @@ touchscreen@48 {
> };
> };
>
> +&ipa {
> + firmware-name = "qcom/sm6350/Sony/pdx213/ipa_fws.mbn";
> +
> + status = "okay";
> +};
> +
> +&mpss {
> + firmware-name = "qcom/sm6350/Sony/pdx213/modem.mbn";
> +
> + status = "okay";
> +};
[Severity: Low]
Should firmware-name for adsp, cdsp, ipa, and mpss use the platform
codename ("qcom/sm6350/Sony/lena/...") instead of "pdx213"?
Other Sony Xperia device trees in arch/arm64/boot/dts/qcom/, including
single-board files such as sm6375-sony-xperia-murray-pdx225.dts and
sm8550-sony-xperia-yodo-pdx234.dts, follow the
qcom/<soc>/Sony/<platform>/<file>.mbn convention standardized in commit
f0a577c3a807 ("arm64: dts: qcom: sm8350: sagami: Fix remoteproc firmware
path").
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-pdx213-upstream-3-v4-0-4b01c50a821c@erebion.eu?part=4
next prev parent reply other threads:[~2026-11-13 1:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 1:24 [PATCH v4 00/12] Enable more nodes for the Xperia 10 III erebion
2026-11-13 1:24 ` [PATCH v4 01/12] arm64: dts: qcom: sm6350-lena: Add flash LED erebion
2026-11-13 1:32 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 02/12] arm64: dts: qcom: sm6350-lena: rename touch-en-regulator erebion
2026-11-13 1:28 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 03/12] arm64: dts: qcom: sm6350-lena: Add qcom,rmtfs-mem node erebion
2026-11-13 1:30 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 04/12] arm64: dts: qcom: sm6350-lena: Enable ADSP, CDSP, IPA & MPSS erebion
2026-11-13 1:40 ` sashiko-bot [this message]
2026-11-13 1:24 ` [PATCH v4 05/12] arm64: dts: qcom: sm6350-lena: Enable Bluetooth erebion
2026-11-13 1:24 ` [PATCH v4 06/12] arm64: dts: qcom: sm6350-lena: Enable wifi erebion
2026-11-13 1:29 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 07/12] arm64: dts: qcom: sm6350-lena: Enable PM7250B erebion
2026-11-13 1:34 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 08/12] arm64: dts: qcom: sm6350-lena: Enable PMK8350 erebion
2026-11-13 1:33 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 09/12] arm64: dts: qcom: sm6350-lena: Add PM7250B thermals erebion
2026-11-13 1:33 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 10/12] arm64: dts: qcom: sm6350-lena: Add PMK8350 thermals erebion
2026-11-13 1:33 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 11/12] arm64: dts: qcom: sm6350-lena: Add PM6150L thermals erebion
2026-11-13 1:38 ` sashiko-bot
2026-11-13 1:24 ` [PATCH v4 12/12] arm64: dts: qcom: sm6350-lena: enable remaining i2c busses erebion
2026-11-13 1:35 ` sashiko-bot
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=sashiko-outbox-212072@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=erebion@erebion.eu \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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