From: kyrie.wu <kyrie.wu@mediatek.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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>,
<angelogioacchino.delregno@collabora.com>,
<nicolas.dufresne@collabora.com>, <wenst@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>, Rob Herring <robh@kernel.org>
Subject: Re: [V14,08/15] dt-bindings: mediatek: Add mediatek,mt8195-jpgdec compatible
Date: Mon, 26 Sep 2022 09:56:22 +0800 [thread overview]
Message-ID: <f0b80a0d60172e9c286c0cd3b599875a345ae4f0.camel@mediatek.com> (raw)
In-Reply-To: <3bbdfb31-2ba2-7345-54c7-82a67d95e30f@kernel.org>
On Fri, 2022-09-23 at 13:28 +0200, Krzysztof Kozlowski wrote:
> On 15/09/2022 08:43, Irui Wang wrote:
> > From: kyrie wu <kyrie.wu@mediatek.com>
> >
> > Add mediatek,mt8195-jpgdec compatible to binding document.
>
> Use scripts/get_maintainers.pl to CC all maintainers and relevant
> mailing lists.
>
> >
> > Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> > Signed-off-by: irui wang <irui.wang@mediatek.com>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > ---
> > .../media/mediatek,mt8195-jpegdec.yaml | 169
> > ++++++++++++++++++
> > 1 file changed, 169 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..9135cf889d1e
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/media/mediatek,mt8195-
> > jpegdec.yaml
> > @@ -0,0 +1,169 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id:
> > https://urldefense.com/v3/__http://devicetree.org/schemas/media/mediatek,mt8195-jpegdec.yaml*__;Iw!!CTRNKA9wMg0ARbw!yu00-_vltBz3bkDyzkeH2PENGyfi_megjPx815JiqrNVa28ZU7kcFYidMEos_id7$
> >
> > +$schema:
> > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!yu00-_vltBz3bkDyzkeH2PENGyfi_megjPx815JiqrNVa28ZU7kcFYidMAikt6uh$
> >
> > +
> > +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:
>
> You do not have more than one item. Skip items.
Hello Krzysztof,
The device node has the compatible of "mediatek,mt8195-jpgdec",
if skip this item, it may case dt-binding checking error.
For another, we may extend this items in the future.
>
> > + - 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.
> > +
> > + dma-ranges:
> > + maxItems: 1
> > + description: |
> > + Describes the physical address space of IOMMU maps to
> > memory.
> > +
> > + "#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
> > + - dma-ranges
> > + - ranges
> > +
> > +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 {
>
> No underscores in node names.
>
> Node names should be generic.
>
https://urldefense.com/v3/__https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html*generic-names-recommendation__;Iw!!CTRNKA9wMg0ARbw!yu00-_vltBz3bkDyzkeH2PENGyfi_megjPx815JiqrNVa28ZU7kcFYidMDjBqHu7$
>
Thanks for your kindly reminding, I will fix it in the next version.
Thanks.
Regards,
Kyrie.
>
> > + 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>;
> > + dma-ranges = <0x1 0x0 0x0 0x40000000 0x0
> > 0xfff00000>;
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > + ranges;
>
> Mess up indentation.
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-09-26 1:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 6:43 [V14,0/15] Enable jpeg enc & dec multi-hardwares for MT8195 Irui Wang
2022-09-15 6:43 ` [V14,1/15] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible Irui Wang
2022-09-15 6:43 ` [V14,02/15] mtk-jpegenc: export jpeg encoder functions Irui Wang
2022-09-15 6:43 ` [V14,03/15] mtk-jpegenc: support jpegenc multi-hardware Irui Wang
2022-09-15 6:43 ` [V14,04/15] mtk-jpegenc: add jpegenc timeout func interface Irui Wang
2022-09-15 6:43 ` [V14,05/15] mtk-jpegenc: add jpeg encode worker interface Irui Wang
2022-09-15 6:43 ` [V14,06/15] mtk-jpegenc: add output pic reorder interface Irui Wang
2022-09-15 6:43 ` [V14,07/15] mtk-jpegenc: add stop cmd interface for jpgenc Irui Wang
2022-09-15 6:43 ` [V14,08/15] dt-bindings: mediatek: Add mediatek,mt8195-jpgdec compatible Irui Wang
2022-09-23 11:28 ` Krzysztof Kozlowski
2022-09-26 1:56 ` kyrie.wu [this message]
2022-09-26 6:36 ` Krzysztof Kozlowski
2022-09-26 8:20 ` kyrie.wu
2022-09-15 6:43 ` [V14,09/15] media: mtk-jpegdec: export jpeg decoder functions Irui Wang
2022-09-15 6:53 ` [V14,0/15] Enable jpeg enc & dec multi-hardwares for MT8195 AngeloGioacchino Del Regno
2022-09-15 7:21 ` kyrie.wu
2022-09-15 7:41 ` Hans Verkuil
2022-09-15 8:16 ` AngeloGioacchino Del Regno
2022-09-23 9:38 ` Hans Verkuil
2022-09-26 6:45 ` kyrie.wu
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=f0b80a0d60172e9c286c0cd3b599875a345ae4f0.camel@mediatek.com \
--to=kyrie.wu@mediatek.com \
--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=krzk@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=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=robh@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