Commit a733c811 authored by Laurent Pinchart's avatar Laurent Pinchart Committed by Simon Horman
Browse files

dt-bindings: media: renesas-fcp: Remove SoC-specific compatible strings 



The FCP IP cores include a version register that identifies which SoC
model the IP is integrated in. SoC-specific compatible strings are not
needed.

Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
parent ea3c17b0

Documentation/devicetree/bindings/media/renesas,fcp.txt

+1 −7
Original line number Diff line number Diff line
@@ -11,15 +11,9 @@ are paired with. These DT bindings currently support the FCPV and FCPF. 


 - compatible: Must be one or more of the following



   - "renesas,r8a7795-fcpv" for R8A7795 (R-Car H3) compatible 'FCP for VSP'

   - "renesas,r8a7795-fcpf" for R8A7795 (R-Car H3) compatible 'FCP for FDP'

   - "renesas,fcpv" for generic compatible 'FCP for VSP'

   - "renesas,fcpf" for generic compatible 'FCP for FDP'



   When compatible with the generic version, nodes must list the

   SoC-specific version corresponding to the platform first, followed by the

   family-specific and/or generic versions.



 - reg: the register base and size for the device registers

 - clocks: Reference to the functional clock
@@ -32,7 +26,7 @@ Device node example 
-------------------



	fcpvd1: fcp@fea2f000 {

		compatible = "renesas,r8a7795-fcpv", "renesas,fcpv";

		compatible = "renesas,fcpv";

		reg = <0 0xfea2f000 0 0x200>;

		clocks = <&cpg CPG_MOD 602>;

		power-domains = <&sysc R8A7795_PD_A3VP>;

CRA Git | Maintained and supported by SUSTech CRA and CCSE