From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> To: dri-devel@lists.freedesktop.org Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Rob Herring <robh+dt@kernel.org> Subject: [PATCH 1/8] dt-bindings: media: renesas,fcp: Convert binding to YAML Date: Fri, 15 May 2020 04:24:25 +0300 [thread overview] Message-ID: <20200515012432.31326-2-laurent.pinchart+renesas@ideasonboard.com> (raw) In-Reply-To: <20200515012432.31326-1-laurent.pinchart+renesas@ideasonboard.com> Convert the Renesas R-Car FCP text binding to YAML. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> --- .../devicetree/bindings/media/renesas,fcp.txt | 34 ----------- .../bindings/media/renesas,fcp.yaml | 56 +++++++++++++++++++ 2 files changed, 56 insertions(+), 34 deletions(-) delete mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.txt create mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.yaml diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt b/Documentation/devicetree/bindings/media/renesas,fcp.txt deleted file mode 100644 index 79c37395b396..000000000000 --- a/Documentation/devicetree/bindings/media/renesas,fcp.txt +++ /dev/null @@ -1,34 +0,0 @@ -Renesas R-Car Frame Compression Processor (FCP) ------------------------------------------------ - -The FCP is a companion module of video processing modules in the Renesas R-Car -Gen3 and RZ/G2 SoCs. It provides data compression and decompression, data -caching, and conversion of AXI transactions in order to reduce the memory -bandwidth. - -There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and FCP -for FDP (FCPF). Their configuration and behaviour depend on the module they -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,fcpf" for generic compatible 'FCP for FDP' - - - reg: the register base and size for the device registers - - clocks: Reference to the functional clock - -Optional properties: - - power-domains : power-domain property defined with a power domain specifier - to respective power domain. - - -Device node example -------------------- - - fcpvd1: fcp@fea2f000 { - compatible = "renesas,fcpv"; - reg = <0 0xfea2f000 0 0x200>; - clocks = <&cpg CPG_MOD 602>; - power-domains = <&sysc R8A7795_PD_A3VP>; - }; diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.yaml b/Documentation/devicetree/bindings/media/renesas,fcp.yaml new file mode 100644 index 000000000000..be085fb398fd --- /dev/null +++ b/Documentation/devicetree/bindings/media/renesas,fcp.yaml @@ -0,0 +1,56 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/media/renesas,fcp.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Renesas R-Car Frame Compression Processor (FCP) + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The FCP is a companion module of video processing modules in the Renesas + R-Car Gen3 and RZ/G2 SoCs. It provides data compression and decompression, + data caching, and conversion of AXI transactions in order to reduce the + memory bandwidth. + + There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and + FCP for FDP (FCPF). Their configuration and behaviour depend on the module + they are paired with. These DT bindings currently support the FCPV and FCPF. + +properties: + compatible: + enum: + - renesas,fcpv # for 'FCP for VSP' + - renesas,fcpf # for 'FCP for FDP' + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + power-domains: + maxItems: 1 + +required: + - compatible + - reg + - clocks + +additionalProperties: false + +examples: + # R8A7790 (R-Car H2) VSP1-S + - | + #include <dt-bindings/clock/renesas-cpg-mssr.h> + #include <dt-bindings/power/r8a7795-sysc.h> + + fcp@fea2f000 { + compatible = "renesas,fcpv"; + reg = <0xfea2f000 0x200>; + clocks = <&cpg CPG_MOD 602>; + power-domains = <&sysc R8A7795_PD_ALWAYS_ON>; + }; +... -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> To: dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, linux-media@vger.kernel.org Subject: [PATCH 1/8] dt-bindings: media: renesas,fcp: Convert binding to YAML Date: Fri, 15 May 2020 04:24:25 +0300 [thread overview] Message-ID: <20200515012432.31326-2-laurent.pinchart+renesas@ideasonboard.com> (raw) In-Reply-To: <20200515012432.31326-1-laurent.pinchart+renesas@ideasonboard.com> Convert the Renesas R-Car FCP text binding to YAML. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> --- .../devicetree/bindings/media/renesas,fcp.txt | 34 ----------- .../bindings/media/renesas,fcp.yaml | 56 +++++++++++++++++++ 2 files changed, 56 insertions(+), 34 deletions(-) delete mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.txt create mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.yaml diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.txt b/Documentation/devicetree/bindings/media/renesas,fcp.txt deleted file mode 100644 index 79c37395b396..000000000000 --- a/Documentation/devicetree/bindings/media/renesas,fcp.txt +++ /dev/null @@ -1,34 +0,0 @@ -Renesas R-Car Frame Compression Processor (FCP) ------------------------------------------------ - -The FCP is a companion module of video processing modules in the Renesas R-Car -Gen3 and RZ/G2 SoCs. It provides data compression and decompression, data -caching, and conversion of AXI transactions in order to reduce the memory -bandwidth. - -There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and FCP -for FDP (FCPF). Their configuration and behaviour depend on the module they -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,fcpf" for generic compatible 'FCP for FDP' - - - reg: the register base and size for the device registers - - clocks: Reference to the functional clock - -Optional properties: - - power-domains : power-domain property defined with a power domain specifier - to respective power domain. - - -Device node example -------------------- - - fcpvd1: fcp@fea2f000 { - compatible = "renesas,fcpv"; - reg = <0 0xfea2f000 0 0x200>; - clocks = <&cpg CPG_MOD 602>; - power-domains = <&sysc R8A7795_PD_A3VP>; - }; diff --git a/Documentation/devicetree/bindings/media/renesas,fcp.yaml b/Documentation/devicetree/bindings/media/renesas,fcp.yaml new file mode 100644 index 000000000000..be085fb398fd --- /dev/null +++ b/Documentation/devicetree/bindings/media/renesas,fcp.yaml @@ -0,0 +1,56 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/media/renesas,fcp.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Renesas R-Car Frame Compression Processor (FCP) + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The FCP is a companion module of video processing modules in the Renesas + R-Car Gen3 and RZ/G2 SoCs. It provides data compression and decompression, + data caching, and conversion of AXI transactions in order to reduce the + memory bandwidth. + + There are three types of FCP: FCP for Codec (FCPC), FCP for VSP (FCPV) and + FCP for FDP (FCPF). Their configuration and behaviour depend on the module + they are paired with. These DT bindings currently support the FCPV and FCPF. + +properties: + compatible: + enum: + - renesas,fcpv # for 'FCP for VSP' + - renesas,fcpf # for 'FCP for FDP' + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + power-domains: + maxItems: 1 + +required: + - compatible + - reg + - clocks + +additionalProperties: false + +examples: + # R8A7790 (R-Car H2) VSP1-S + - | + #include <dt-bindings/clock/renesas-cpg-mssr.h> + #include <dt-bindings/power/r8a7795-sysc.h> + + fcp@fea2f000 { + compatible = "renesas,fcpv"; + reg = <0xfea2f000 0x200>; + clocks = <&cpg CPG_MOD 602>; + power-domains = <&sysc R8A7795_PD_ALWAYS_ON>; + }; +... -- Regards, Laurent Pinchart _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-15 1:24 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-15 1:24 [PATCH 0/8] d-bindings: media: Conversion of Renesas bindings to YAML Laurent Pinchart 2020-05-15 1:24 ` Laurent Pinchart 2020-05-15 1:24 ` Laurent Pinchart [this message] 2020-05-15 1:24 ` [PATCH 1/8] dt-bindings: media: renesas,fcp: Convert binding " Laurent Pinchart 2020-05-15 8:05 ` Geert Uytterhoeven 2020-05-15 8:05 ` [PATCH 1/8] dt-bindings: media: renesas, fcp: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 2/8] dt-bindings: media: renesas,fcp: Make power-domains mandatory Laurent Pinchart 2020-05-15 1:24 ` [PATCH 2/8] dt-bindings: media: renesas, fcp: " Laurent Pinchart 2020-05-15 7:52 ` [PATCH 2/8] dt-bindings: media: renesas,fcp: " Geert Uytterhoeven 2020-05-15 7:52 ` [PATCH 2/8] dt-bindings: media: renesas, fcp: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 3/8] dt-bindings: media: renesas,fcp: Add resets and iommus properties Laurent Pinchart 2020-05-15 1:24 ` [PATCH 3/8] dt-bindings: media: renesas, fcp: " Laurent Pinchart 2020-05-15 8:01 ` [PATCH 3/8] dt-bindings: media: renesas,fcp: " Geert Uytterhoeven 2020-05-15 8:01 ` Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 4/8] dt-bindings: media: renesas,fdp1: Convert binding to YAML Laurent Pinchart 2020-05-15 1:24 ` [PATCH 4/8] dt-bindings: media: renesas, fdp1: " Laurent Pinchart 2020-05-15 8:07 ` [PATCH 4/8] dt-bindings: media: renesas,fdp1: " Geert Uytterhoeven 2020-05-15 8:07 ` [PATCH 4/8] dt-bindings: media: renesas, fdp1: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 5/8] dt-bindings: media: renesas,fdp1: Make power-domains mandatory Laurent Pinchart 2020-05-15 1:24 ` [PATCH 5/8] dt-bindings: media: renesas, fdp1: " Laurent Pinchart 2020-05-15 8:00 ` [PATCH 5/8] dt-bindings: media: renesas,fdp1: " Geert Uytterhoeven 2020-05-15 8:00 ` [PATCH 5/8] dt-bindings: media: renesas, fdp1: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 6/8] dt-bindings: media: renesas,fdp1: Add resets property Laurent Pinchart 2020-05-15 1:24 ` Laurent Pinchart 2020-05-15 8:02 ` Geert Uytterhoeven 2020-05-15 8:02 ` [PATCH 6/8] dt-bindings: media: renesas, fdp1: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 7/8] dt-bindings: media: renesas,vsp1: Convert binding to YAML Laurent Pinchart 2020-05-15 1:24 ` [PATCH 7/8] dt-bindings: media: renesas, vsp1: " Laurent Pinchart 2020-05-15 8:10 ` [PATCH 7/8] dt-bindings: media: renesas,vsp1: " Geert Uytterhoeven 2020-05-15 8:10 ` [PATCH 7/8] dt-bindings: media: renesas, vsp1: " Geert Uytterhoeven 2020-05-15 1:24 ` [PATCH 8/8] dt-bindings: media: renesas,vsp1: Add power-domains and resets Laurent Pinchart 2020-05-15 1:24 ` [PATCH 8/8] dt-bindings: media: renesas, vsp1: " Laurent Pinchart 2020-05-15 8:03 ` [PATCH 8/8] dt-bindings: media: renesas,vsp1: " Geert Uytterhoeven 2020-05-15 8:03 ` Geert Uytterhoeven
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=20200515012432.31326-2-laurent.pinchart+renesas@ideasonboard.com \ --to=laurent.pinchart+renesas@ideasonboard.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=robh+dt@kernel.org \ /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: linkBe 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.