public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"angelogioacchino.delregno@collabora.com" 
	<angelogioacchino.delregno@collabora.com>
Cc: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
	"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.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>,
	"Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>
Subject: Re: [PATCH v4 1/6] dt-bindings: arm: mediatek: mmsys: change compatible for MT8195
Date: Mon, 26 Sep 2022 02:49:25 +0000	[thread overview]
Message-ID: <99c38ceec83c2470fa4eb6a4d1416388b0679c55.camel@mediatek.com> (raw)
In-Reply-To: <23fd466265eec1effd83de6e8ad4ff64eadf5cae.camel@mediatek.com>

On Mon, 2022-09-26 at 09:19 +0800, Jason-JH.Lin wrote:
> Hi Krzysztof,
> 
> Thanks for the reviews.
> 
> On Sun, 2022-09-25 at 09:52 +0200, Krzysztof Kozlowski wrote:
> > On 24/09/2022 10:00, Jason-JH.Lin wrote:
> > > For previous MediaTek SoCs, such as MT8173, there are 2 display
> > > HW
> > > pipelines binding to 1 mmsys with the same power domain, the same
> > > clock driver and the same mediatek-drm driver.
> > > 
> > > For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines
> > > binding
> > > to
> > > 2 different power domains, different clock drivers and different
> > > mediatek-drm drivers.
> > > 
> > > Moreover, Hardware pipeline of VDOSYS0 has these components:
> > > COLOR,
> > > CCORR, AAL, GAMMA, DITHER. They are related to the PQ (Picture
> > > Quality)
> > > and they makes VDOSYS0 supports PQ function while they are not
> > > including in VDOSYS1.
> > > 
> > > Hardware pipeline of VDOSYS1 has the component ETHDR (HDR related
> > > component). It makes VDOSYS1 supports the HDR function while it's
> > > not
> > > including in VDOSYS0.
> > > 
> > > To summarize0:
> > > Only VDOSYS0 can support PQ adjustment.
> > > Only VDOSYS1 can support HDR adjustment.
> > > 
> > > Therefore, we need to separate these two different mmsys
> > > hardwares
> > > to
> > > 2 different compatibles for MT8195.
> > > 
> > > Fixes: 81c5a41d10b9 ("dt-bindings: arm: mediatek: mmsys: add
> > > mt8195
> > > SoC binding")
> > > Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com>
> > > Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> > > ---
> > >  .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml     | 5
> > > ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git
> > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
> > > am
> > > l
> > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
> > > am
> > > l
> > > index 6ad023eec193..4f90ea03c596 100644
> > > ---
> > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
> > > am
> > > l
> > > +++
> > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
> > > am
> > > l
> > > @@ -31,13 +31,16 @@ properties:
> > >                - mediatek,mt8183-mmsys
> > >                - mediatek,mt8186-mmsys
> > >                - mediatek,mt8192-mmsys
> > > -              - mediatek,mt8195-mmsys
> > 
> > We keep making circles...
> 
> I didn't find the sample of "deprecated" in the example-schema.yaml,
> so I keep misunderstand what you mean.
> I'm sorry about that...
> 
> > 
> > I asked "and why mediatek,mt8195-mmsys is kept as non-deprecated?"
> > 
> 
> Yes, it should be deprecated. I shouldn't remove it...
> 
> > and your response is to remove it... Eh, okay, that's fine but now
> > your
> > change causes now warnings in existing DTS. Either you keep old
> > entry
> > as
> > deprecated (just git grep for deprecated, you will find examples
> > how
> > to
> > do it) or fix the DTS.
> > 
> 
> Thanks for the advice.
> 
> Now I found an example in other yaml, so I just added the
> "deprecated"
> tag like this, right?
> 
>  - items:
>           - enum:
>               - mediatek,mt2701-mmsys
>               - mediatek,mt2712-mmsys
>               - mediatek,mt6765-mmsys
>               - mediatek,mt6779-mmsys
>               - mediatek,mt6797-mmsys
>               - mediatek,mt8167-mmsys
>               - mediatek,mt8173-mmsys
>               - mediatek,mt8183-mmsys
>               - mediatek,mt8186-mmsys
>               - mediatek,mt8192-mmsys
>               - mediatek,mt8195-mmsys
>                   deprecated: true
>               - mediatek,mt8365-mmsys
>           - const: syscon

No, this can not pass the DT_SCHEMA checking...


I have to move it out like this, but I'm not sure if this is correct?

- items:
          - enum:
              - mediatek,mt2701-mmsys
              - mediatek,mt2712-mmsys
              - mediatek,mt6765-mmsys
              - mediatek,mt6779-mmsys
              - mediatek,mt6797-mmsys
              - mediatek,mt8167-mmsys
              - mediatek,mt8173-mmsys
              - mediatek,mt8183-mmsys
              - mediatek,mt8186-mmsys
              - mediatek,mt8192-mmsys
              - mediatek,mt8365-mmsys
          - const: syscon
      - description: For mt8195, vdosys0 and vdosys1 are 2 display HW
pipelines binding,
                     so mediatek,mt8195-mmsys should be deprecated.
        deprecated: true
        items:
          - enum:
              - mediatek,mt8195-mmsys
          - const: syscon

Regards,
Jason-JH.Lin

> 
> Regard,
> Jason-JH.Lin
> 
> > Best regards,
> > Krzysztof
> > 

  reply	other threads:[~2022-09-26  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220924080058.20566-1-jason-jh.lin@mediatek.com>
     [not found] ` <20220924080058.20566-2-jason-jh.lin@mediatek.com>
2022-09-25  7:52   ` [PATCH v4 1/6] dt-bindings: arm: mediatek: mmsys: change compatible for MT8195 Krzysztof Kozlowski
2022-09-26  1:19     ` Jason-JH Lin (林睿祥)
2022-09-26  2:49       ` Jason-JH Lin (林睿祥) [this message]
2022-09-26  6:40       ` Krzysztof Kozlowski

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=99c38ceec83c2470fa4eb6a4d1416388b0679c55.camel@mediatek.com \
    --to=jason-jh.lin@mediatek.com \
    --cc=Nancy.Lin@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=Singo.Chang@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=ck.hu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --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=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