From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"nfraprado@collabora.com" <nfraprado@collabora.com>
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>,
"nathan@kernel.org" <nathan@kernel.org>,
"Yongqiang Niu (牛永强)" <yongqiang.niu@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"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>,
"airlied@linux.ie" <airlied@linux.ie>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"ndesaulniers@google.com" <ndesaulniers@google.com>
Subject: Re: [PATCH v28 01/11] dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible for MT8195
Date: Tue, 22 Nov 2022 16:48:45 +0100 [thread overview]
Message-ID: <a5464d62-bb42-5bdf-e49e-5c3edef4b09b@gmail.com> (raw)
In-Reply-To: <de21390898759ce979da8d2ae76a93982f59c149.camel@mediatek.com>
On 22/11/2022 11:51, Nancy Lin (林欣螢) wrote:
> Dear Matthias,
>
> Thanks for the review.
>
> On Thu, 2022-11-10 at 14:10 +0100, Matthias Brugger wrote:
>>
>> On 09/11/2022 06:10, Jason-JH Lin (林睿祥) wrote:
>> > On Tue, 2022-11-08 at 18:46 +0100, Matthias Brugger wrote:
>> > >
>> > > On 07/11/2022 08:22, Nancy.Lin wrote:
>> > > > Add vdosys1 mmsys compatible for MT8195 platform.
>> > > >
>> > > > For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines
>> > > > binding
>> > > > to
>> > > > 2 different power domains, different clock drivers and
>> > > > different
>> > > > mediatek-drm drivers.
>> > > >
>> > > > Signed-off-by: Nancy.Lin <nancy.lin@mediatek.com>
>> > > > Reviewed-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>> > > > ---
>> > > >
>> > > > .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml |
>> > > > 4
>> > > > +++-
>> > > > 1 file changed, 3 insertions(+), 1 deletion(-)
>> > > >
>> > > > diff --git
>> > > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys
>> > > > .yam
>> > > > l
>> > > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys
>> > > > .yam
>> > > > l
>> > > > index 0711f1834fbd..aaabe2196185 100644
>> > > > ---
>> > > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys
>> > > > .yam
>> > > > l
>> > > > +++
>> > > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys
>> > > > .yam
>> > > > l
>> > > > @@ -48,7 +48,9 @@ properties:
>> > > > - const: syscon
>> > > >
>> > > > - items:
>> > > > - - const: mediatek,mt8195-vdosys0
>> > > > + - enum:
>> > > > + - mediatek,mt8195-vdosys0
>> > > > + - mediatek,mt8195-vdosys1
>> > > > - const: mediatek,mt8195-mmsys
>> > > > - const: syscon
>> > > >
>> > >
>> > > I think we had that several times already:
>> > >
>> >
>> >
> https://lore.kernel.org/all/6bbe9527-ae48-30e0-fb45-519223a744d7@linaro.org/
>> > >
>> > > We will something like this, but please check that this does not
>> > > give
>> > > any
>> > > errors/warnings:
>> > >
>> > > diff --git
>> > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
>> > > aml
>> > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
>> > > aml
>> > > index eb451bec23d3d..8e9c4f4d7c389 100644
>> > > ---
>> > > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
>> > > aml
>> > > +++
>> > > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.y
>> > > aml
>> > > @@ -32,13 +32,22 @@ properties:
>> > > - mediatek,mt8183-mmsys
>> > > - mediatek,mt8186-mmsys
>> > > - mediatek,mt8192-mmsys
>> > > - - mediatek,mt8195-mmsys
>> > > - mediatek,mt8365-mmsys
>> > > - const: syscon
>> > > - items:
>> > > - const: mediatek,mt7623-mmsys
>> > > - const: mediatek,mt2701-mmsys
>> > > - const: syscon
>> > > + - items:
>> > > + - const: mediatek,mt8195-vdosys0
>> > > + - const: syscon
>> > > + - items:
>> > > + - const: mediatek,mt8195-vdosys1
>> > > + - const: syscon
>> > > + - items:
>> > > + - const: mediatek,mt8195-mmsys
>> > > + - const: syscon
>> > > + deprecated: true
>> > >
>> > > reg:
>> > > maxItems: 1
>> >
>> > Hi Matthias,
>> >
>> > As the vdosys0 previous reviewed patch:
>> >
>> >
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/patch/20220927152704.12018-2-jason-jh.lin@mediatek.com/__;!!CTRNKA9wMg0ARbw!zRdbIyyAsfqob2kapMAcKYATAguhEV0x0qE5cTOAcWUNhzeAbMHzZoos_2QzUCxS$
>> >
>> > Should I modify the vdosys0 items format like your example?
>> >
>> > Or should vdosys1 add items format like vdosys0's previous patch?
>> > - items:
>> > - const: mediatek,mt8195-vdosys1
>> > - const: mediatek,mt8195-mmsys
>> > - const: syscon
>> >
>>
>> No, vdosys1 must not have mediatek,mt8195-mmsys fallback.
>>
>> Regards,
>> Matthias
>>
>
> I will fix it and add the following vdosys1 binding base on [1].
>
> - description: vdosys0 and vdosys1 are 2 display HW pipelines,
> so mt8195 binding should be deprecated.
> deprecated: true
> items:
> - const: mediatek,mt8195-mmsys
> - const: syscon
> - items:
> - const: mediatek,mt7623-mmsys
> - const: mediatek,mt2701-mmsys
> - const: syscon
> - items:
> - const: mediatek,mt8195-vdosys0
> - const: mediatek,mt8195-mmsys
> - const: syscon
> + - items:
> + - const: mediatek,mt8195-vdosys1
> + - const: syscon
>
Looks good, thanks
Matthias
> [1]
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/matthias.bgg/linux/+/b237efd47df7d25b78c306e90b97c5aa0ff4c4fc/Documentation/devicetree/bindings/arm/mediatek/mediatek%2Cmmsys.yaml
>
> Regards,
> Nancy
>
>
>> > Regards,
>> > Jason-JH.Lin
>> >
>> >
>> >
>> > ************* MEDIATEK Confidentiality Notice
>> > ********************
>> > The information contained in this e-mail message (including any
>> > attachments) may be confidential, proprietary, privileged, or
>> > otherwise
>> > exempt from disclosure under applicable laws. It is intended to be
>> > conveyed only to the designated recipient(s). Any use,
>> > dissemination,
>> > distribution, printing, retaining or copying of this e-mail
>> > (including its
>> > attachments) by unintended recipient(s) is strictly prohibited and
>> > may
>> > be unlawful. If you are not an intended recipient of this e-mail,
>> > or believe
>> >
>> > that you have received this e-mail in error, please notify the
>> > sender
>> > immediately (by replying to this e-mail), delete any and all copies
>> > of
>> > this e-mail (including any attachments) from your system, and do
>> > not
>> > disclose the content of this e-mail to any other person. Thank you!
>>
>>
>
> ************* MEDIATEK Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
next prev parent reply other threads:[~2022-11-22 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221107072243.15748-1-nancy.lin@mediatek.com>
[not found] ` <20221107072243.15748-7-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 06/11] soc: mediatek: add mtk-mmsys config API for mt8195 vdosys1 Matthias Brugger
2022-11-28 7:38 ` Nancy Lin (林欣螢)
[not found] ` <20221107072243.15748-5-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 04/11] soc: mediatek: add mtk-mmsys support " Matthias Brugger
2022-11-08 19:10 ` Nícolas F. R. A. Prado
2022-11-09 11:18 ` Matthias Brugger
[not found] ` <20221107072243.15748-2-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 01/11] dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible for MT8195 Matthias Brugger
2022-11-09 5:10 ` Jason-JH Lin (林睿祥)
2022-11-10 13:10 ` Matthias Brugger
2022-11-22 10:51 ` Nancy Lin (林欣螢)
2022-11-22 15:48 ` Matthias Brugger [this message]
2022-11-23 16:06 ` Krzysztof Kozlowski
2022-11-24 7:34 ` Nancy Lin (林欣螢)
[not found] ` <20221107072243.15748-6-nancy.lin@mediatek.com>
2022-11-08 17:37 ` [PATCH v28 05/11] soc: mediatek: refine code to use mtk_mmsys_update_bits API Matthias Brugger
2022-11-08 19:43 ` Nícolas F. R. A. Prado
2022-11-10 13:12 ` Matthias Brugger
2022-11-24 9:38 ` Nancy Lin (林欣螢)
2022-12-01 11:44 ` Chen-Yu Tsai
2022-12-27 7:54 ` Nancy Lin (林欣螢)
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=a5464d62-bb42-5bdf-e49e-5c3edef4b09b@gmail.com \
--to=matthias.bgg@gmail.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=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=yongqiang.niu@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;
as well as URLs for NNTP newsgroup(s).