[PATCH v2 0/2] Initial support for Qualcomm Hamoa IOT COME board

[PATCH v2 0/2] Initial support for Qualcomm Hamoa IOT COME board

[Yuanjie Yang]

Introduce the device tree, DT bindings for HAMOA-IOT-COME board.

The system consists of a SoM mounted on a carrier board. The HAMOA-IOT-COME
SoM integrates the core system, including a SiP that contains the SoC and
related components.

The SiP on the HAMOA-IOT-COME SoM is equivalent to the HAMOA-IOT-EVK SoM.

┌───────────────────────────────┐
│          SoM (Module)         │
│   System on Module (small     │
│   pluggable board)            │
│                               │
│   ┌───────────────────────┐   │
│   │        SiP            │   │
│   │   System in Package   │   │
│   │        (chip)         │   │
│   │                       │   │
│   │   ┌───────────────┐   │   │
│   │   │     SoC       │   │   │
│   │   │               │   │   │
│   │   └───────────────┘   │   │
│   │                       │   │
│   │                       │   │
│   └───────────────────────┘   │
│                               │
└──────────────┬────────────────┘
               │ Plugs into
┌──────────────▼────────────────┐
│   Carrier Board (COME)        │
│                               │
└───────────────────────────────┘

Co-developed-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Co-developed-by: Ziyue zhang <ziyue.zhang@oss.qualcomm.com>
Signed-off-by: Ziyue zhang <ziyue.zhang@oss.qualcomm.com>
Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
---

Changes in v2:
- update commit msg
- fix binding error
- update pcie and usb DT
- Link to v1: https://lore.kernel.org/all/20260630071022.3256-1-yuanjie.yang@oss.qualcomm.com/
---

Yuanjie Yang (2):
  dt-bindings: arm: qcom: Add HAMOA-IOT-COME board
  arm64: dts: qcom: Add base HAMOA-IOT-COME board

 .../devicetree/bindings/arm/qcom.yaml         |   7 ++
 arch/arm64/boot/dts/qcom/Makefile             |   1 +
 .../boot/dts/qcom/hamoa-iot-come-som.dtsi     |  52 ++++++++
 arch/arm64/boot/dts/qcom/hamoa-iot-come.dts   | 116 ++++++++++++++++++
 4 files changed, 176 insertions(+)
 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


base-commit: c5e32e86ca02b003f86e095d379b38148999293d
-- 
2.43.0

[PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[Yuanjie Yang]

Document the device tree binding for the HAMOA-IOT-COME board based on
the Qualcomm X1E80100 SoC.

The platform consists of a system-on-module (SoM) mounted on a carrier
board. The SoM integrates the core system functionality, including a
SiP containing the X1E80100 SoC and its supporting components.

The COME SiP hardware is effectively the same as the SoM used on the
Qualcomm HAMOA EVK, while the carrier board provides the board-specific
peripherals and connectivity.

Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/arm/qcom.yaml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index c7c9a9279684..443191b12137 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1209,6 +1209,13 @@ properties:
               - qcom,x1e80100-qcp
           - const: qcom,x1e80100
 
+      - items:
+          - enum:
+              - qcom,hamoa-iot-come
+          - const: qcom,hamoa-iot-come-som
+          - const: qcom,hamoa-iot-som
+          - const: qcom,x1e80100
+
       - items:
           - enum:
               - qcom,hamoa-iot-evk
-- 
2.43.0

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[Krzysztof Kozlowski]

On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
> Document the device tree binding for the HAMOA-IOT-COME board based on
> the Qualcomm X1E80100 SoC.
> 
> The platform consists of a system-on-module (SoM) mounted on a carrier
> board. The SoM integrates the core system functionality, including a
> SiP containing the X1E80100 SoC and its supporting components.
> 
> The COME SiP hardware is effectively the same as the SoM used on the

Effectively the same or the same? I googled for "hamoa iot come" and it
gives me zero results. Provide some URLs describing both.

Are you calling same SoM differently based where did you mount it? That
would be complete opposite of the idea of SoM, so I have doubts that
this is SoM in the first place.

Best regards,
Krzysztof

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[yuanjiey]

On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
> > Document the device tree binding for the HAMOA-IOT-COME board based on
> > the Qualcomm X1E80100 SoC.
> > 
> > The platform consists of a system-on-module (SoM) mounted on a carrier
> > board. The SoM integrates the core system functionality, including a
> > SiP containing the X1E80100 SoC and its supporting components.
> > 
> > The COME SiP hardware is effectively the same as the SoM used on the
> 
> Effectively the same or the same? I googled for "hamoa iot come" and it
> gives me zero results. Provide some URLs describing both.
The same.


Here is pdf about the "hamoa iot come" SiP and SoM
link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf

The preliminary figure provides a complete overview of architecture, including the SiP, SoM.

In Block Diagram
hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.

Thanks,
Yuanjie

> Are you calling same SoM differently based where did you mount it? That
> would be complete opposite of the idea of SoM, so I have doubts that
> this is SoM in the first place.
> 
> Best regards,
> Krzysztof
> 

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[Krzysztof Kozlowski]

On 30/07/2026 11:54, yuanjiey wrote:
> On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
>> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
>>> Document the device tree binding for the HAMOA-IOT-COME board based on
>>> the Qualcomm X1E80100 SoC.
>>>
>>> The platform consists of a system-on-module (SoM) mounted on a carrier
>>> board. The SoM integrates the core system functionality, including a
>>> SiP containing the X1E80100 SoC and its supporting components.
>>>
>>> The COME SiP hardware is effectively the same as the SoM used on the
>>
>> Effectively the same or the same? I googled for "hamoa iot come" and it
>> gives me zero results. Provide some URLs describing both.
> The same.
> 
> 
> Here is pdf about the "hamoa iot come" SiP and SoM
> link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
> 
> The preliminary figure provides a complete overview of architecture, including the SiP, SoM.
> 
> In Block Diagram
> hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.

I see on that PDF "SOM-6820", not "Hamoa IoT Come".

I have an impression that all this and previous bindings and DTs did not
match reality at all. Or did not match how upstream works with such
hardware.

Best regards,
Krzysztof

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[Krzysztof Kozlowski]

On 30/07/2026 12:08, Krzysztof Kozlowski wrote:
> On 30/07/2026 11:54, yuanjiey wrote:
>> On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
>>> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
>>>> Document the device tree binding for the HAMOA-IOT-COME board based on
>>>> the Qualcomm X1E80100 SoC.
>>>>
>>>> The platform consists of a system-on-module (SoM) mounted on a carrier
>>>> board. The SoM integrates the core system functionality, including a
>>>> SiP containing the X1E80100 SoC and its supporting components.
>>>>
>>>> The COME SiP hardware is effectively the same as the SoM used on the
>>>
>>> Effectively the same or the same? I googled for "hamoa iot come" and it
>>> gives me zero results. Provide some URLs describing both.
>> The same.
>>
>>
>> Here is pdf about the "hamoa iot come" SiP and SoM
>> link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
>>
>> The preliminary figure provides a complete overview of architecture, including the SiP, SoM.
>>
>> In Block Diagram
>> hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.
> 
> I see on that PDF "SOM-6820", not "Hamoa IoT Come".
> 
> I have an impression that all this and previous bindings and DTs did not
> match reality at all. Or did not match how upstream works with such
> hardware.
> 

Adding more: I did ask in the past to properly represent SoM and
carriers. I pointed to other examples how this is done correctly. I did
look now inside and found absolutely no reference of actual product
called "Hamoa IoT" or "Purwa IoT". For sure there is no "Hamoa IoT Come"
SoM (sometimes COMe appears).

Look, this is a SoM:
https://www.toradex.com/computer-on-modules/verdin-arm-family/nxp-imx95

And you can find corresponding bindings and DTS in tree.

I refuse to accept more of this fake products trying to imitate well
known industry standards in their own way and effectively pushing some
downstream crap, just because that's how we do it in downstream.

Unless you can present us with such product details matching what you
send, I will be NAK-ing these and future patches like that.

Best regards,
Krzysztof

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[yuanjiey]

On Thu, Jul 30, 2026 at 12:23:56PM +0200, Krzysztof Kozlowski wrote:
> On 30/07/2026 12:08, Krzysztof Kozlowski wrote:
> > On 30/07/2026 11:54, yuanjiey wrote:
> >> On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
> >>> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
> >>>> Document the device tree binding for the HAMOA-IOT-COME board based on
> >>>> the Qualcomm X1E80100 SoC.
> >>>>
> >>>> The platform consists of a system-on-module (SoM) mounted on a carrier
> >>>> board. The SoM integrates the core system functionality, including a
> >>>> SiP containing the X1E80100 SoC and its supporting components.
> >>>>
> >>>> The COME SiP hardware is effectively the same as the SoM used on the
> >>>
> >>> Effectively the same or the same? I googled for "hamoa iot come" and it
> >>> gives me zero results. Provide some URLs describing both.
> >> The same.
> >>
> >>
> >> Here is pdf about the "hamoa iot come" SiP and SoM
> >> link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
> >>
> >> The preliminary figure provides a complete overview of architecture, including the SiP, SoM.
> >>
> >> In Block Diagram
> >> hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.
> > 
> > I see on that PDF "SOM-6820", not "Hamoa IoT Come".
> > 
> > I have an impression that all this and previous bindings and DTs did not
> > match reality at all. Or did not match how upstream works with such
> > hardware.
> > 
> 
> Adding more: I did ask in the past to properly represent SoM and
> carriers. I pointed to other examples how this is done correctly. I did
> look now inside and found absolutely no reference of actual product
> called "Hamoa IoT" or "Purwa IoT". For sure there is no "Hamoa IoT Come"
> SoM (sometimes COMe appears).

I check the hamoa iot evk board page:
https://docs.qualcomm.com/doc/80-77183-262/topic/Getting-started.html#get-familiar
and 
purwa iot evk board page:
https://docs.qualcomm.com/doc/80-80022-297/80-80022-297_REV_AC_Qualcomm_IQ-X_Series_Evaluation_Kit_-_Linux_Bringup_guide.pdf

And I see below info:

Dragonwing IQ-X7xxx EVK components:
The kit includes the following components:
Dragonwing IQ-X7xxx EVK mainboard
"System in package (SiP) "

I think the current naming of hamoa-iot-som.dtsi and purwa-iot-som.dtsi in the
Linux device tree is incorrect. They should be renamed to hamoa-iot-sip.dtsi
and purwa-iot-sip.dtsi.

hamoa-iot-som.dtsi --> hamoa-iot-sip.dtsi
purwa-iot-som.dtsi --> purwa-iot-sip.dtsi

> Look, this is a SoM:
> https://www.toradex.com/computer-on-modules/verdin-arm-family/nxp-imx95
> 
> And you can find corresponding bindings and DTS in tree.
> 
> I refuse to accept more of this fake products trying to imitate well
> known industry standards in their own way and effectively pushing some
> downstream crap, just because that's how we do it in downstream.
> 
> Unless you can present us with such product details matching what you
> send, I will be NAK-ing these and future patches like that.

Thanks for your tips:

I check hamoa come som page:
https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
and come board page:
https://www.advantech.com.cn/zh-cn/products/1-fc23ff/som-db5830/mod_16b1a718-27d6-4a4c-8684-e8f2a8e9c57b

So I should rename come binding with real devices name:
binding should be:

      - items:
          - enum:
              - hamoa-som6820-db5830.dts
          - const: hamoa-som6820.dtsi
          - const: qcom,hamoa-iot-sip
          - const: qcom,x1e80100


Thanks,
Yuanjie

> Best regards,
> Krzysztof

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[Krzysztof Kozlowski]

On 03/08/2026 08:14, yuanjiey wrote:
> On Thu, Jul 30, 2026 at 12:23:56PM +0200, Krzysztof Kozlowski wrote:
>> On 30/07/2026 12:08, Krzysztof Kozlowski wrote:
>>> On 30/07/2026 11:54, yuanjiey wrote:
>>>> On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
>>>>> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
>>>>>> Document the device tree binding for the HAMOA-IOT-COME board based on
>>>>>> the Qualcomm X1E80100 SoC.
>>>>>>
>>>>>> The platform consists of a system-on-module (SoM) mounted on a carrier
>>>>>> board. The SoM integrates the core system functionality, including a
>>>>>> SiP containing the X1E80100 SoC and its supporting components.
>>>>>>
>>>>>> The COME SiP hardware is effectively the same as the SoM used on the
>>>>>
>>>>> Effectively the same or the same? I googled for "hamoa iot come" and it
>>>>> gives me zero results. Provide some URLs describing both.
>>>> The same.
>>>>
>>>>
>>>> Here is pdf about the "hamoa iot come" SiP and SoM
>>>> link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
>>>>
>>>> The preliminary figure provides a complete overview of architecture, including the SiP, SoM.
>>>>
>>>> In Block Diagram
>>>> hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.
>>>
>>> I see on that PDF "SOM-6820", not "Hamoa IoT Come".
>>>
>>> I have an impression that all this and previous bindings and DTs did not
>>> match reality at all. Or did not match how upstream works with such
>>> hardware.
>>>
>>
>> Adding more: I did ask in the past to properly represent SoM and
>> carriers. I pointed to other examples how this is done correctly. I did
>> look now inside and found absolutely no reference of actual product
>> called "Hamoa IoT" or "Purwa IoT". For sure there is no "Hamoa IoT Come"
>> SoM (sometimes COMe appears).
> 
> I check the hamoa iot evk board page:
> https://docs.qualcomm.com/doc/80-77183-262/topic/Getting-started.html#get-familiar
> and 

It says it has "IQ-X7xxx module".

> purwa iot evk board page:
> https://docs.qualcomm.com/doc/80-80022-297/80-80022-297_REV_AC_Qualcomm_IQ-X_Series_Evaluation_Kit_-_Linux_Bringup_guide.pdf

And this is "IQ-X5xxx"

So how is this anyhow related to Hamoa IoT or Hamoa Iot Come?


> 
> And I see below info:
> 
> Dragonwing IQ-X7xxx EVK components:
> The kit includes the following components:
> Dragonwing IQ-X7xxx EVK mainboard
> "System in package (SiP) "
> 
> I think the current naming of hamoa-iot-som.dtsi and purwa-iot-som.dtsi in the
> Linux device tree is incorrect. They should be renamed to hamoa-iot-sip.dtsi
> and purwa-iot-sip.dtsi.

som/sip does not matter here. That's not what we discuss.


> 
> hamoa-iot-som.dtsi --> hamoa-iot-sip.dtsi
> purwa-iot-som.dtsi --> purwa-iot-sip.dtsi
> 
>> Look, this is a SoM:
>> https://www.toradex.com/computer-on-modules/verdin-arm-family/nxp-imx95
>>
>> And you can find corresponding bindings and DTS in tree.
>>
>> I refuse to accept more of this fake products trying to imitate well
>> known industry standards in their own way and effectively pushing some
>> downstream crap, just because that's how we do it in downstream.
>>
>> Unless you can present us with such product details matching what you
>> send, I will be NAK-ing these and future patches like that.
> 
> Thanks for your tips:
> 
> I check hamoa come som page:
> https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
> and come board page:
> https://www.advantech.com.cn/zh-cn/products/1-fc23ff/som-db5830/mod_16b1a718-27d6-4a4c-8684-e8f2a8e9c57b
> 
> So I should rename come binding with real devices name:
> binding should be:
> 
>       - items:
>           - enum:
>               - hamoa-som6820-db5830.dts
>           - const: hamoa-som6820.dtsi

No clue what is this. But the links above are Advantech.



Best regards,
Krzysztof

Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add HAMOA-IOT-COME board

[yuanjiey]

On Mon, Aug 03, 2026 at 08:36:11AM +0200, Krzysztof Kozlowski wrote:
> On 03/08/2026 08:14, yuanjiey wrote:
> > On Thu, Jul 30, 2026 at 12:23:56PM +0200, Krzysztof Kozlowski wrote:
> >> On 30/07/2026 12:08, Krzysztof Kozlowski wrote:
> >>> On 30/07/2026 11:54, yuanjiey wrote:
> >>>> On Thu, Jul 30, 2026 at 08:51:40AM +0200, Krzysztof Kozlowski wrote:
> >>>>> On Mon, Jul 27, 2026 at 03:07:16PM +0800, Yuanjie Yang wrote:
> >>>>>> Document the device tree binding for the HAMOA-IOT-COME board based on
> >>>>>> the Qualcomm X1E80100 SoC.
> >>>>>>
> >>>>>> The platform consists of a system-on-module (SoM) mounted on a carrier
> >>>>>> board. The SoM integrates the core system functionality, including a
> >>>>>> SiP containing the X1E80100 SoC and its supporting components.
> >>>>>>
> >>>>>> The COME SiP hardware is effectively the same as the SoM used on the
> >>>>>
> >>>>> Effectively the same or the same? I googled for "hamoa iot come" and it
> >>>>> gives me zero results. Provide some URLs describing both.
> >>>> The same.
> >>>>
> >>>>
> >>>> Here is pdf about the "hamoa iot come" SiP and SoM
> >>>> link: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
> >>>>
> >>>> The preliminary figure provides a complete overview of architecture, including the SiP, SoM.
> >>>>
> >>>> In Block Diagram
> >>>> hamoa come Qualcomm X-Elite SiP Module is the SoM on haoma evk.
> >>>
> >>> I see on that PDF "SOM-6820", not "Hamoa IoT Come".
> >>>
> >>> I have an impression that all this and previous bindings and DTs did not
> >>> match reality at all. Or did not match how upstream works with such
> >>> hardware.
> >>>
> >>
> >> Adding more: I did ask in the past to properly represent SoM and
> >> carriers. I pointed to other examples how this is done correctly. I did
> >> look now inside and found absolutely no reference of actual product
> >> called "Hamoa IoT" or "Purwa IoT". For sure there is no "Hamoa IoT Come"
> >> SoM (sometimes COMe appears).
> > 
> > I check the hamoa iot evk board page:
> > https://docs.qualcomm.com/doc/80-77183-262/topic/Getting-started.html#get-familiar
> > and 
> 
> It says it has "IQ-X7xxx module".
> 
> > purwa iot evk board page:
> > https://docs.qualcomm.com/doc/80-80022-297/80-80022-297_REV_AC_Qualcomm_IQ-X_Series_Evaluation_Kit_-_Linux_Bringup_guide.pdf
> 
> And this is "IQ-X5xxx"
> 
> So how is this anyhow related to Hamoa IoT or Hamoa Iot Come?

Our current naming does not clearly reflect the specific hardware document it refers to.

Maybe "IQ-X7181 evk module" and "IQ-X5121 evk module" can would better reflect the actual
hardware configuration.  
just like:
hamoa-iot-som.dtsi --> iq-x7181-evk-som.dtsi
purwa-iot-som.dtsi --> iq-x5121-evk-som.dtsi

IQ-X7181 evk board: 
do some dts name fix, just like:

hamoa-iq-x7181-evk.dts
  iq-x7181-evk-som.dtsi
    hamoa.dtsi        

> 
> > 
> > And I see below info:
> > 
> > Dragonwing IQ-X7xxx EVK components:
> > The kit includes the following components:
> > Dragonwing IQ-X7xxx EVK mainboard
> > "System in package (SiP) "
> > 
> > I think the current naming of hamoa-iot-som.dtsi and purwa-iot-som.dtsi in the
> > Linux device tree is incorrect. They should be renamed to hamoa-iot-sip.dtsi
> > and purwa-iot-sip.dtsi.
> 
> som/sip does not matter here. That's not what we discuss.
> 
> 
> > 
> > hamoa-iot-som.dtsi --> hamoa-iot-sip.dtsi
> > purwa-iot-som.dtsi --> purwa-iot-sip.dtsi
> > 
> >> Look, this is a SoM:
> >> https://www.toradex.com/computer-on-modules/verdin-arm-family/nxp-imx95
> >>
> >> And you can find corresponding bindings and DTS in tree.
> >>
> >> I refuse to accept more of this fake products trying to imitate well
> >> known industry standards in their own way and effectively pushing some
> >> downstream crap, just because that's how we do it in downstream.
> >>
> >> Unless you can present us with such product details matching what you
> >> send, I will be NAK-ing these and future patches like that.
> > 
> > Thanks for your tips:
> > 
> > I check hamoa come som page:
> > https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
> > and come board page:
> > https://www.advantech.com.cn/zh-cn/products/1-fc23ff/som-db5830/mod_16b1a718-27d6-4a4c-8684-e8f2a8e9c57b
> > 
> > So I should rename come binding with real devices name:
> > binding should be:
> > 
> >       - items:
> >           - enum:
> >               - hamoa-som6820-db5830.dts
> >           - const: hamoa-som6820.dtsi
> 
> No clue what is this. But the links above are Advantech.

correct here: 

      - items:
          - enum:
              - advantech,som-db5830            
          - const: advantech,som-6820
          - const: qcom,iq-x7181-evk-som
          - const: qcom,x1e80100


Thanks,
Yuanjie


> 
> 
> Best regards,
> Krzysztof

[PATCH v2 2/2] arm64: dts: qcom: Add base HAMOA-IOT-COME board

[Yuanjie Yang]

Add the initial device tree for the HAMOA-IOT-COME platform based on
the Qualcomm X1E80100 SoC.

The platform consists of a system-on-module (SoM) mounted on a carrier
board. The SoM integrates the core system functionality through a SiP
containing the X1E80100 SoC and its supporting components.

Hierarchy:

    Carrier Board
        -> SoM
            -> SiP
                -> SoC

The COME SiP hardware is effectively the same as the SoM used on the
Qualcomm HAMOA EVK, while the carrier board provides the platform-specific
peripherals and connectivity.

Compared to the HAMOA EVK, PCIe controllers 3, 5 and 6 are routed to
expansion slots, while PCIe controller 4 is connected to an ASM1164
SATA controller. The platform does not provide a USB Type-C connector.
The eUSB repeater (TUSB2E111YCGR) is configured through hardware strapping
pins and therefore requires no software control.

The initial device tree includes support for:
- UART
- Regulators
- USB
- PCIe
- Pinctrl
- ADSP, CDSP
- UFS
- Graphics
- Video

Regulators, pinctrl, graphics, video, ADSP and CDSP support are
inherited from the common hamoa-iot-som.dtsi description.

Co-developed-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Signed-off-by: Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Co-developed-by: Ziyue zhang <ziyue.zhang@oss.qualcomm.com>
Signed-off-by: Ziyue zhang <ziyue.zhang@oss.qualcomm.com>
Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
---
 arch/arm64/boot/dts/qcom/Makefile             |   1 +
 .../boot/dts/qcom/hamoa-iot-come-som.dtsi     |  52 ++++++++
 arch/arm64/boot/dts/qcom/hamoa-iot-come.dts   | 116 ++++++++++++++++++
 3 files changed, 169 insertions(+)
 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 e05414290d8e..09847b4ff337 100644
--- a/arch/arm64/boot/dts/qcom/Makefile
+++ b/arch/arm64/boot/dts/qcom/Makefile
@@ -17,6 +17,7 @@ dtb-$(CONFIG_ARCH_QCOM)	+= apq8096-ifc6640.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= eliza-cqs-evk.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-som.dtsi b/arch/arm64/boot/dts/qcom/hamoa-iot-come-som.dtsi
new file mode 100644
index 000000000000..d8d9765be64b
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/hamoa-iot-come-som.dtsi
@@ -0,0 +1,52 @@
+// SPDX-License-Identifier: BSD-3-Clause
+/*
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ */
+
+#include "hamoa-iot-som.dtsi"
+
+/ {
+	vph_pwr: regulator-vph-pwr {
+		compatible = "regulator-fixed";
+
+		regulator-name = "vph_pwr";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+
+		regulator-always-on;
+		regulator-boot-on;
+	};
+};
+
+&ufs_mem_phy {
+	vdda-phy-supply = <&vreg_l3i_0p8>;
+	vdda-pll-supply = <&vreg_l3e_1p2>;
+
+	status = "okay";
+};
+
+&ufs_mem_hc {
+	reset-gpios = <&tlmm 238 GPIO_ACTIVE_LOW>;
+
+	vcc-supply = <&vreg_l17b_2p5>;
+	vcc-max-microamp = <1300000>;
+	vccq-supply = <&vreg_l2i_1p2>;
+	vccq-max-microamp = <1200000>;
+
+	status = "okay";
+};
+
+&usb_1_ss0 {
+	/delete-property/ usb-role-switch;
+	dr_mode = "peripheral";
+};
+
+&usb_1_ss1 {
+	/delete-property/ usb-role-switch;
+	dr_mode = "host";
+};
+
+&usb_1_ss2 {
+	/delete-property/ usb-role-switch;
+	dr_mode = "host";
+};
diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-come.dts b/arch/arm64/boot/dts/qcom/hamoa-iot-come.dts
new file mode 100644
index 000000000000..735a2b4efd97
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/hamoa-iot-come.dts
@@ -0,0 +1,116 @@
+// SPDX-License-Identifier: BSD-3-Clause
+/*
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ */
+
+/dts-v1/;
+
+#include "hamoa-iot-come-som.dtsi"
+
+/ {
+	model = "Qualcomm Technologies, Inc. Hamoa IoT ComE";
+	compatible = "qcom,hamoa-iot-come", "qcom,hamoa-iot-come-som",
+		     "qcom,hamoa-iot-som", "qcom,x1e80100";
+	chassis-type = "embedded";
+
+	aliases {
+		serial0 = &uart21;
+	};
+
+	chosen {
+		stdout-path = "serial0:115200n8";
+	};
+
+};
+
+&pcie3_port0 {
+	reset-gpios = <&tlmm 143 GPIO_ACTIVE_LOW>;
+	wake-gpios = <&tlmm 145 GPIO_ACTIVE_LOW>;
+};
+
+&pcie4_port0 {
+	reset-gpios = <&tlmm 146 GPIO_ACTIVE_LOW>;
+	wake-gpios = <&tlmm 148 GPIO_ACTIVE_LOW>;
+};
+
+&pcie5_port0 {
+	reset-gpios = <&tlmm 149 GPIO_ACTIVE_LOW>;
+	wake-gpios = <&tlmm 151 GPIO_ACTIVE_LOW>;
+};
+
+&pcie6a_port0 {
+	reset-gpios = <&tlmm 152 GPIO_ACTIVE_LOW>;
+	wake-gpios = <&tlmm 154 GPIO_ACTIVE_LOW>;
+};
+
+&thermal_zones {
+	gpuss-0-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-1-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-2-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-3-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-4-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-5-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-6-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+
+	gpuss-7-thermal {
+		trips {
+			trip-point0 {
+				temperature = <105000>;
+			};
+		};
+	};
+};
+
+&uart21 {
+	compatible = "qcom,geni-debug-uart";
+
+	status = "okay";
+};
-- 
2.43.0