From: Matthias Brugger <matthias.bgg@gmail.com>
To: Bo-Chen Chen <rex-bc.chen@mediatek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>
Cc: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"hsinyi@google.com" <hsinyi@google.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH] dt-bindings: arm: mediatek: mmsys: change compatible for MT8195
Date: Thu, 25 Aug 2022 15:03:41 +0200 [thread overview]
Message-ID: <83f5f34f-6e71-3d36-e715-71896f0ac9a4@gmail.com> (raw)
In-Reply-To: <781356a88b502661ec23b3869679d80cf682017d.camel@mediatek.com>
On 25/08/2022 13:06, Bo-Chen Chen wrote:
> On Thu, 2022-08-25 at 18:55 +0800, Matthias Brugger wrote:
>>
>> On 25/08/2022 08:59, Bo-Chen Chen wrote:
>>> On Thu, 2022-08-25 at 14:11 +0800, Krzysztof Kozlowski wrote:
>>>> On 25/08/2022 08:56, Bo-Chen Chen wrote:
>>>>> From: "Jason-JH.Lin" <jason-jh.lin@mediatek.com>
>>>>>
>>>>> 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.
>>
>> drop clock driver example here.
>>
>
> Hello Matthias,
>
> Thanks for your review.
> I am not sure what do you mean.
> Could you explain more detailedly?
>
Never mind, it's not that important.
Regards,
Matthias
>>>>
>>>> I don't see binding to different clock drivers and anyway that's
>>>> not
>>>> really an argument here. Please focus in description on hardware
>>>> properties, IOW, are devices compatible or different. What is the
>>>> incompatible difference between VDOSYS0 and 1?
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>
>>> Hello Krzysztof,
>>>
>>> Thanks for yor review.
>>>
>>> From the functions perspective:
>>>
>>> Hardware pipeline of VDOSYS0 has these components: COLOR, CCORR,
>>> AAL,
>>> GAMMA, DITHER.
>>> They are related to PQ (Picture Quality) functions 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.
>>>
>>
>> Please include a description of this in the commit message.
>>
>
> Yes, I have sent v2 and add these to commit meesage.
>
> https://lore.kernel.org/all/20220825091448.14008-1-rex-bc.chen@mediatek.com/
>
> BRs,
> Bo-chen
>
>>> About mediatek ETHDR, you can refer to this series:
>>>
>>>
> https://lore.kernel.org/all/20220819061456.8042-2-nancy.lin@mediatek.com/
>>>
>>> To summary:
>>> Only VDOSYS0 can support PQ adjustment.
>>> Only VDOSYS1 can support HDR adjustment.
>>>
>>> Is this description ok for you?
>>> If it is ok, I will put them into commit message in next version.
>>>
>>> BRs,
>>> Bo-Chen
>>>
>
next prev parent reply other threads:[~2022-08-25 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 5:56 [PATCH] dt-bindings: arm: mediatek: mmsys: change compatible for MT8195 Bo-Chen Chen
2022-08-25 6:11 ` Krzysztof Kozlowski
2022-08-25 6:59 ` Bo-Chen Chen
2022-08-25 8:13 ` Krzysztof Kozlowski
2022-08-25 10:55 ` Matthias Brugger
2022-08-25 11:06 ` Bo-Chen Chen
2022-08-25 13:03 ` Matthias Brugger [this message]
2022-08-25 10:56 ` Matthias Brugger
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=83f5f34f-6e71-3d36-e715-71896f0ac9a4@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=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@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=rex-bc.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).