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

[yuanjiey]

On Wed, Jul 01, 2026 at 09:28:41AM +0200, Krzysztof Kozlowski wrote:
> On Tue, Jun 30, 2026 at 03:10:11PM +0800, Yuanjie Yang wrote:
> > Document the device tree binding for the HAMOA-IOT-COME board, which uses
> > the Qualcomm X1E80100 SoC.
> > 
> > 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
> 
> This is contradictory to the code. Your binding said you are using IOT
> SoM, not IoT COME SoM.

Hierarchy:

Hamoa ComE
 Carrier Board
     -> SoM
         -> SiP(This SiP hardware is effectively the same as the SoM on the Hamoa EVK)
             -> SoC

Hamoa evk
 Carrier Board
     -> SoM
         -> SoC


So I think I write a wrong dt binding about Hamoa ComE:
correct here:
I think the binding should be: 

1.
      - items:
          - enum:
              - qcom,hamoa-iot-come
          - const: qcom,hamoa-iot-come-som
          - const: qcom,hamoa-iot-come-sip
          - const: qcom,x1e80100

or
2.
      - items:
          - enum:
              - qcom,hamoa-iot-come
          - const: qcom,hamoa-iot-come-som
          - const: qcom,hamoa-iot-som
          - const: qcom,x1e80100


> > related components.
> > 
> > Hierarchy:
> > 
> >     Carrier Board
> >         -> SoM
> >             -> SiP
> >                 -> SoC
> 
> Drop. Compatibles define that.

Sure , will do.

> > 
> > The SiP on the HAMOA-IOT-COME SoM is equivalent to the HAMOA-IOT-EVK SoM.
> 
> I don't even know what does it mean. How two different hardware can be
> equivalent? Are they the same? Are you creating duplicated compatibles
> for same hardware?

This ComE SiP hardware is effectively the same as the SoM on the Hamoa EVK, 
It's just called differently on a different board. I should update my
commit msg show this.

> Best regards,
> Krzysztof
> 
Thanks,
Yuanjie