From: yuanjiey <yuanjie.yang@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, tingwei.zhang@oss.qualcomm.com
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Add base HAMOA-IOT-COME board
Date: Wed, 1 Jul 2026 16:51:05 +0800 [thread overview]
Message-ID: <akTU-YQkms64qivB@YUANJIEY2.ap.qualcomm.com> (raw)
In-Reply-To: <20260701-uptight-piquant-raccoon-abceb4@quoll>
On Wed, Jul 01, 2026 at 09:29:34AM +0200, Krzysztof Kozlowski wrote:
> On Tue, Jun 30, 2026 at 03:10:12PM +0800, Yuanjie Yang wrote:
> > Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
> > ---
> > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > .../boot/dts/qcom/hamoa-iot-come-sip.dtsi | 9 ++
> > .../boot/dts/qcom/hamoa-iot-come-som.dtsi | 38 ++++++
> > arch/arm64/boot/dts/qcom/hamoa-iot-come.dts | 108 ++++++++++++++++++
> > 4 files changed, 156 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/qcom/hamoa-iot-come-sip.dtsi
> > create mode 100644 arch/arm64/boot/dts/qcom/hamoa-iot-come-som.dtsi
> > create mode 100644 arch/arm64/boot/dts/qcom/hamoa-iot-come.dts
> >
> > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> > index 6f33c4e2f09c..549287e3eeba 100644
> > --- a/arch/arm64/boot/dts/qcom/Makefile
> > +++ b/arch/arm64/boot/dts/qcom/Makefile
> > @@ -16,6 +16,7 @@ dtb-$(CONFIG_ARCH_QCOM) += apq8096sg-db820c.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += apq8096-ifc6640.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += eliza-mtp.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += glymur-crd.dtb
> > +dtb-$(CONFIG_ARCH_QCOM) += hamoa-iot-come.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += hamoa-iot-evk.dtb
> >
> > hamoa-iot-evk-el2-dtbs := hamoa-iot-evk.dtb x1-el2.dtbo
> > diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-come-sip.dtsi b/arch/arm64/boot/dts/qcom/hamoa-iot-come-sip.dtsi
> > new file mode 100644
> > index 000000000000..935af96c2b85
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/qcom/hamoa-iot-come-sip.dtsi
>
> What is the point of this file?
This SiP hardware is effectively the same as the SoM on the Hamoa EVK.
It's just called differently on a different board. I want to use this
file to include hamoa-iot-som.dtsi header to show this idea.
Thanks,
Yuanjie
> > @@ -0,0 +1,9 @@
> > +// SPDX-License-Identifier: BSD-3-Clause
> > +/*
> > + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> > + */
> > +
> > +#include "hamoa-iot-som.dtsi"
> > +
> > +/ {
> > +};
>
> It is completely empty.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-07-01 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:10 [PATCH 0/2] Initial support for Qualcomm Hamoa IOT COME board Yuanjie Yang
2026-06-30 7:10 ` [PATCH 1/2] dt-bindings: arm: qcom: Document HAMOA-IOT-COME board Yuanjie Yang
2026-07-01 7:28 ` Krzysztof Kozlowski
2026-07-01 8:47 ` yuanjiey
2026-06-30 7:10 ` [PATCH 2/2] arm64: dts: qcom: Add base " Yuanjie Yang
2026-07-01 7:29 ` Krzysztof Kozlowski
2026-07-01 8:51 ` yuanjiey [this message]
2026-07-01 10:19 ` Krzysztof Kozlowski
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=akTU-YQkms64qivB@YUANJIEY2.ap.qualcomm.com \
--to=yuanjie.yang@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@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