The FCP instances associated with a VSPI must be treated differently than the ones associated with another type of VSP. Add a new compatible string to allow telling them apart. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> --- Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt b/Documentation/devicetree/bindings/media/renesas,fcp.txt index 3ec91803ba58..c1f28736e2d6 100644 --- a/Documentation/devicetree/bindings/media/renesas,fcp.txt +++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt @@ -11,7 +11,8 @@ are paired with. These DT bindings currently support the FCPV and FCPF. - compatible: Must be one or more of the following - - "renesas,fcpv" for generic compatible 'FCP for VSP' + - "renesas,fcpvi" for generic compatible 'FCP for VSPI' + - "renesas,fcpv" for generic compatible 'FCP for VSP' (all other VSPs) - "renesas,fcpf" for generic compatible 'FCP for FDP' - reg: the register base and size for the device registers -- Regards, Laurent Pinchart