Re: [PATCH v3 1/3] arm64: dts: qcom: lemans-evk: Add LVDS display overlay

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing Driver Support / Undocumented Compatible Strings
--

commit 78dfb1b1aa86e3fb2e9b0abac38907b8140f5130
Author: Vishnu Saini <vishnu.saini@oss.qualcomm.com>

arm64: dts: qcom: lemans-evk: Add LVDS display overlay

This commit adds a device tree overlay for the Lemans EVK IFP mezzanine to
support LVDS display output. It configures the LT9211C DSI-to-LVDS bridge and
a BOE dv215fhm-r01 panel.

> diff --git a/arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso b/arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso
> new file mode 100644
> index 0000000000000..bd3e13c46a1e7
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso
[ ... ]
> +&{/} {
> +	model = "Qualcomm Technologies, Inc. Lemans EVK LVDS";
> +
> +	panel_lvds: panel-lvds {
> +		compatible = "boe,dv215fhm-r01";

[Severity: Medium]
Will the panel_lvds node probe successfully during boot? 

The compatible string "boe,dv215fhm-r01" in
arch/arm64/boot/dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso appears to be
undocumented and unsupported by the panel-simple driver. Because there is no
generic fallback (such as "panel-lvds") with explicitly supplied timings, the
driver core will not find a matching OF entry and the binding will fail
deterministically.

Could a generic fallback be added, or does this compatible string need to be
added to the driver bindings first?

> +		power-supply = <&lcd_disp_bias>;
[ ... ]
> +&i2c1 {
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&qup_i2c1_default>;
> +
> +	status = "okay";
> +
> +	lt9211c_codec: lvds-bridge@2d {
> +		compatible = "lontium,lt9211c";

[Severity: Medium]
Is it expected that the lt9211c_codec bridge device lacks a driver match?

Similar to the panel node above, the compatible string "lontium,lt9211c" is
undocumented and not supported by the existing lontium-lt9211 driver. Without
a matching driver entry or a generic fallback like "lontium,lt9211", the
bridge will not probe, leaving the display pipeline uninitialized.

Does the lontium-lt9211 driver need to be updated to match this compatible, or
should this node include a generic fallback?

> +		reg = <0x2d>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260905-lvds-support-v3-0-b40a1b03f63c@oss.qualcomm.com?part=1