From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Irui Wang <irui.wang@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>,
nicolas.dufresne@collabora.com, wenst@chromium.org,
kyrie wu <kyrie.wu@mediatek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.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,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: Re: [V12,1/7] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible
Date: Fri, 29 Jul 2022 10:34:51 +0200 [thread overview]
Message-ID: <44dde534-769c-c456-c869-4e29213b3d56@collabora.com> (raw)
In-Reply-To: <20220729062630.5592-2-irui.wang@mediatek.com>
Il 29/07/22 08:26, Irui Wang ha scritto:
> From: kyrie wu <kyrie.wu@mediatek.com>
>
> Add mediatek,mt8195-jpgenc 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-jpegenc.yaml | 139 ++++++++++++++++++
> 1 file changed, 139 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..d9133e6a92f8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegenc.yaml
> @@ -0,0 +1,139 @@
..snip..
> +
> +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>;
> +
> + jpgenc_master {
What about using ranges here? The binding would look way cleaner, like:
jpeg-encoder@1a030000 {
.... properties ....
ranges = <0x30000 0 0x1a030000 0x10000>, /* P.S.: Not tested! */
<0x1030000 0 0x1b030000 0x10000>;
encoder-core@30000 {
compatible = "mediatek,mt8195-jpgenc-hw";
reg = <0 0x30000 0 0x10000>;
.... properties ....
};
encoder-core@1030000 {
compatible = "mediatek,mt8195-jpgenc-hw";
reg = <0 0x1030000 0 0x10000>;
.... properties ....
};
};
P.S.: Added Krzysztof to the loop.
Krzysztof, can you please give an opinion on that?
Thanks,
Angelo
> + 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 = <2>;
> + #size-cells = <2>;
> +
> + jpgenc@1a030000 {
> + compatible = "mediatek,mt8195-jpgenc-hw";
> + reg = <0 0x1a030000 0 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-jpgenc-hw";
> + reg = <0 0x1b030000 0 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>;
> + };
> + };
> + };
next prev parent reply other threads:[~2022-07-29 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 6:26 [V12,0/7] Enable two hardware jpeg encoder for MT8195 Irui Wang
2022-07-29 6:26 ` [V12,1/7] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible Irui Wang
2022-07-29 8:34 ` AngeloGioacchino Del Regno [this message]
2022-08-16 16:27 ` Rob Herring
2022-07-29 6:26 ` [V12,2/7] mtk-jpegenc: export jpeg encoder functions Irui Wang
2022-07-29 6:26 ` [V12,3/7] mtk-jpegenc: manage jpegenc multi-hardware Irui Wang
2022-08-03 11:35 ` Matthias Brugger
2022-07-29 6:26 ` [V12,4/7] mtk-jpegenc: add jpegenc timeout func interface Irui Wang
2022-07-29 6:26 ` [V12,5/7] mtk-jpegenc: add jpeg encode worker interface Irui Wang
2022-07-29 6:26 ` [V12,6/7] mtk-jpegenc: add output pic reorder interface Irui Wang
2022-07-29 6:26 ` [V12,7/7] mtk-jpegenc: add stop cmd interface for jpgenc 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=44dde534-769c-c456-c869-4e29213b3d56@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--cc=krzysztof.kozlowski@linaro.org \
--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=nfraprado@collabora.com \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®