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>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>
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 v4 1/2] dt-bindings: memory: mediatek: Add SMI reset and clamp for MT8188
Date: Fri, 7 Mar 2025 08:04:49 +0100 [thread overview]
Message-ID: <8d90731b-4b5a-45a8-83d1-4351044f59c7@kernel.org> (raw)
In-Reply-To: <9305a4fd6829e5e2ae6c3247d11b9f47ed277f8b.camel@mediatek.com>
On 07/03/2025 07:38, Friday Yang (杨阳) wrote:
> On Thu, 2025-03-06 at 13:48 +0100, Krzysztof Kozlowski wrote:
>> External email : Please do not click links or open attachments until
>> you have verified the sender or the content.
>>
>>
>> On 06/03/2025 13:45, Friday Yang (杨阳) wrote:
>>>>> + const: mediatek,mt8188-smi-larb
>>>>> + mediatek,larb-id:
>>>>> + oneOf:
>>>>
>>>> Are you really sure that you need 'oneOf' here? :-)
>>>>
>>>> Regards,
>>>> Angelo
>>>
>>> Yes, I have tested it. If I try to modify the 'examples'
>>> like this. That is:
>>> change the compatible to "mediatek,mt8188-smi-larb",
>>> add 'mediatek,larb-id = <10>;'
>>>
>>> examples:
>>> - |+
>>> #include <dt-bindings/clock/mt8173-clk.h>
>>> #includ
>>> e <dt-bindings/power/mt8173-power.h>
>>>
>>> larb1: larb@16010000 {
>>> compatible = "mediatek,mt8188-smi-larb";
>>> reg = <0x16010000 0x1000>;
>>> mediatek,smi = <&smi_common>;
>>> mediatek,larb-id = <10>;
>>> power-domains = <&scpsys MT8188_POWER_DOMAIN_VDEC>;
>>> clocks = <&vdecsys CLK_VDEC_CKEN>,
>>> <&vdecsys CLK_VDEC_LARB_CKEN>;
>>> clock-names = "apb", "smi";
>>> };
>>>
>>> The 'dt_binding_check' could give the following
>>> errors:
>>>
>>> Documentation/devicetree/bindings/memory-controllers/mediatek,smi-
>>> larb.example.dtb: larb@16010000: 'resets' is a required property
>>> from schema $id:
>>>
> https://urldefense.com/v3/__http://devicetree.org/schemas/memory-controllers/mediatek,smi-larb.yaml*__;Iw!!CTRNKA9wMg0ARbw!kEwWhxyfjVtuHKBHazZGRaFdlmrU2bcIsiVDcsUDzEIManMw2XIG9RgOzq773vtmqlR9_sWZDFhU09SV$
>>> Documentation/devicetree/bindings/memory-controllers/mediatek,smi-
>>> larb.example.dtb: larb@16010000: 'reset-names' is a required
>>> property
>>> from schema $id:
>>>
> https://urldefense.com/v3/__http://devicetree.org/schemas/memory-controllers/mediatek,smi-larb.yaml*__;Iw!!CTRNKA9wMg0ARbw!kEwWhxyfjVtuHKBHazZGRaFdlmrU2bcIsiVDcsUDzEIManMw2XIG9RgOzq773vtmqlR9_sWZDFhU09SV$
>>>
>>> And this is what I want to achieve. On the MediaTek MT8188 SoC
>>> platform, 'resets' and 'reset-names' are only required for SMI
>>> LARBs
>>> located in image, camera and ipe subsys. Others can be ignored. And
>>> the
>>> 'larb-id' of these SMI LARBs are shown in this array: [ 9, 10, 11,
>>> 12,
>>> 13, 16, 17, 18, 19, 20 ].
>>>
>>> Please feel free to let me know if you have any doubts.
>>
>> You did not really answer the question. Where is anything about oneOf
>> in
>> your reply?
>>
>> I am dropping this patchset from my queue.
>>
>
> In this SoC, we encountered power-off failures and SMI bus hang issues
> during camera stress tests. SMI LARBs located in the image, IPE, and
> camera subsystems need to implement a reset, while other LARBs do not
> require it.
>
> The 'mediatek,larb-id' for SMI LARBs in the image, IPE, and camera
> subsystems are as follows:
> - image subsystem: 9, 10, 11, 12, 16
> - IPE subsystem: 13
> - camera subsystem: 17, 18, 19, 20
>
> Therefore, we believe that 'mediatek,larb-id' should be 'oneOf' the
So explain me where is the second condition?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-07 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 7:48 [PATCH v4 0/2] Add SMI reset and clamp for MediaTek MT8188 SoC Friday Yang
2025-02-21 7:48 ` [PATCH v4 1/2] dt-bindings: memory: mediatek: Add SMI reset and clamp for MT8188 Friday Yang
2025-02-24 8:41 ` AngeloGioacchino Del Regno
2025-03-06 12:45 ` Friday Yang (杨阳)
2025-03-06 12:48 ` Krzysztof Kozlowski
2025-03-07 6:38 ` Friday Yang (杨阳)
2025-03-07 7:04 ` Krzysztof Kozlowski [this message]
2025-03-07 8:14 ` Friday Yang (杨阳)
2025-03-07 8:37 ` Krzysztof Kozlowski
2025-02-21 7:48 ` [PATCH v4 2/2] memory: mtk-smi: mt8188: " Friday Yang
2025-02-24 8:41 ` AngeloGioacchino Del Regno
2025-03-06 12:46 ` Friday Yang (杨阳)
2025-02-22 9:45 ` [PATCH v4 0/2] Add SMI reset and clamp for MediaTek MT8188 SoC Krzysztof Kozlowski
2025-02-24 6:11 ` 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=8d90731b-4b5a-45a8-83d1-4351044f59c7@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