linux-kernel - Re: [PATCH v2 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cf84a8ef-9f4e-4f13-b41e-9525e21a913b@oss.qualcomm.com>
Date: Fri, 25 Jul 2025 17:01:03 +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 14:51, Krzysztof Kozlowski wrote:
> On 24/07/2025 10:15, Yijie Yang wrote:
>> The HAMOA-IOT-EVK is an evaluation platform for IoT products, composed of
>> the Hamoa IoT SoM and a carrier board. Together, they form a complete
>> embedded system capable of booting to UART.
>>
>> This change enables and overlays the following peripherals on the carrier
>> board:
>> - UART
>> - On-board regulators
>> - USB Type-C mux
>> - Pinctrl
>> - Embedded USB (EUSB) repeaters
>> - NVMe
>> - pmic-glink
>> - USB DisplayPorts
>>
>> Written with contributions from Shuai Zhang (added Bluetooth) and Yongxing
>> Mou (added USB DisplayPorts).
>>
>> Signed-off-by: Yijie Yang <yijie.yang@....qualcomm.com>
>> ---
> 
> This still wasn't tested. Use the automated tools instead of community
> reviewers... Your internal guideline documents how to do it.

Thanks for pointing that out. I’ll update the node name from 
wcn_usb_sw_n_state to wcn-usb-sw-n-state to align with the schema 
pattern and eliminate unevaluated property warnings.

Regarding the regulator properties for wcn7850-pmu, as discussed in the 
previous version, the required supplies are already configured via UEFI. 
Therefore, redefining them in the device tree would be redundant. To 
satisfy schema validation without introducing unnecessary definitions, I 
plan to use a dummy regulator as a placeholder.

Here’s the pseudocode I intend to use:

dummy_reg: regulator-dummy {
     compatible = "regulator-dummy";
};

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?

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie