From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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
Subject: Re: [PATCH 3/4] arm64: dts: qcom: Add HAMOA-IOT-SOM platform
Date: Fri, 18 Jul 2025 14:33:50 +0800 [thread overview]
Message-ID: <822af9fe-5db0-4620-8f08-9232c608d443@oss.qualcomm.com> (raw)
In-Reply-To: <b4nxjsx4fu4xmookpxukumw36wlcpzelh6axjucqe4lyswptm4@kczsldalq53n>
On 2025-07-18 02:52, Dmitry Baryshkov wrote:
> On Wed, Jul 16, 2025 at 05:08:41PM +0800, Yijie Yang wrote:
>> The HAMOA-IOT-SOM is a compact computing module that integrates a System
>> on Chip (SoC) — specifically the x1e80100 — along with essential
>> components optimized for IoT applications. It is designed to be mounted on
>> carrier boards, enabling the development of complete embedded systems.
>>
>> This change enables and overlays the following components:
>> - Regulators on the SOM
>> - Reserved memory regions
>> - PCIe6a and its PHY
>> - PCIe4 and its PHY
>> - USB0 through USB6 and their PHYs
>> - ADSP, CDSP
>> - WLAN, Bluetooth (M.2 interface)
>>
>> Written with contributions from Yingying Tang (added PCIe4 and its PHY to
>> enable WLAN).
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi | 607 ++++++++++++++++++++++++++++
>> 1 file changed, 607 insertions(+)
>>
>
>> +&remoteproc_adsp {
>> + firmware-name = "qcom/hamoa-iot/adsp.mbn",
>> + "qcom/hamoa-iot/adsp_dtb.mbn";
>
> Is there a significant difference qcom/x1e80100/adsp.mbn ? If not, can
> we use that firmware?
I believe there are differences in firmware between it and the EVK, even
if they’re minor. Therefore, it's better to maintain a dedicated folder
for each board and move the code to the carrier board.
>
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_cdsp {
>> + firmware-name = "qcom/hamoa-iot/cdsp.mbn",
>> + "qcom/hamoa-iot/cdsp_dtb.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>
--
Best Regards,
Yijie
next prev parent reply other threads:[~2025-07-18 6:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:08 [PATCH 0/4] Initial support for Qualcomm Hamoa IOT EVK board Yijie Yang
2025-07-16 9:08 ` [PATCH 1/4] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board Yijie Yang
2025-07-16 9:30 ` Krzysztof Kozlowski
2025-07-16 10:26 ` Konrad Dybcio
2025-07-16 10:32 ` Krzysztof Kozlowski
2025-07-17 2:14 ` Yijie Yang
2025-07-16 9:08 ` [PATCH 2/4] firmware: qcom: scm: Allow QSEECOM on HAMOA-IOT-EVK Yijie Yang
2025-07-16 9:08 ` [PATCH 3/4] arm64: dts: qcom: Add HAMOA-IOT-SOM platform Yijie Yang
2025-07-17 16:14 ` Stephan Gerhold
2025-07-17 20:10 ` Konrad Dybcio
2025-07-17 20:14 ` Stephan Gerhold
2025-07-23 7:53 ` Yijie Yang
2025-07-18 6:27 ` Yijie Yang
2025-07-17 18:52 ` Dmitry Baryshkov
2025-07-18 6:33 ` Yijie Yang [this message]
2025-07-18 9:26 ` Dmitry Baryshkov
2025-07-22 11:09 ` Yijie Yang
2025-07-18 6:40 ` Krzysztof Kozlowski
2025-07-23 6:28 ` Krzysztof Kozlowski
2025-07-23 6:44 ` Yijie Yang
2025-07-23 11:26 ` Dmitry Baryshkov
2025-07-24 0:48 ` Yijie Yang
2025-07-16 9:08 ` [PATCH 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board Yijie Yang
2025-07-17 16:37 ` Stephan Gerhold
2025-07-18 8:19 ` Yijie Yang
2025-07-18 9:27 ` Dmitry Baryshkov
2025-07-18 9:33 ` Stephan Gerhold
2025-07-18 11:46 ` Dmitry Baryshkov
2025-07-17 15:56 ` [PATCH 0/4] Initial support for Qualcomm Hamoa IOT EVK board Rob Herring (Arm)
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=822af9fe-5db0-4620-8f08-9232c608d443@oss.qualcomm.com \
--to=yijie.yang@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=robh@kernel.org \
/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).