From: Yingying Tang <quic_yintang@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Shuai Zhang <shuaz@qti.qualcomm.com>, <quic_miaoqing@quicinc.com>,
<quic_zhichen@quicinc.com>
Subject: Re: [PATCH v3 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board
Date: Tue, 29 Jul 2025 17:39:02 +0800 [thread overview]
Message-ID: <c0b804e3-16ee-4e81-9aa8-4b6051b5af03@quicinc.com> (raw)
In-Reply-To: <d14b2a0c-8304-497f-a662-5b93dbaaa1ed@oss.qualcomm.com>
On 7/29/2025 4:37 PM, Konrad Dybcio wrote:
> On 7/29/25 7:51 AM, Yijie Yang wrote:
>>
>>
>> On 2025-07-29 09:32, 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@oss.qualcomm.com>
>>> ---
>
> [...]>> + vreg_wcn_3p3: regulator-wcn-3p3 {
>>> + compatible = "regulator-fixed";
>>> +
>>> + regulator-name = "VREG_WCN_3P3";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> +
>>> + gpio = <&tlmm 214 GPIO_ACTIVE_HIGH>;
>>> + enable-active-high;
>>> +
>>> + pinctrl-0 = <&wcn_sw_en>;
>>> + pinctrl-names = "default";
>>> +
>>> + regulator-boot-on;
>>
>> It should be set to 'regulator-always-on'.
>
> Are you sure? Turning off Wi-Fi sounds like a valid usecase..
Hi Konard, It is m.2 interface on Hamoa. The PCIe power of m.2 should be always on.
Even on QCOM's B2B interface, we are unable to dynamically control the power of PCIe devices on upstream kernel.
The PCIe specification does not support dynamic power control between the PCIe device and the RC.
PCIe power should be always on here.
>
> Konrad
next prev parent reply other threads:[~2025-07-29 9:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 1:31 [PATCH v3 0/4] Initial support for Qualcomm Hamoa IOT EVK board Yijie Yang
2025-07-29 1:31 ` [PATCH v3 1/4] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board Yijie Yang
2025-07-30 7:14 ` Krzysztof Kozlowski
2025-07-29 1:31 ` [PATCH v3 2/4] firmware: qcom: scm: Allow QSEECOM on HAMOA-IOT-EVK Yijie Yang
2025-07-29 1:31 ` [PATCH v3 3/4] arm64: dts: qcom: Add HAMOA-IOT-SOM platform Yijie Yang
2025-07-29 8:36 ` Konrad Dybcio
2025-07-29 10:44 ` Dmitry Baryshkov
2025-07-30 1:11 ` Yijie Yang
2025-07-30 6:44 ` Krzysztof Kozlowski
2025-07-30 7:13 ` Yijie Yang
2025-07-31 15:02 ` Krzysztof Kozlowski
2025-07-29 1:32 ` [PATCH v3 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board Yijie Yang
2025-07-29 5:51 ` Yijie Yang
2025-07-29 8:37 ` Konrad Dybcio
2025-07-29 9:39 ` Yingying Tang [this message]
2025-07-31 11:33 ` Konrad Dybcio
2025-07-29 10:37 ` Dmitry Baryshkov
2025-07-30 1:07 ` Yijie Yang
2025-07-30 6:28 ` Yijie Yang
2025-07-30 18:42 ` Dmitry Baryshkov
2025-07-31 8:45 ` Yijie Yang
2025-07-31 20:22 ` Dmitry Baryshkov
2025-08-01 1:48 ` Yijie Yang
2025-08-01 10:39 ` Konrad Dybcio
2025-08-01 17:54 ` Dmitry Baryshkov
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=c0b804e3-16ee-4e81-9aa8-4b6051b5af03@quicinc.com \
--to=quic_yintang@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@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=quic_miaoqing@quicinc.com \
--cc=quic_zhichen@quicinc.com \
--cc=robh@kernel.org \
--cc=shuaz@qti.qualcomm.com \
--cc=yijie.yang@oss.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