From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: stanimir.varbanov@linaro.org, agross@kernel.org,
bjorn.andersson@linaro.org, mchehab@kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: dt-bindings: media: venus: Add sdm660 DT schema
Date: Tue, 19 Jan 2021 17:17:09 -0600 [thread overview]
Message-ID: <20210119231709.GA2775697@robh.at.kernel.org> (raw)
In-Reply-To: <20210115185252.333562-3-angelogioacchino.delregno@somainline.org>
On Fri, Jan 15, 2021 at 07:52:52PM +0100, AngeloGioacchino Del Regno wrote:
> Add new qcom,sdm660-venus DT binding schema.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
> ---
> .../bindings/media/qcom,sdm660-venus.yaml | 164 ++++++++++++++++++
> 1 file changed, 164 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml
>
> base-commit: 012bd807cf654b992cdc4db7eab85c1e95f9d571
> prerequisite-patch-id: 734bdefdb043a8f91a48916246cc9a36fb5966e5
> prerequisite-patch-id: 999517c02973237996492a41ed5bfc2990083932
> prerequisite-patch-id: a48910425fac61948a7a26bec4d40d63e3368569
> prerequisite-patch-id: b1a1a4216eed0d04dd16e6e8e1053dee185d06d8
> prerequisite-patch-id: dff12be2631cc21ef1c3c930fba49d979f5055fe
>
> diff --git a/Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml b/Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml
> new file mode 100644
> index 000000000000..e7568d4007af
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml
> @@ -0,0 +1,164 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/media/qcom,sdm660-venus.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Qualcomm Venus video encode and decode accelerators
> +
> +maintainers:
> + - Stanimir Varbanov <stanimir.varbanov@linaro.org>
> +
> +description: |
> + The Venus IP is a video encode and decode accelerator present
> + on Qualcomm platforms
> +
> +properties:
> + compatible:
> + const: qcom,sdm660-venus
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 5
> +
> + clock-names:
> + items:
> + - const: core
> + - const: iface
> + - const: bus
> + - const: bus_throttle
> + - const: vcodec0_core
> +
> + interconnects:
> + maxItems: 2
> +
> + interconnect-names:
> + items:
> + - const: video-mem
> + - const: cpu-cfg
> +
> + iommus:
> + maxItems: 20
Perhaps some explanation as to what all these are. Looks like it is just
1 iommu, but lots of ids?
> +
> + memory-region:
> + maxItems: 1
> +
> + power-domains:
> + minItems: 3
> +
> + power-domain-names:
> + items:
> + - const: cx
> + - const: vcodec0
> + - const: venus
> +
> + video-decoder:
> + type: object
> +
> + properties:
> + compatible:
> + const: venus-decoder
> +
> + required:
> + - compatible
> +
> + additionalProperties: false
> +
> + video-encoder:
> + type: object
> +
> + properties:
> + compatible:
> + const: venus-encoder
> +
> + required:
> + - compatible
> +
> + additionalProperties: false
> +
> + video-firmware:
> + type: object
> +
> + description: |
> + Firmware subnode is needed when the platform does not
> + have TrustZone.
> +
> + properties:
> + iommus:
> + maxItems: 2
> +
> + required:
> + - iommus
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - power-domains
> + - power-domain-names
> + - clocks
> + - clock-names
> + - iommus
> + - memory-region
> + - video-decoder
> + - video-encoder
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/qcom,mmcc-sdm660.h>
> + #include <dt-bindings/power/qcom-rpmpd.h>
> +
> + video-codec@cc00000 {
> + compatible = "qcom,sdm660-venus";
> + reg = <0x0cc00000 0xff000>;
> + interrupts = <GIC_SPI 287 IRQ_TYPE_LEVEL_HIGH>;
> + power-domains = <&rpmpd SDM660_VDDCX>,
> + <&mmcc VENUS_CORE0_GDSC>,
> + <&mmcc VENUS_GDSC>;
> + power-domain-names = "cx", "vcodec0", "venus";
> + clocks = <&mmcc VIDEO_CORE_CLK>,
> + <&mmcc VIDEO_AHB_CLK>,
> + <&mmcc VIDEO_AXI_CLK>,
> + <&mmcc THROTTLE_VIDEO_AXI_CLK>,
> + <&mmcc VIDEO_SUBCORE0_CLK>;
> + clock-names = "core", "iface", "bus", "bus_throttle",
> + "vcodec0_core";
> + iommus = <&mmss_smmu 0x400>,
> + <&mmss_smmu 0x401>,
> + <&mmss_smmu 0x40a>,
> + <&mmss_smmu 0x407>,
> + <&mmss_smmu 0x40e>,
> + <&mmss_smmu 0x40f>,
> + <&mmss_smmu 0x408>,
> + <&mmss_smmu 0x409>,
> + <&mmss_smmu 0x40b>,
> + <&mmss_smmu 0x40c>,
> + <&mmss_smmu 0x40d>,
> + <&mmss_smmu 0x410>,
> + <&mmss_smmu 0x421>,
> + <&mmss_smmu 0x428>,
> + <&mmss_smmu 0x429>,
> + <&mmss_smmu 0x42b>,
> + <&mmss_smmu 0x42c>,
> + <&mmss_smmu 0x42d>,
> + <&mmss_smmu 0x411>,
> + <&mmss_smmu 0x431>;
> + memory-region = <&venus_region>;
> +
> + video-decoder {
> + compatible = "venus-decoder";
> + };
> +
> + video-encoder {
> + compatible = "venus-encoder";
> + };
> + };
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-01-19 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 18:52 [PATCH 0/2] SDM630/660 Venus hardware video decoder/encoder AngeloGioacchino Del Regno
2021-01-15 18:52 ` [PATCH 1/2] media: venus: core: Add sdm660 DT compatible and resource struct AngeloGioacchino Del Regno
2021-01-18 17:21 ` Stanimir Varbanov
2021-01-18 17:45 ` AngeloGioacchino Del Regno
2021-01-25 10:40 ` Hans Verkuil
2021-01-25 14:51 ` AngeloGioacchino Del Regno
2021-01-25 15:01 ` Hans Verkuil
2021-01-26 8:44 ` Stanimir Varbanov
2021-01-25 15:18 ` Bjorn Andersson
2021-01-15 18:52 ` [PATCH 2/2] media: dt-bindings: media: venus: Add sdm660 DT schema AngeloGioacchino Del Regno
2021-01-17 15:45 ` Rob Herring
2021-01-17 19:23 ` AngeloGioacchino Del Regno
2021-01-18 17:21 ` Stanimir Varbanov
2021-01-18 17:48 ` AngeloGioacchino Del Regno
2021-01-19 23:17 ` Rob Herring [this message]
2021-01-19 23:19 ` AngeloGioacchino Del Regno
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=20210119231709.GA2775697@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mchehab@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=stanimir.varbanov@linaro.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).