From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Friday Yang (杨阳)" <Friday.Yang@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"Yong Wu (吴勇)" <Yong.Wu@mediatek.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v11 1/2] dt-bindings: memory: mediatek: Add SMI reset and clamp for MT8188
Date: Fri, 31 Oct 2025 13:07:51 +0100 [thread overview]
Message-ID: <008ce91a-9037-4f18-9639-f1ccda277624@kernel.org> (raw)
In-Reply-To: <1c84112b5a7fa48d8422f531e660aa1b49ec6487.camel@mediatek.com>
On 31/10/2025 07:10, Friday Yang (杨阳) wrote:
> On Sat, 2025-10-18 at 18:42 +0200, Krzysztof Kozlowski wrote:
>> External email : Please do not click links or open attachments until
>> you have verified the sender or the content.
>>
>>
>> On 17/09/2025 14:07, Friday Yang wrote:
>>> Add 'resets' and 'reset-names' properties for SMI LARBs to support
>>> SMI reset operations.
>>
>> Not informative...
>>
>>> diff --git a/Documentation/devicetree/bindings/memory-
>>> controllers/mediatek,smi-larb.yaml
>>> b/Documentation/devicetree/bindings/memory-
>>> controllers/mediatek,smi-larb.yaml
>>> index 2e7fac4b5094..fc5feb2eac1f 100644
>>> --- a/Documentation/devicetree/bindings/memory-
>>> controllers/mediatek,smi-larb.yaml
>>> +++ b/Documentation/devicetree/bindings/memory-
>>> controllers/mediatek,smi-larb.yaml
>>> @@ -70,6 +70,12 @@ properties:
>>> description: the hardware id of this larb. It's only required
>>> when this
>>> hardware id is not consecutive from its M4U point of view.
>>>
>>> + resets:
>>> + maxItems: 1
>>> +
>>> + reset-names:
>>> + const: larb
>>
>> Is the reset valid for all existing devices as well? Commit msg does
>> not
>> explain that... it is pretty useless - you say what you did. We see
>> that
>> from the diff. Explain something not obvious.
>>
>
> Thanks, I could add more descriptions here, like below:
>
> On the MediaTek MT8188 SoC, bus glitches may occur during MTCMOS
> on/off transitions. To prevent these glitches from causing errors,
> SMI requires clamp and reset operations. This issue specifically
> affects the image, camera, and IPE subsystems.
This explains why you need it. But I asked more questions than only "whY".
Read the question:
"Is the reset valid for all existing devices as well?"
Where is the answer for that? I still do not know...
Do not reply to only pieces of review.
> This change adds the
> 'resets' and 'reset-names' properties to the SMI LARBs within
> these subsystems to support the necessary reset operations.
Read again my message:
" it is pretty useless - you say what you did"
That's the same, drop.
So again you just cared to implement only piece of review.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-31 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 12:07 [PATCH v11 0/2] Add SMI reset and clamp for MediaTek MT8188 SoC Friday Yang
2025-09-17 12:07 ` [PATCH v11 1/2] dt-bindings: memory: mediatek: Add SMI reset and clamp for MT8188 Friday Yang
2025-10-18 16:42 ` Krzysztof Kozlowski
2025-10-31 6:10 ` Friday Yang (杨阳)
2025-10-31 12:07 ` Krzysztof Kozlowski [this message]
2025-09-17 12:07 ` [PATCH v11 2/2] memory: mtk-smi: mt8188: Add SMI reset and clamp Friday Yang
2025-09-17 12:55 ` AngeloGioacchino Del Regno
2025-09-20 2:11 ` Yong Wu (吴勇)
2025-10-18 16:41 ` Krzysztof Kozlowski
2025-10-31 6:10 ` Friday Yang (杨阳)
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=008ce91a-9037-4f18-9639-f1ccda277624@kernel.org \
--to=krzk@kernel.org \
--cc=Friday.Yang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Yong.Wu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).