Add QCS_HAMOA_10CORE support in qcom-metadata.dts

[xinlon-z]

Is your feature request related to a problem? Please describe.
Currently we have two different Hamoa IOT chip: QCS_HAMOA and QCS_HAMOA_10CORE, but in qcom-metadata.dts only defined QCS_HAMOA, can we add QCS_HAMOA_10CORE into qcom-metadata.dts also?

QCS_HAMOA_10CORE Boot log:

[I2CClientLib] I2C client device tree structure is uninitialized. Exit status=Not Ready
[I2CTrackPad] I2CClientIsDeviceEnabled() failed with Not Ready
BDS Entry      [ 5020]
WaitParallelThreads InIt [ 5053]
EnvDxe locate display utils protocol failed with status: Not Found
Var Store          : WARNING, not persistent
UEFI Ver           : 6.0.260210.BOOT.MXF_UEFI.2.5-00591-HAMOA-1
Platform           : EVK
Subtype            : 0
Boot Device        : SPINOR-UFS
Chip Name          : QCS_HAMOA_10CORE
Chip Ver           : 2.1
Chip Num           : 0x26E664CC
Chip ECID          : 0x044626E664CC
SKU ID             : 0x1
P_Code             : 0x1
Boot Core          : 3 MHz
-----------------------------
...
 ProcessQcomMetaDtbBoardMemorySizeNode: Node 4GB+ From fdt DdrSizeId = 0
 ProcessQcomMetaDtbSoftSkuNode: Board Param: Board SoftSkuId = 0
 ProcessQcomMetaDtbSoftSkuNode: Node softsku0 SoftSkuId = 0
 ParseFitDt: Configuration From BoardParam
qcom, evk, subtype0, emmc, 4GB+, softsku0,
 FindConfigToBoot: SubNode 1360 And Node Name conf-1 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcm6490-idp"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1440 And Node Name conf-2 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs6490-iot"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1524 And Node Name conf-3 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs6490-iot-subtype2"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1636 And Node Name conf-4 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs6490-iot-subtype9"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1752 And Node Name conf-5 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9075-iot"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1832 And Node Name conf-6 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9075v2-iot"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1912 And Node Name conf-7 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9100-qam"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 1996 And Node Name conf-8 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9100v2-qam"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2080 And Node Name conf-9 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9100-qamr2"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2164 And Node Name conf-10 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs9100v2-qamr2"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2252 And Node Name conf-11 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs8300-adp"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2336 And Node Name conf-12 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs8275-iot"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2416 And Node Name conf-13 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs615-adp"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2492 And Node Name conf-14 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs615v1.1-adp"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2572 And Node Name conf-15 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,sa8775p-qam"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2656 And Node Name conf-16 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,sa8775pv2-qam"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2740 And Node Name conf-17 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,sa8775p-qamr2"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2824 And Node Name conf-18 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,sa8775pv2-qamr2"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2912 And Node Name conf-19 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,hamoa-evk"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 FindConfigToBoot: SubNode 2992 And Node Name conf-20 Len = 7
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,hamoav2.1-evk"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 ParseFitDt: Cannot find correct config to boot, Falling to default config
 ParseFitDt:Loading default FIT Config
LoadDtbOnReadyToBoot OS DTB Matching failed with Status = 1
DtPlatformLoadDtbBlob Checking for secondary-dtb.dtb
DtPlatformLoadDtbBlob secondary-dtb.dtb load failed with status = E
DtPlatformLoadDtbBlob Checking for default-upstream-dtb.dtb
DtPlatformLoadDtbBlob default-upstream-dtb.dtb load failed with status = E
LoadDtbOnReadyToBoot: Failing to load fallback dtb)
 CallBack: 0xD64B7568 [ 6552] DtPlatformDxe.dll WARN: ExecTime: 1026 ms
PM: PM_DT_PARSING_ERR: soccp
Reading of OsConfigTableSelection failed,checking DT settings
 UEFI Total : 3467 ms

Describe the solution you'd like
Is it possible to add feature for one chip name map to multiple msm-ids at the same time, for example:

                hamoa {
                      msm-id = <0x000002c5>, <0x000002c6>;
                };
 

[NainaMehtaQUIC]

If both the chip variants require distinct DTB(O)s, separate compatible strings would be required with msm-id being the differentiator in case there is no other differentiator.