From: sashiko-bot@kernel.org
To: "Shashank Maurya" <shashank.maurya@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: lemans-evk: Add Raspberry Pi 7-inch DSI panel overlay
Date: Mon, 07 Sep 2026 06:44:02 +0000 [thread overview]
Message-ID: <20260907064402.9954B1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907-rpi_dts_overlay-v2-2-a4989322ce00@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] Downstream-only I2C properties (`qcom,load-firmware` and `qcom,xfer-mode`) are leaked into the upstream device tree.
- [Low] The panel node is missing the mandatory fallback compatible for the ILI9881c driver.
- [Low] The regulator MCU node uses an invalid node name and includes an unsupported vcc-supply property.
--
commit c29fa706b8fbecd36dcc880f57d516cffcc9f530
Author: Shashank Maurya <shashank.maurya@oss.qualcomm.com>
arm64: dts: qcom: lemans-evk: Add Raspberry Pi 7-inch DSI panel overlay
This commit adds a device tree overlay for the Raspberry Pi 7" DSI touchscreen
panel on Lemans EVK. It configures mdss0_dsi0 with 2 data lanes and adds the
panel MCU on I2C1.
> diff --git a/arch/arm64/boot/dts/qcom/lemans-evk-raspberrypi-dsi-7inch.dtso b/arch/arm64/boot/dts/qcom/lemans-evk-raspberrypi-dsi-7inch.dtso
> new file mode 100644
> index 0000000000000..14743b3c38637
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/lemans-evk-raspberrypi-dsi-7inch.dtso
[ ... ]
> +&i2c1 {
> + qcom,load-firmware;
> + qcom,xfer-mode = <1>;
[Severity: Low]
Are these downstream I2C properties intended to be included in the upstream
device tree?
They do not exist in the upstream devicetree bindings and are not parsed by
mainline drivers, which will cause schema validation errors during make
dtbs_check.
> +
> + status = "okay";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + reg_backlight: reg_backlight@45 {
[Severity: Low]
Does this node name violate the expected naming convention?
It seems it should match the ^regulator(@.*)?$ pattern inherited from
regulator.yaml to avoid dtbs_check schema validation errors.
> + compatible = "raspberrypi,touchscreen-panel-regulator-v2";
> + reg = <0x45>;
> +
> + vcc-supply = <®_dsi_touch>;
[Severity: Low]
Is this vcc-supply property supported by the binding?
The raspberrypi,7inch-touchscreen-panel-regulator-v2.yaml specifies
additionalProperties: false and does not define vcc-supply. Since the panel
explicitly enables reg_dsi_touch anyway, should this be removed to pass
schema validation?
> + gpio-controller;
> + #gpio-cells = <2>;
> + #pwm-cells = <3>;
> + };
> +};
> +
> +&mdss0_dsi0 {
> + vdda-supply = <&vreg_l1c>;
> +
> + status = "okay";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + panel@0 {
> + compatible = "raspberrypi,dsi-7inch";
[Severity: Low]
Is this missing the mandatory fallback compatible for the ILI9881c driver?
According to Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml,
this should be an array of two strings containing the specific panel and the
fallback ilitek,ili9881c.
> + reg = <0>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260907-rpi_dts_overlay-v2-0-a4989322ce00@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-09-07 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:33 [PATCH v2 0/2] arm64: dts: qcom: Add RPi 7-inch DSI panel overlays for Monaco/Lemans EVK Shashank Maurya
2026-09-07 6:33 ` [PATCH v2 1/2] arm64: dts: qcom: monaco-evk: Add Raspberry Pi 7-inch DSI panel overlay Shashank Maurya
2026-09-07 6:47 ` sashiko-bot
2026-09-09 14:50 ` Konrad Dybcio
2026-09-22 6:18 ` Shashank Maurya
2026-09-09 14:51 ` Konrad Dybcio
2026-09-22 6:17 ` Shashank Maurya
2026-09-07 6:33 ` [PATCH v2 2/2] arm64: dts: qcom: lemans-evk: " Shashank Maurya
2026-09-07 6:44 ` sashiko-bot [this message]
2026-09-10 19:35 ` [PATCH v2 0/2] arm64: dts: qcom: Add RPi 7-inch DSI panel overlays for Monaco/Lemans EVK Bjorn Andersson
2026-09-17 5:34 ` Shashank Maurya
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=20260907064402.9954B1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shashank.maurya@oss.qualcomm.com \
/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.