From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Eugen Hristev <eugen.hristev@collabora.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
tiffany.lin@mediatek.com, andrew-ct.chen@mediatek.com,
matthias.bgg@gmail.com, Kyrie Wu <kyrie.wu@mediatek.com>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Hsin-Yi Wang <hsinyi@chromium.org>
Subject: Re: [PATCH 4/4] arm64: dts: mediatek: mt8186: Add venc node
Date: Thu, 14 Dec 2023 11:44:26 +0100 [thread overview]
Message-ID: <d20c35e2-cc40-436d-90ca-4cab555874ca@collabora.com> (raw)
In-Reply-To: <20231213122017.102100-4-eugen.hristev@collabora.com>
Il 13/12/23 13:20, Eugen Hristev ha scritto:
> From: Kyrie Wu <kyrie.wu@mediatek.com>
>
> Add video encoder node.
>
> Signed-off-by: Kyrie Wu <kyrie.wu@mediatek.com>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> Reviewed-by: Hsin-Yi Wang <hsinyi@chromium.org>
> [eugen.hristev@collabora.com: minor cleanup]
> Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8186.dtsi b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> index 66ead3f23336..8535ff2b44e9 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> @@ -1993,6 +1993,30 @@ larb7: smi@17010000 {
> power-domains = <&spm MT8186_POWER_DOMAIN_VENC>;
> };
>
> + venc: venc@17020000 {
> + compatible = "mediatek,mt8183-vcodec-enc";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + reg = <0 0x17020000 0 0x2000>;
> + interrupts = <GIC_SPI 243 IRQ_TYPE_LEVEL_HIGH 0>;
> + iommus = <&iommu_mm IOMMU_PORT_L7_VENC_RCPU>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_REC>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_BSDMA>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_SV_COMV>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_RD_COMV>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_CUR_LUMA>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_CUR_CHROMA>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_REF_LUMA>,
> + <&iommu_mm IOMMU_PORT_L7_VENC_REF_CHROMA>;
> + dma-ranges = <0x1 0x0 0x1 0x0 0x1 0x0>;
> + mediatek,scp = <&scp>;
> + clocks = <&vencsys CLK_VENC_CKE1_VENC>;
> + clock-names = "MT_CG_VENC";
clock-names = "venc"; (please no underscores and please lower case)
> + assigned-clocks = <&topckgen CLK_TOP_VENC>;
> + assigned-clock-parents = <&topckgen CLK_TOP_UNIVPLL_D3>;
> + power-domains = <&spm MT8186_POWER_DOMAIN_VENC>;
> + };
....also:
The following order of properties in device nodes is preferred:
1. "compatible"
2. "reg"
3. "ranges"
4. Standard/common properties (defined by common bindings, e.g. without
vendor-prefixes)
5. Vendor-specific properties
6. "status" (if applicable)
7. Child nodes, where each node is preceded with a blank line
Documentation/devicetree/bindings/dts-coding-style.rst
Please reorder as per the DTS coding style document, and also please rename the
venc node to use a generic name, such as "video-encoder@xxxx"
Cheers,
Angelo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:20 [PATCH 1/4] dt-bindings: media: mtk-vcodec-encoder: add dma-ranges Eugen Hristev
2023-12-13 12:20 ` [PATCH 2/4] media: mediatek: vcodec: fix possible unbalanced PM counter Eugen Hristev
2023-12-14 10:45 ` AngeloGioacchino Del Regno
2023-12-13 12:20 ` [PATCH 3/4] arm64: dts: mediatek: mt8186: fix VENC power domain clocks Eugen Hristev
2023-12-13 12:20 ` [PATCH 4/4] arm64: dts: mediatek: mt8186: Add venc node Eugen Hristev
2023-12-14 10:44 ` AngeloGioacchino Del Regno [this message]
2023-12-14 10:50 ` AngeloGioacchino Del Regno
2023-12-14 10:52 ` Eugen Hristev
2023-12-14 15:30 ` Eugen Hristev
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=d20c35e2-cc40-436d-90ca-4cab555874ca@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=hsinyi@chromium.org \
--cc=kernel@collabora.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=matthias.bgg@gmail.com \
--cc=tiffany.lin@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