public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Moudy Ho (何宗原)" <Moudy.Ho@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Project_Global_Chrome_Upstream_Group 
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"angelogioacchino.delregno@collabora.com" 
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v2 01/12] dt-binding: mediatek: add bindings for MediaTek 8195 MDP3 components
Date: Mon, 12 Dec 2022 06:28:44 +0000	[thread overview]
Message-ID: <a731f459237051094940bc024ede9dee75ffde9b.camel@mediatek.com> (raw)
In-Reply-To: <20221209210631.GA3840519-robh@kernel.org>

Hi Rob,

Thanks for helping to review this series.

On Fri, 2022-12-09 at 15:06 -0600, Rob Herring wrote:
> On Wed, Dec 07, 2022 at 04:44:01PM +0800, Moudy Ho wrote:
> > This patch adds support for MT8195 MDP3 RDMA, and introduce more
> > MDP3 components present in MT8195.
> > 
> > Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
> > ---
> >  .../bindings/media/mediatek,mdp3-aal.yaml     | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-color.yaml   | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-fg.yaml      | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-hdr.yaml     | 63 +++++++++++++++
> >  .../bindings/media/mediatek,mdp3-merge.yaml   | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-ovl.yaml     | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-pad.yaml     | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-rdma.yaml    |  5 +-
> >  .../bindings/media/mediatek,mdp3-split.yaml   | 76
> > +++++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-stitch.yaml  | 64
> > ++++++++++++++++
> >  .../bindings/media/mediatek,mdp3-tcc.yaml     | 63 +++++++++++++++
> >  .../bindings/media/mediatek,mdp3-tdshp.yaml   | 64
> > ++++++++++++++++
> >  12 files changed, 717 insertions(+), 2 deletions(-)
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-aal.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-color.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-fg.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-hdr.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-merge.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-ovl.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-pad.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-split.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-stitch.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-tcc.yaml
> >  create mode 100644
> > Documentation/devicetree/bindings/media/mediatek,mdp3-tdshp.yaml
> > 
> > diff --git a/Documentation/devicetree/bindings/media/mediatek,mdp3-
> > aal.yaml b/Documentation/devicetree/bindings/media/mediatek,mdp3-
> > aal.yaml
> > new file mode 100644
> > index 000000000000..5b59e0802357
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/media/mediatek,mdp3-
> > aal.yaml
> > @@ -0,0 +1,64 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: 
> > https://urldefense.com/v3/__http://devicetree.org/schemas/media/mediatek,mdp3-aal.yaml*__;Iw!!CTRNKA9wMg0ARbw!gDIFKWscMU7roNTbdA1-AyzzrxCwA7ErPkkF-OaHo9UU8Y53_SGcVhOwp6dgB9hRhLzmmol53Sqlqg$ 
> >  
> > +$schema: 
> > https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!gDIFKWscMU7roNTbdA1-AyzzrxCwA7ErPkkF-OaHo9UU8Y53_SGcVhOwp6dgB9hRhLzmmolTzbOS7Q$ 
> >  
> > +
> > +title: MediaTek Media Data Path 3 AAL Device Tree Bindings
> 
> Drop ' Device Tree Bindings' from titles.
> 
> > +
> > +maintainers:
> > +  - Matthias Brugger <matthias.bgg@gmail.com>
> > +  - Moudy Ho <moudy.ho@mediatek.com>
> > +
> > +description: |
> 
> Don't need '|'
> 
> > +  One of Media Data Path 3 (MDP3) components is responsible for
> > backlight
> > +  power saving and sunlight visibility improving.
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - mediatek,mt8195-mdp3-aal
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +  mediatek,gce-client-reg:
> > +    $ref: /schemas/types.yaml#/definitions/phandle-array
> > +    items:
> > +      items:
> > +        - description: phandle of GCE
> > +        - description: GCE subsys id
> > +        - description: register offset
> > +        - description: register size
> > +    description: The register of client driver can be configured
> > by gce with
> > +      4 arguments defined in this property. Each GCE subsys id is
> > mapping to
> > +      a client defined in the header include/dt-
> > bindings/gce/<chip>-gce.h.
> 
> How many 4 cell entries? This allows any number. If 1, then you need 
> 'maxItems: 1' with the outer 'items'.
> 

Sorry for the confusion here, since the GCE clients are all unique,
I'll add a "maxItems: 1" in this property.

> > +
> > +  clocks:
> > +    minItems: 1
> > +
> > +  power-domains:
> > +    maxItems: 1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - mediatek,gce-client-reg
> > +  - clocks
> > +  - power-domains
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > +  - |
> > +    #include <dt-bindings/clock/mt8195-clk.h>
> > +    #include <dt-bindings/gce/mt8195-gce.h>
> > +    #include <dt-bindings/power/mt8195-power.h>
> > +
> > +    mdp3-aal0@14005000 {
> > +      compatible = "mediatek,mt8195-mdp3-aal";
> > +      reg = <0x14005000 0x1000>;
> > +      mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0x5000
> > 0x1000>;
> > +      clocks = <&vppsys0 CLK_VPP0_MDP_AAL>;
> > +      power-domains = <&spm MT8195_POWER_DOMAIN_VPPSYS0>;
> 
> Indent by 4 spaces here.
> 

Apologies for the indentation mismatch, it will be corrected in next
version.

> > +    };
> 
> Same comments for the rest...
> 

Sincerely,
Moudy

  reply	other threads:[~2022-12-12  6:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:44 [PATCH v2 00/12] add support MDP3 on MT8195 platform Moudy Ho
2022-12-07  8:44 ` [PATCH v2 01/12] dt-binding: mediatek: add bindings for MediaTek 8195 MDP3 components Moudy Ho
2022-12-09 21:06   ` Rob Herring
2022-12-12  6:28     ` Moudy Ho (何宗原) [this message]
2022-12-07  8:44 ` [PATCH v2 02/12] arm64: dts: mediatek: mt8195: add MDP3 nodes Moudy Ho
2022-12-07  8:44 ` [PATCH v2 03/12] media: platform: mtk-mdp3: add support second sets of MMSYS Moudy Ho
2022-12-07  8:44 ` [PATCH v2 04/12] media: platform: mtk-mdp3: add support second sets of MUTEX Moudy Ho
2022-12-07  8:44 ` [PATCH v2 05/12] media: platform: mtk-mdp3: introduce more pipelines from 8195 Moudy Ho
2022-12-07  8:44 ` [PATCH v2 06/12] media: platform: mtk-mdp3: introduce more MDP3 components Moudy Ho
2022-12-07  8:44 ` [PATCH v2 07/12] media: platform: mtk-mdp3: add checks for dummy components Moudy Ho
2022-12-07  8:44 ` [PATCH v2 08/12] media: platform: mtk-mdp3: avoid multiple driver registrations Moudy Ho
2022-12-07  8:44 ` [PATCH v2 09/12] media: platform: mtk-mdp3: extend GCE event waiting in RDMA and WROT Moudy Ho
2022-12-07  8:44 ` [PATCH v2 10/12] media: platform: mtk-mdp3: add 8195 platform configuration Moudy Ho
2022-12-07  8:44 ` [PATCH v2 11/12] media: platform: mtk-mdp3: add 8195 shared memory configurations Moudy Ho
2022-12-07  8:44 ` [PATCH v2 12/12] media: platform: mtk-mdp3: add 8195 component settings Moudy Ho

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=a731f459237051094940bc024ede9dee75ffde9b.camel@mediatek.com \
    --to=moudy.ho@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@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=robh@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