From: "Shawn Sung (宋孝謙)" <Shawn.Sung@mediatek.com>
To: "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"fshao@google.com" <fshao@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 1/6] dt-bindings: display/mediatek: mt8188: Add documentations for VDOSYS1
Date: Thu, 8 Jun 2023 03:12:26 +0000 [thread overview]
Message-ID: <9db76b20dcd87d0406e8b26f14436431126d27fc.camel@mediatek.com> (raw)
In-Reply-To: <85713602-dfe1-c90b-174b-3678d91369aa@linaro.org>
Hi Krzysztof,
Sorry, I missed this step in my SOP.
Will follow the instruction below to check again,
thank you for the information.
Best regards,
Hsiao Chien Sung
On Wed, 2023-06-07 at 09:26 +0200, Krzysztof Kozlowski wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
> On 07/06/2023 08:11, Hsiao Chien Sung wrote:
> > Add device tree documentations for MT8188 VDOSYS1.
>
> It does not look like you tested the bindings, at least after quick
> look. Please run `make dt_binding_check` (see
> Documentation/devicetree/bindings/writing-schema.rst for
> instructions).
> Maybe you need to update your dtschema and yamllint.
>
> > diff --git
> a/Documentation/devicetree/bindings/display/mediatek/mediatek,padding
> .yaml
> b/Documentation/devicetree/bindings/display/mediatek/mediatek,padding
> .yaml
> > new file mode 100644
> > index 000000000000..8a9e74cbf6dc
> > --- /dev/null
> > +++
> b/Documentation/devicetree/bindings/display/mediatek/mediatek,padding
> .yaml
> > @@ -0,0 +1,80 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id:
> http://devicetree.org/schemas/display/mediatek/mediatek,padding.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: MediaTek PADDING
> > +
> > +maintainers:
> > + - Chun-Kuang Hu <chunkuang.hu@kernel.org>
> > + - Philipp Zabel <p.zabel@pengutronix.de>
> > +
> > +description:
> > + MediaTek PADDING provides ability to VDOSYS1 to fill pixels to
> > + width and height of a layer with a specified color.
> > + Since MIXER in VDOSYS1 requires the width of a layer to be 2-
> pixel-align, or
> > + 4-pixel-align when ETHDR is enabled, we need PADDING to deal
> with odd width.
> > + Please notice that even if the PADDING is in bypass mode,
> > + settings in the registers must be cleared to 0, otherwise
> > + undeinfed behaviors could happen.
>
> Typo, undefined
>
> > +
>
>
>
> > +required:
> > + - compatible
> > + - reg
> > + - power-domains
> > + - clocks
> > + - mediatek,gce-client-reg
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + #include <dt-bindings/clock/mt8188-clk.h>
> > + #include <dt-bindings/power/mt8188-power.h>
> > + #include <dt-bindings/gce/mt8188-gce.h>
> > + #include <dt-bindings/memory/mt8188-memory-port.h>
> > +
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + vdo1_padding0: vdo1_padding0@1c11d000 {
>
> No underscores in node names.
>
> Node names should be generic. See also explanation and list of
> examples
> in DT specification:
>
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
>
> > + compatible = "mediatek,mt8188-vdo1-padding";
> > + reg = <0 0x1c11d000 0 0x1000>;
> > + clocks = <&vdosys1 CLK_VDO1_PADDING0>;
> > + power-domains = <&spm MT8188_POWER_DOMAIN_VDOSYS1>;
> > + mediatek,gce-client-reg =
> > + <&gce0 SUBSYS_1c11XXXX 0xd000 0x1000>;
>
> Wrong wrapping. It's one line. Properties should not be wrapped after
> '='.
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-06-08 3:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 6:11 [PATCH v1 0/6] Add display driver for MT8188 VDOSYS1 Hsiao Chien Sung
2023-06-07 6:11 ` [PATCH v1 1/6] dt-bindings: display/mediatek: mt8188: Add documentations for VDOSYS1 Hsiao Chien Sung
2023-06-07 7:15 ` Rob Herring
2023-06-07 7:26 ` Krzysztof Kozlowski
2023-06-08 3:12 ` Shawn Sung (宋孝謙) [this message]
2023-06-07 6:11 ` [PATCH v1 2/6] dt-bindings: reset: mt8188: Add reset control bits " Hsiao Chien Sung
2023-06-07 7:27 ` Krzysztof Kozlowski
2023-06-08 3:07 ` Shawn Sung (宋孝謙)
2023-06-07 7:37 ` AngeloGioacchino Del Regno
2023-06-07 7:51 ` AngeloGioacchino Del Regno
2023-06-08 3:01 ` Shawn Sung (宋孝謙)
2023-06-08 6:15 ` Shawn Sung (宋孝謙)
2023-06-08 7:56 ` Krzysztof Kozlowski
2023-06-07 6:11 ` [PATCH v1 3/6] soc: mediatek: mt8188: Support VDOSYS1 in mtk-mmsys Hsiao Chien Sung
2023-06-07 6:11 ` [PATCH v1 4/6] drm/mediatek: mt8188: Modify display driver for VDOSYS1 Hsiao Chien Sung
2023-06-07 7:20 ` AngeloGioacchino Del Regno
2023-07-06 6:16 ` CK Hu (胡俊光)
2023-06-07 6:11 ` [PATCH v1 5/6] soc: mediatek: mt8188: Support VDOSYS1 PADDING in mtk-mmsys Hsiao Chien Sung
2023-06-07 6:11 ` [PATCH v1 6/6] drm/mediatek: mt8188: Add VDOSYS1 PADDING driver Hsiao Chien Sung
2023-06-07 7:36 ` AngeloGioacchino Del Regno
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=9db76b20dcd87d0406e8b26f14436431126d27fc.camel@mediatek.com \
--to=shawn.sung@mediatek.com \
--cc=Jason-JH.Lin@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fshao@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
/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