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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fd8dd19a-a15b-48a3-ab14-9c63e617ed10@quicinc.com>
Date: Tue, 10 Dec 2024 10:37:44 +0800
From: "Yu Zhang (Yuriy)" <quic_yuzha@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>, <andersson@...nel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>
CC: <agross@...nel.org>, <ath11k@...ts.infradead.org>,
        <dmitry.baryshkov@...aro.org>, <konradybcio@...nel.org>,
        <kvalo@...nel.org>, <linux-media@...r.kernel.org>,
        <mchehab@...nel.org>, <quic_jjohnson@...cinc.com>,
        <quic_miaoqing@...cinc.com>, <quic_vgarodia@...cinc.com>,
        <stanimir.k.varbanov@...il.com>, <quic_jiaymao@...cinc.com>
Subject: Re: [PATCH v3] arm64: dts: qcom: qcs615: add WiFi/BT nodes



On 12/6/2024 8:16 PM, Konrad Dybcio wrote:
> On 6.12.2024 4:22 AM, Yu Zhang (Yuriy) wrote:
>>
>>
>> On 12/6/2024 1:14 AM, Konrad Dybcio wrote:
>>> On 3.12.2024 7:03 AM, Yu Zhang(Yuriy) wrote:
>>>> Add a node for the PMU module of the WCN6855 present on the qcs615
>>>> board. Assign its LDO power outputs to the existing WiFi/BT module.
>>>>
>>>
>>> subject:
>>>
>>> arm64: dts: qcom: qcs615-ride: ....
>>>
>>> [...]
>>>
>>>> +
>>>> +    vreg_conn_1p8: vreg_conn_1p8 {
>>>> +        compatible = "regulator-fixed";
>>>> +        regulator-name = "vreg_conn_1p8";
>>>> +        startup-delay-us = <4000>;
>>>> +        enable-active-high;
>>>> +        gpio = <&pm8150_gpios 1 GPIO_ACTIVE_HIGH>;
>>>> +    };
>>>> +
>>>> +    vreg_conn_pa: vreg_conn_pa {
>>>> +        compatible = "regulator-fixed";
>>>> +        regulator-name = "vreg_conn_pa";
>>>> +        startup-delay-us = <4000>;
>>>> +        enable-active-high;
>>>> +        gpio = <&pm8150_gpios 6 GPIO_ACTIVE_HIGH>;
>>>> +    };
>>>
>>> Are any of these boot-on?
>>>
>> Yes, these are used wcn6855-pmu:
>>       vddio-supply = <&vreg_conn_pa>;
>>       vddpmu-supply = <&vreg_conn_1p8>;
> 
> What i meant is, whether these regulators are enabled at boot
> time (i.e. without software intervention). If that's the case,
> `regulator-boot-on;` should be added
> 
No need regulator-boot-on, it was triggered by the 
software(pci_pwrctl_pwrseq_driver).
> Konrad
Yu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ