[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20829683-b2ce-4aaa-beb4-4ca5774350a2@oss.qualcomm.com>
Date: Fri, 25 Jul 2025 17:36:37 +0800
From: Yijie Yang <yijie.yang@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board
On 2025-07-25 17:18, Krzysztof Kozlowski wrote:
> On 25/07/2025 11:01, Yijie Yang wrote:
>>
>> wcn7850_pmu: wcn7850-pmu@...x {
>> compatible = "qcom,wcn7850-pmu";
>> reg = <0x...>;
>> vdd-supply = <&dummy_reg>;
>> vddaon-supply = <&dummy_reg>;
>> vdddig-supply = <&dummy_reg>;
>> vddrfa1p2-supply = <&dummy_reg>;
>> vddrfa1p8-supply = <&dummy_reg>;
>> };
>> This approach ensures the DTB passes schema checks while keeping the
>> implementation clean and consistent with the actual platform setup. Do
>> you think this is appropriate?
>
> No. There is no dummy regulator in the hardware, so you cannot add it to
> the DTS.
What should I do in this case? Is it acceptable to deviate from the
dt-binding rules due to differences in firmware behavior? Otherwise,
I’ll need to revert to the first version, leave a TODO in the DTS, and
wait for someone to properly model the M.2 card.
>
> Best regards,
> Krzysztof
--
Best Regards,
Yijie
Powered by blists - more mailing lists