From: Guoniu Zhou Date: Tue, 19 May 2026 02:07:42 +0000 (+0800) Subject: media: dt-bindings: add NXP i.MX95 compatible string X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=113423645c9363acdb03859c65b5b030ae9ddd43;p=thirdparty%2Fkernel%2Flinux.git media: dt-bindings: add NXP i.MX95 compatible string The i.MX95 CSI-2 controller is nearly identical to i.MX93, with the main difference being the data output interface: i.MX93 use IPI (Image Pixel Interface), which requires: - Pixel clock input - Software configuration through registers i.MX95 uses IDI (Image Data Interface), which: - Does not require pixel clock - Is software transparent (no register configuration needed) Due to these differences in register layout and initialization needs, the two variants cannot share the same compatible string. The driver needs to distinguish between them to handle the interface correctly. Reviewed-by: Krzysztof Kozlowski Reviewed-by: Frank Li Signed-off-by: Guoniu Zhou Signed-off-by: Sakari Ailus --- diff --git a/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml index fbcf28e9e1da..8bfad0fca3b7 100644 --- a/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml +++ b/Documentation/devicetree/bindings/media/rockchip,rk3568-mipi-csi2.yaml @@ -19,6 +19,7 @@ properties: oneOf: - enum: - fsl,imx93-mipi-csi2 + - fsl,imx95-mipi-csi2 - rockchip,rk3568-mipi-csi2 - items: - enum: @@ -140,6 +141,21 @@ allOf: clock-names: minItems: 2 + - if: + properties: + compatible: + contains: + const: fsl,imx95-mipi-csi2 + then: + properties: + interrupts: + maxItems: 1 + interrupt-names: false + clocks: + maxItems: 1 + clock-names: + maxItems: 1 + examples: - | #include