From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Moudy Ho (何宗原)" <Moudy.Ho@mediatek.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"airlied@gmail.com" <airlied@gmail.com>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 3/3] dt-binding: mediatek: add MediaTek mt8195 MDP3 components
Date: Wed, 13 Sep 2023 10:58:38 +0200 [thread overview]
Message-ID: <c0cf592a-3cde-4bad-431b-6d80c1970638@linaro.org> (raw)
In-Reply-To: <0b4f1ab2753d4fdb4934e8f76df6e584bba2d628.camel@mediatek.com>
On 13/09/2023 10:39, Moudy Ho (何宗原) wrote:
>>> @@ -63,7 +64,6 @@ properties:
>>> required:
>>> - compatible
>>> - reg
>>> - - interrupts
>>
>> Why? commit msg tells nothing about it. Why interrupt is not erquired
>> in
>> mt8173? How dropping such requirement is anyhow related to mt8195?
>>
>>
> The signals of the MDP engines are completely controlled by MTK's MUTEX
> for starting and stopping frame processing, eliminating the need for
> additional interrupts.
Then it does not look like related to this patch at all.
...
>>>
>>> reg:
>>> maxItems: 1
>>> @@ -50,17 +51,19 @@ properties:
>>> maxItems: 1
>>>
>>> clocks:
>>> - items:
>>> - - description: RDMA clock
>>> - - description: RSZ clock
>>> + oneOf:
>>> + - items:
>>> + - description: RDMA clock
>>> + - description: SRAM shared component clock
>>> + - items:
>>> + - description: RDMA clock
>>
>> Why now mt8183 can have SRAM clock optional? How changing mt8183 is
>> related to this patch?
>>
>> I'll finish the review, sorry fix basics here.
>>
>> Best regards,
>> Krzysztof
>>
> The RDMA of only the 8183 needed to share SRMA with other component due
> to the old desgin.
> I attempted to describe both the situation of the 8183 and new designs
> like the 8195, but it appears that this writing style may lead to
> misunderstandings.
> I am unsure if there are any ways to enhance it.
Just like many other bindings, just look at Qualcomm, use allOf to
restrict entries per variants.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-09-13 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:56 [PATCH v5 0/3] introduce more MDP3 components in mt8195 Moudy Ho
2023-09-12 7:56 ` [PATCH v5 1/3] dt-binding: mediatek: correct MDP3 node with generic names Moudy Ho
2023-09-12 7:56 ` [PATCH v5 2/3] dt-binding: mediatek: integrate MDP RDMA to one binding Moudy Ho
2023-09-12 8:16 ` Krzysztof Kozlowski
2023-09-13 3:04 ` Moudy Ho (何宗原)
2023-09-13 6:37 ` Krzysztof Kozlowski
2023-09-12 7:56 ` [PATCH v5 3/3] dt-binding: mediatek: add MediaTek mt8195 MDP3 components Moudy Ho
2023-09-12 8:19 ` Krzysztof Kozlowski
2023-09-13 8:39 ` Moudy Ho (何宗原)
2023-09-13 8:58 ` Krzysztof Kozlowski [this message]
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=c0cf592a-3cde-4bad-431b-6d80c1970638@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Moudy.Ho@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).