From: Rob Herring <robh@kernel.org>
To: "bo.kong" <bo.kong@mediatek.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Conor Dooley <conor+dt@kernel.org>,
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,
Project_Global_Chrome_Upstream_Group@mediatek.com,
zhaoyuan.chen@mediatek.com, teddy.chen@mediatek.com
Subject: Re: [PATCH v4 1/4] media: dt-bindings: add MT8188 AIE
Date: Fri, 21 Feb 2025 16:33:06 -0600 [thread overview]
Message-ID: <20250221223306.GA190439-robh@kernel.org> (raw)
In-Reply-To: <20250220070114.15015-2-bo.kong@mediatek.com>
On Thu, Feb 20, 2025 at 02:59:50PM +0800, bo.kong wrote:
> From: Bo Kong <Bo.Kong@mediatek.com>
>
> Add YAML device tree bindings for MT8188 AIE.
>
> Signed-off-by: Bo Kong <Bo.Kong@mediatek.com>
> ---
> Changes in v4:
> 1. Remove address-cells and size-cells
> 2. Remove larb12 related content
> 3. Update id content
>
> Changes in v3:
> None
>
> Changes in v2:
> 1. Fix coding style
> ---
> .../bindings/media/mediatek,mt8188-aie.yaml | 90 +++++++++++++++++++
> 1 file changed, 90 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/mediatek,mt8188-aie.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/mediatek,mt8188-aie.yaml b/Documentation/devicetree/bindings/media/mediatek,mt8188-aie.yaml
> new file mode 100644
> index 000000000000..232b5afc2ad3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek,mt8188-aie.yaml
> @@ -0,0 +1,90 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/mediatek,mt8188-aie.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: The AI Engine Unit of MediaTek Camera System
> +
> +maintainers:
> + - Bo Kong <bo.kong@mediatek.com>
> +
> +description:
> + AIE(AI Engine) is one of the units in mt8188 ISP which
> + provides hardware accelerated face detection function,
> + it can detect different sizes of faces in a raw image.
Wrap lines at 80 char.
> +
> +properties:
> + compatible:
> + items:
> + - const: mediatek,mt8188-aie
> +
> + reg:
> + maxItems: 1
> + description: Physical base address and length of the register space.
Drop description. That's every 'reg' entry.
> +
> + interrupts:
> + maxItems: 1
> +
> + mediatek,larb:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Must contain the local arbiters in the current SoCs, see
> + Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.yaml
> + for details.
> +
> + 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.
It's not really clear what the 4 entries are. Like any other property,
the order should be defined.
> +
> + power-domains:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: clock for imgsys main ipe
> + - description: clock for ipe fdvt
> + - description: clock for ipe top
> +
> + clock-names:
> + items:
> + - const: img_ipe
> + - const: ipe_fdvt
> + - const: ipe_top
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - iommus
> + - power-domains
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/memory/mediatek,mt8188-memory-port.h>
> + #include <dt-bindings/power/mediatek,mt8188-power.h>
> + #include <dt-bindings/clock/mediatek,mt8188-clk.h>
> + aie@15310000 {
> + compatible = "mediatek,mt8188-aie";
> + reg = <0x15310000 0x1000>;
> + interrupts = <GIC_SPI 787 IRQ_TYPE_LEVEL_HIGH 0>;
> + iommus = <&vpp_iommu M4U_PORT_L12_FDVT_RDA_0>,
> + <&vpp_iommu M4U_PORT_L12_FDVT_RDB_0>,
> + <&vpp_iommu M4U_PORT_L12_FDVT_WRA_0>,
> + <&vpp_iommu M4U_PORT_L12_FDVT_WRB_0>;
> + power-domains = <&spm MT8188_POWER_DOMAIN_IPE>;
> + clocks = <&imgsys CLK_IMGSYS_MAIN_IPE>,
> + <&ipesys CLK_IPE_FDVT>,
> + <&ipesys CLK_IPESYS_TOP>;
> + clock-names = "img_ipe",
> + "ipe_fdvt",
> + "ipe_top";
> + };
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-02-21 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 6:59 [PATCH v4 0/4] Add MTK AIE Driver For MT8188 bo.kong
2025-02-20 6:59 ` [PATCH v4 1/4] media: dt-bindings: add MT8188 AIE bo.kong
2025-02-21 22:33 ` Rob Herring [this message]
2025-03-03 2:50 ` CK Hu (胡俊光)
2025-02-20 6:59 ` [PATCH v4 2/4] arm64: dts: mt8188: add aie node bo.kong
2025-02-20 6:59 ` [PATCH v4 3/4] uapi: linux: add MT8188 AIE bo.kong
2025-03-03 2:37 ` CK Hu (胡俊光)
2025-02-20 6:59 ` [PATCH v4 4/4] media: mediatek: add MT8188 AIE driver bo.kong
2025-02-20 9:49 ` AngeloGioacchino Del Regno
2025-02-20 15:18 ` Nicolas Dufresne
2025-03-12 5:32 ` CK Hu (胡俊光)
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=20250221223306.GA190439-robh@kernel.org \
--to=robh@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bo.kong@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=mchehab@kernel.org \
--cc=teddy.chen@mediatek.com \
--cc=zhaoyuan.chen@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 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.