From: sashiko-bot@kernel.org
To: "Atanas Filipov" <atanas.filipov@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 3/4] arm64: dts: qcom: sm8250: Add JPEG encoder node
Date: Mon, 29 Jun 2026 12:34:54 +0000 [thread overview]
Message-ID: <20260629123455.009A21F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629121750.3469292-4-atanas.filipov@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Renaming `interconnect-names` in the `camss` DT node violates the API contract and fatally breaks the `camss` driver probe on SM8250.
- [Low] The modifications to the `camss` node violate the `qcom,sm8250-camss.yaml` binding schema, resulting in DT validation failures.
--
commit 28e11fda34f9237ee15cc0f987e7147787f608e8
Author: Atanas Filipov <atanas.filipov@oss.qualcomm.com>
arm64: dts: qcom: sm8250: Add JPEG encoder node
Add the JPEG encoder hardware node to the SM8250 device tree so the
qcom-jpeg V4L2 encoder driver can bind and operate on this platform.
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index 7076720413ab2..d0cacb4ec35bb 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -4472,6 +4472,9 @@ cci1_i2c1: i2c-bus@1 {
> camss: camss@ac6a000 {
> compatible = "qcom,sm8250-camss";
> status = "disabled";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
[Severity: Low]
Does adding these new properties and the jpeg-encoder child node cause device
tree validation failures?
The qcom,sm8250-camss.yaml schema uses additionalProperties: false and does
not appear to currently document these new properties or the child node. This
might cause make dtbs_check to complain about unapproved properties.
[ ... ]
> - interconnect-names = "cam_ahb",
> - "cam_hf_0_mnoc",
> - "cam_sf_0_mnoc",
> - "cam_sf_icp_mnoc";
> + interconnect-names = "ahb",
> + "hf_mnoc",
> + "sf_mnoc",
> + "icp_mnoc";
[Severity: High]
Will renaming these interconnect-names break the camera subsystem probe on
SM8250?
The camss driver expects the original names to be present. During boot,
camss_probe() calls camss_icc_get(), which searches for names hardcoded
in icc_res_sm8250:
drivers/media/platform/qcom/camss/camss.c:
static const struct resources_icc icc_res_sm8250[] = {
{ .name = "cam_ahb", },
...
If devm_of_icc_get() searches for "cam_ahb" but the device tree provides
"ahb", the lookup will return -EINVAL and cause the probe to abort.
Additionally, does renaming these properties violate the allowed items list
in qcom,sm8250-camss.yaml?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629121750.3469292-1-atanas.filipov@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-06-29 12:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:17 [PATCH v3 0/4] Add Qualcomm JPEG V4L2 encoder for SM8250 Atanas Filipov
2026-06-29 12:17 ` [PATCH v3 1/4] media: qcom: camss: populate child platform devices Atanas Filipov
2026-06-29 12:30 ` sashiko-bot
2026-06-29 13:41 ` Vladimir Zapolskiy
2026-06-29 12:17 ` [PATCH v3 2/4] dt-bindings: media: qcom: Add JPEG encoder binding Atanas Filipov
2026-06-29 12:25 ` sashiko-bot
2026-06-29 12:58 ` Dmitry Baryshkov
2026-06-29 13:38 ` Vladimir Zapolskiy
2026-06-30 13:19 ` Bryan O'Donoghue
2026-06-30 13:32 ` Vladimir Zapolskiy
2026-06-30 20:24 ` Bryan O'Donoghue
2026-06-30 21:02 ` Vladimir Zapolskiy
2026-06-29 13:41 ` Rob Herring (Arm)
2026-06-29 12:17 ` [PATCH v3 3/4] arm64: dts: qcom: sm8250: Add JPEG encoder node Atanas Filipov
2026-06-29 12:34 ` sashiko-bot [this message]
2026-06-29 13:02 ` Dmitry Baryshkov
2026-06-29 12:17 ` [PATCH v3 4/4] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder Atanas Filipov
2026-06-29 12:46 ` sashiko-bot
2026-06-29 13:48 ` Bryan O'Donoghue
2026-06-29 13:50 ` Bryan O'Donoghue
2026-06-30 9:13 ` Konrad Dybcio
2026-06-30 13:06 ` Dmitry Baryshkov
2026-06-30 14:14 ` Atanas Filipov
2026-07-01 0:13 ` Dmitry Baryshkov
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=20260629123455.009A21F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=atanas.filipov@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 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.