From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Yingying Tang <quic_yintang@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Yijie Yang <yijie.yang@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Yingying Tang <yintang@qti.qualcomm.com>,
miaoqing.pan@oss.qualcomm.com,
"stone Zhang (Stone)" <stonez@qti.qualcomm.com>,
zhichen@qti.qualcomm.com
Subject: Re: [PATCH v8 3/3] arm64: dts: qcom: Add base HAMOA-IOT-EVK board
Date: Tue, 2 Sep 2025 12:09:26 +0200 [thread overview]
Message-ID: <d13d416d-507c-4f74-91f5-38447ac39599@oss.qualcomm.com> (raw)
In-Reply-To: <23d10901-6b8a-41fb-8cb2-e8e361093561@quicinc.com>
On 9/2/25 8:56 AM, Yingying Tang wrote:
>
>
> On 9/2/2025 10:37 AM, Dmitry Baryshkov wrote:
>> On Mon, Sep 01, 2025 at 11:02:24AM +0800, Yingying Tang wrote:
>>>
>>>
>>> On 8/28/2025 7:18 PM, Dmitry Baryshkov wrote:
>>>> On Thu, Aug 28, 2025 at 12:48:47PM +0800, 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.
[...]
>>>>> + wcn7850-pmu {
>>>>> + compatible = "qcom,wcn7850-pmu";
>>>>> +
>>>>> + vdd-supply = <&vreg_wcn_0p95>;
>>>>> + vddio-supply = <&vreg_l15b_1p8>;
>>>>> + vddaon-supply = <&vreg_wcn_0p95>;
>>>>> + vdddig-supply = <&vreg_wcn_0p95>;
>>>>> + vddrfa1p2-supply = <&vreg_wcn_1p9>;
>>>>> + vddrfa1p8-supply = <&vreg_wcn_1p9>;
>>>>> +
>>>>> + bt-enable-gpios = <&tlmm 116 GPIO_ACTIVE_HIGH>;
>>>>
>>>> Okay, so how is WiFi controlled? Is there a GPIO? The DT should be
>>>> describing the hardware, not the UEFI behaviour.
>>>>
>>> Hi Dmitry, as I described in previous mail, On hamoa platfrom whole wifi module's power supply and enable gpio are voted in UEFI.
>>> Hamoa is PC platform, so BIOS/UEFI behavior is compatible with Windows/ACPI architecture. UEFI is responsible for enabling power supply
>>> for all devices which may be used in boot phase (such as WLAN may be used to boot from network).
>>
>> This is not completely relevant. You are describing driver / Linux /
>> bootloader behaviour. I asked if there is a GPIO in the hardware. If
>> there is one, please add it here.
>
> Hi Dimitry,
>
> During the UEFI boot phase, the WLAN enable GPIO has already been asserted, and the WLAN chip is functioning normally.
> If we include this GPIO in the kernel device tree, when the kernel configures this GPIO, its voltage level may experience a brief glitch, which could cause the WLAN chip to reset and result in a PCIe link down.
The WCN pwrseq code handles this already, please simply describe the
hardware like the platform firmware description which you're creating
is supposed to
Konrad
next prev parent reply other threads:[~2025-09-02 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 4:48 [PATCH v8 0/3] Initial support for Qualcomm Hamoa IOT EVK board Yijie Yang
2025-08-28 4:48 ` [PATCH v8 1/3] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board Yijie Yang
2025-08-28 4:48 ` [PATCH v8 2/3] arm64: dts: qcom: Add HAMOA-IOT-SOM platform Yijie Yang
2025-08-28 4:48 ` [PATCH v8 3/3] arm64: dts: qcom: Add base HAMOA-IOT-EVK board Yijie Yang
2025-08-28 11:15 ` Dmitry Baryshkov
2025-08-29 0:56 ` Yijie Yang
2025-08-28 11:18 ` Dmitry Baryshkov
2025-09-01 3:02 ` Yingying Tang
2025-09-02 2:37 ` Dmitry Baryshkov
2025-09-02 6:56 ` Yingying Tang
2025-09-02 9:50 ` Dmitry Baryshkov
2025-09-02 10:09 ` Konrad Dybcio [this message]
2025-09-01 8:00 ` Yijie 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=d13d416d-507c-4f74-91f5-38447ac39599@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoqing.pan@oss.qualcomm.com \
--cc=quic_yintang@quicinc.com \
--cc=robh@kernel.org \
--cc=stonez@qti.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.com \
--cc=yintang@qti.qualcomm.com \
--cc=zhichen@qti.qualcomm.com \
/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).