linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: kyrie.wu <kyrie.wu@mediatek.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	Tzung-Bi Shih <tzungbi@chromium.org>
Cc: <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>, <srv_heupstream@mediatek.com>
Subject: Re: [RESEND, V7, 1/6] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible
Date: Wed, 16 Mar 2022 20:58:10 +0800	[thread overview]
Message-ID: <be5f6c6d17b78c5b99bd149ffd8030ad4bace9da.camel@mediatek.com> (raw)
In-Reply-To: <1645693637-627-2-git-send-email-kyrie.wu@mediatek.com>

On Thu, 2022-02-24 at 17:07 +0800, kyrie.wu wrote:
> From: kyrie wu <kyrie.wu@mediatek.com>
> 
> Add mediatek,mt8195-jpgenc compatible to binding document.
> 
> Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> ---
>  .../media/mediatek,mt8195-jpegenc.yaml        | 174
> ++++++++++++++++++
>  1 file changed, 174 insertions(+)
>  create mode 100644
> Documentation/devicetree/bindings/media/mediatek,mt8195-jpegenc.yaml
> 
> diff --git a/Documentation/devicetree/bindings/media/mediatek,mt8195-
> jpegenc.yaml
> b/Documentation/devicetree/bindings/media/mediatek,mt8195-
> jpegenc.yaml
> new file mode 100644
> index 000000000000..efb0d843edb6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek,mt8195-
> jpegenc.yaml
> @@ -0,0 +1,174 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: 
> http://devicetree.org/schemas/media/mediatek,mt8195-jpegenc.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>

Hello Kyrie,

I think you should use kyrie.wu@mediatek.com instead of pd account.

BRs,
Rex

> +
> +description: |-
> +  MediaTek JPEG Encoder is the JPEG encode hardware present in
> MediaTek SoCs
> +
> +properties:
> +  compatible:
> +    items:
> +      - const: mediatek,mt8195-jpgenc
> +
> +  power-domains:
> +    maxItems: 1
> +
> +  iommus:
> +    maxItems: 4
> +    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: 1
> +
> +  "#size-cells":
> +    const: 1
> +
> +  ranges: true
> +
> +# Required child node:
> +patternProperties:
> +  "jpgenc@1a030000":
> +    type: object
> +
> +    properties:
> +      compatible:
> +        const: mediatek,mt8195-jpgenc0
> +
> +      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: jpgenc
> +
> +      power-domains:
> +        maxItems: 1
> +
> +    required:
> +      - compatible
> +      - reg
> +      - iommus
> +      - interrupts
> +      - clocks
> +      - clock-names
> +      - power-domains
> +
> +    additionalProperties: false
> +
> +  "jpgenc@1b030000":
> +    type: object
> +
> +    properties:
> +      compatible:
> +        const: mediatek,mt8195-jpgenc1
> +
> +      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: jpgenc
> +
> +      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>
> +
> +    jpgenc_master {
> +            compatible = "mediatek,mt8195-jpgenc";
> +            power-domains = <&spm MT8195_POWER_DOMAIN_VENC_CORE1>;
> +            iommus = <&iommu_vpp M4U_PORT_L20_JPGENC_Y_RDMA>,
> +            <&iommu_vpp M4U_PORT_L20_JPGENC_C_RDMA>,
> +            <&iommu_vpp M4U_PORT_L20_JPGENC_Q_TABLE>,
> +            <&iommu_vpp M4U_PORT_L20_JPGENC_BSDMA>;
> +            #address-cells = <1>;
> +            #size-cells = <1>;
> +            ranges;
> +
> +            jpgenc@1a030000 {
> +                    compatible = "mediatek,mt8195-jpgenc0";
> +                    reg = <0x1a030000 0x10000>;
> +                    iommus = <&iommu_vdo
> M4U_PORT_L19_JPGENC_Y_RDMA>,
> +                    <&iommu_vdo M4U_PORT_L19_JPGENC_C_RDMA>,
> +                    <&iommu_vdo M4U_PORT_L19_JPGENC_Q_TABLE>,
> +                    <&iommu_vdo M4U_PORT_L19_JPGENC_BSDMA>;
> +                    interrupts = <GIC_SPI 342 IRQ_TYPE_LEVEL_HIGH
> 0>;
> +                    clocks = <&vencsys CLK_VENC_JPGENC>;
> +                    clock-names = "jpgenc";
> +                    power-domains = <&spm MT8195_POWER_DOMAIN_VENC>;
> +            };
> +
> +            jpgenc@1b030000 {
> +                    compatible = "mediatek,mt8195-jpgenc1";
> +                    reg = <0x1b030000 0x10000>;
> +                    iommus = <&iommu_vpp
> M4U_PORT_L20_JPGENC_Y_RDMA>,
> +                    <&iommu_vpp M4U_PORT_L20_JPGENC_C_RDMA>,
> +                    <&iommu_vpp M4U_PORT_L20_JPGENC_Q_TABLE>,
> +                    <&iommu_vpp M4U_PORT_L20_JPGENC_BSDMA>;
> +                    interrupts = <GIC_SPI 347 IRQ_TYPE_LEVEL_HIGH
> 0>;
> +                    clocks = <&vencsys_core1 CLK_VENC_CORE1_JPGENC>;
> +                    clock-names = "jpgenc";
> +                    power-domains = <&spm
> MT8195_POWER_DOMAIN_VENC_CORE1>;
> +            };
> +    };


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-16 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  9:07 [RESEND,V7,0/6] Enable two hardware jpeg encoder for MT8195 kyrie.wu
2022-02-24  9:07 ` [RESEND, V7, 1/6] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible kyrie.wu
2022-03-16 12:58   ` Rex-BC Chen [this message]
2022-02-24  9:07 ` [RESEND,V7,2/6] media: mtk-jpegenc: export jpeg encoder functions kyrie.wu
2022-02-24  9:07 ` [RESEND,V7,3/6] media: mtk-jpegenc: manage jpegenc multi-hardware kyrie.wu
2022-03-02  9:45   ` [RESEND, V7, 3/6] " AngeloGioacchino Del Regno
2022-03-07  1:46     ` [RESEND,V7,3/6] " kyrie.wu
2022-02-24  9:07 ` [RESEND, V7, 4/6] media: mtk-jpegenc: add jpegenc timeout func interface kyrie.wu
2022-02-24  9:07 ` [RESEND,V7,5/6] media: mtk-jpegenc: add jpeg encode worker interface kyrie.wu
2022-02-24  9:07 ` [RESEND,V7,6/6] media: mtk-jpegenc: add output pic reorder interface kyrie.wu
2022-02-24 10:04 ` [RESEND,V7,0/6] Enable two hardware jpeg encoder for MT8195 Hans Verkuil

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=be5f6c6d17b78c5b99bd149ffd8030ad4bace9da.camel@mediatek.com \
    --to=rex-bc.chen@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --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=robh+dt@kernel.org \
    --cc=srv_heupstream@mediatek.com \
    --cc=tfiga@chromium.org \
    --cc=tzungbi@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).