From: Rob Herring <robh@kernel.org>
To: Irui Wang <irui.wang@mediatek.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tzung-Bi Shih <tzungbi@chromium.org>,
angelogioacchino.delregno@collabora.com,
nicolas.dufresne@collabora.com, wenst@chromium.org,
kyrie wu <kyrie.wu@mediatek.com>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Tomasz Figa <tfiga@chromium.org>,
xia.jiang@mediatek.com, maoguang.meng@mediatek.com
Subject: Re: [V6,1/8] dt-bindings: mediatek: Add mediatek,mt8195-jpgdec compatible
Date: Tue, 16 Aug 2022 10:26:05 -0600 [thread overview]
Message-ID: <20220816162605.GA2315090-robh@kernel.org> (raw)
In-Reply-To: <20220729062603.5533-2-irui.wang@mediatek.com>
On Fri, Jul 29, 2022 at 02:25:56PM +0800, Irui Wang wrote:
> From: kyrie wu <kyrie.wu@mediatek.com>
>
> Add mediatek,mt8195-jpgdec compatible to binding document.
>
> Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> Signed-off-by: irui wang <irui.wang@mediatek.com>
> ---
> .../media/mediatek,mt8195-jpegdec.yaml | 160 ++++++++++++++++++
> 1 file changed, 160 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml b/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml
> new file mode 100644
> index 000000000000..ebda0ade8153
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml
> @@ -0,0 +1,160 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/mediatek,mt8195-jpegdec.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek JPEG Encoder Device Tree Bindings
> +
> +maintainers:
> + - kyrie wu <kyrie.wu@mediatek.corp-partner.google.com>
> +
> +description:
> + MediaTek JPEG Decoder is the JPEG decode hardware present in MediaTek SoCs
> +
> +properties:
> + compatible:
> + items:
> + - const: mediatek,mt8195-jpgdec
> +
> + power-domains:
> + maxItems: 1
> +
> + iommus:
> + maxItems: 6
> + description:
> + Points to the respective IOMMU block with master port as argument, see
> + Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
> + Ports are according to the HW.
> +
> + "#address-cells":
> + const: 2
> +
> + "#size-cells":
> + const: 2
> +
> + ranges: true
> +
> +# Required child node:
> +patternProperties:
> + "^jpgdec@[0-9a-f]+$":
> + type: object
> + description:
> + The jpeg decoder hardware device node which should be added as subnodes to
> + the main jpeg node.
> +
> + properties:
> + compatible:
> + const: mediatek,mt8195-jpgdec-hw
> +
> + reg:
> + maxItems: 1
> +
> + iommus:
> + minItems: 1
> + maxItems: 32
> + description:
> + List of the hardware port in respective IOMMU block for current Socs.
> + Refer to bindings/iommu/mediatek,iommu.yaml.
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: jpgdec
> +
> + power-domains:
> + maxItems: 1
> +
> + required:
> + - compatible
> + - reg
> + - iommus
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> +
> + additionalProperties: false
> +
> +required:
> + - compatible
> + - power-domains
> + - iommus
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/memory/mt8195-memory-port.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/clock/mt8195-clk.h>
> + #include <dt-bindings/power/mt8195-power.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + jpgdec_master {
> + compatible = "mediatek,mt8195-jpgdec";
> + power-domains = <&spm MT8195_POWER_DOMAIN_VDEC1>;
> + iommus = <&iommu_vpp M4U_PORT_L19_JPGDEC_WDMA0>,
> + <&iommu_vpp M4U_PORT_L19_JPGDEC_BSDMA0>,
> + <&iommu_vpp M4U_PORT_L19_JPGDEC_WDMA1>,
> + <&iommu_vpp M4U_PORT_L19_JPGDEC_BSDMA1>,
> + <&iommu_vpp M4U_PORT_L19_JPGDEC_BUFF_OFFSET1>,
> + <&iommu_vpp M4U_PORT_L19_JPGDEC_BUFF_OFFSET0>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
Missing ranges.
Presumably at least 1 child node is required because there's no 'reg'
property in the parent to access the h/w. So 'ranges', "#address-cells',
and '#size-cells' should all be required.
> + jpgdec@1a040000 {
> + compatible = "mediatek,mt8195-jpgdec-hw";
> + reg = <0 0x1a040000 0 0x10000>;/* JPGDEC_C0 */
> + iommus = <&iommu_vdo M4U_PORT_L19_JPGDEC_WDMA0>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BSDMA0>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_WDMA1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BSDMA1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BUFF_OFFSET1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BUFF_OFFSET0>;
> + interrupts = <GIC_SPI 343 IRQ_TYPE_LEVEL_HIGH 0>;
> + clocks = <&vencsys CLK_VENC_JPGDEC>;
> + clock-names = "jpgdec";
> + power-domains = <&spm MT8195_POWER_DOMAIN_VDEC0>;
> + };
> +
> + jpgdec@1a050000 {
> + compatible = "mediatek,mt8195-jpgdec-hw";
> + reg = <0 0x1a050000 0 0x10000>;/* JPGDEC_C1 */
> + iommus = <&iommu_vdo M4U_PORT_L19_JPGDEC_WDMA0>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BSDMA0>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_WDMA1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BSDMA1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BUFF_OFFSET1>,
> + <&iommu_vdo M4U_PORT_L19_JPGDEC_BUFF_OFFSET0>;
> + interrupts = <GIC_SPI 344 IRQ_TYPE_LEVEL_HIGH 0>;
> + clocks = <&vencsys CLK_VENC_JPGDEC_C1>;
> + clock-names = "jpgdec";
> + power-domains = <&spm MT8195_POWER_DOMAIN_VDEC1>;
> + };
> +
> + jpgdec@1b040000 {
> + compatible = "mediatek,mt8195-jpgdec-hw";
> + reg = <0 0x1b040000 0 0x10000>;/* JPGDEC_C2 */
> + iommus = <&iommu_vpp M4U_PORT_L20_JPGDEC_WDMA0>,
> + <&iommu_vpp M4U_PORT_L20_JPGDEC_BSDMA0>,
> + <&iommu_vpp M4U_PORT_L20_JPGDEC_WDMA1>,
> + <&iommu_vpp M4U_PORT_L20_JPGDEC_BSDMA1>,
> + <&iommu_vpp M4U_PORT_L20_JPGDEC_BUFF_OFFSET1>,
> + <&iommu_vpp M4U_PORT_L20_JPGDEC_BUFF_OFFSET0>;
> + interrupts = <GIC_SPI 348 IRQ_TYPE_LEVEL_HIGH 0>;
> + clocks = <&vencsys_core1 CLK_VENC_CORE1_JPGDEC>;
> + clock-names = "jpgdec";
> + power-domains = <&spm MT8195_POWER_DOMAIN_VDEC2>;
> + };
> + };
> + };
> --
> 2.18.0
>
>
next prev parent reply other threads:[~2022-08-16 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 6:25 [V6,0/8] Support multi-hardware jpeg decoder for MT8195 Irui Wang
2022-07-29 6:25 ` [V6,1/8] dt-bindings: mediatek: Add mediatek,mt8195-jpgdec compatible Irui Wang
2022-08-16 16:26 ` Rob Herring [this message]
2022-07-29 6:25 ` [V6,2/8] media: mtk-jpegdec: export jpeg decoder functions Irui Wang
2022-07-29 6:25 ` [V6,3/8] media: mtk-jpegdec: manage jpegdec multi-hardware Irui Wang
2022-07-29 6:25 ` [V6,4/8] media: mtk-jpegdec: add jpegdec timeout func interface Irui Wang
2022-07-29 6:26 ` [V6,5/8] media: mtk-jpegdec: add jpeg decode worker interface Irui Wang
2022-07-29 6:26 ` [V6,6/8] media: mtk-jpegdec: add output pic reorder interface Irui Wang
2022-07-29 6:26 ` [V6,7/8] media: mtk-jpegdec: refactor jpegdec func interface Irui Wang
2022-07-29 6:26 ` [V6,8/8] mtk-jpegdec: add stop cmd interface for jpgdec Irui Wang
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=20220816162605.GA2315090-robh@kernel.org \
--to=robh@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--cc=kyrie.wu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=tfiga@chromium.org \
--cc=tzungbi@chromium.org \
--cc=wenst@chromium.org \
--cc=xia.jiang@mediatek.com \
/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).