[PATCH v3 0/4] Initial support for Advantech SOM-DB5830 board

[PATCH v3 0/4] Initial support for Advantech SOM-DB5830 board

[Yuanjie Yang]

Board layout:
+--------------------------------------------------+
|               SoM (Advantech SOM-6820)           |
|                                                  |
|   +------------------------------------------+   |
|   |     SiP (IQ X7181 EVK SiP)               |   |
|   |                                          |   |
|   |   +----------------------------------+   |   |
|   |   |   SoC (X1E80100)                 |   |   |
|   |   +----------------------------------+   |   |
|   |                                          |   |
|   +------------------------------------------+   |
|                                                  |
+------------------------+-------------------------+
                         |
                         |  Plugs into
                         v
+--------------------------------------------------+
|         Carrier Board (Advantech SOM-DB5830)     |
+--------------------------------------------------+

Introduce the device tree, DT bindings for Advantech SOM-DB5830 board.
And fix HAMOA/PURWA IOT EVK compatibles.

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 v3
- add patch to fix HAMOA/PURWA IOT EVK SOM compatibles
- update Advantech SOM-DB5830 binding and dts
- rebase on next-20260804
- Link to v2: https://lore.kernel.org/all/20260727070758.528-1-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 (4):
      dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles
      arm64: dts: qcom: fix PURWA/HAMOA IOT SOM compatibles
      dt-bindings: arm: qcom: Add Advantech SOM-DB5830
      arm64: dts: qcom: Add Advantech SOM-DB5830

 Documentation/devicetree/bindings/arm/qcom.yaml    |  11 +-
 arch/arm64/boot/dts/qcom/Makefile                  |   1 +
 arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts         |   4 +-
 arch/arm64/boot/dts/qcom/hamoa-som-6820.dtsi       |  54 ++++++++++
 arch/arm64/boot/dts/qcom/hamoa-som-db5830.dts      | 119 +++++++++++++++++++++
 .../{purwa-iot-som.dtsi => iq-x5121-evk-som.dtsi}  |   0
 .../{hamoa-iot-som.dtsi => iq-x7181-evk-som.dtsi}  |   0
 arch/arm64/boot/dts/qcom/purwa-iot-evk.dts         |   4 +-
 8 files changed, 187 insertions(+), 6 deletions(-)
---
base-commit: 0f6da28aab51b16762ed82e8fdeaa5042da45b08
change-id: 20260805-hamoa-come-v3-555d3f56cadc

Best regards,
--  
Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>

[PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

[Yuanjie Yang]

The compatible strings for the Hamoa and Purwa IoT SOM platforms do not
match the naming used in the official hardware documentation.

The documentation identifies these SOMs using their IQ product names
rather than hamoa-iot-som or purwa-iot-som style names. In particular,
there are no SOM products documented with the names:

  - hamoa-iot-som
  - purwa-iot-som

Update the compatible strings to use the correct SOM names as described
in the hardware documentation:

  - hamoa-iot-som -> iq-x7181-evk-som
  - purwa-iot-som -> iq-x5121-evk-som

This aligns the DT compatible strings with the official product naming
and documentation.

Fixes: 06a4db5d8d0e ("dt-bindings: arm: qcom: Document PURWA-IOT-EVK board")
Fixes: 458bb855f274 ("dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board")
Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/arm/qcom.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index ff8a35df7862..f244f547d511 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1220,7 +1220,7 @@ properties:
       - items:
           - enum:
               - qcom,hamoa-iot-evk
-          - const: qcom,hamoa-iot-som
+          - const: qcom,iq-x7181-evk-som
           - const: qcom,x1e80100
 
       - items:
@@ -1235,7 +1235,7 @@ properties:
       - items:
           - enum:
               - qcom,purwa-iot-evk
-          - const: qcom,purwa-iot-som
+          - const: qcom,iq-x5121-evk-som
           - const: qcom,x1p42100
 
       - items:

-- 
2.43.0

Re: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Renaming device tree compatible strings in the YAML schema without updating the corresponding device tree (.dts) files breaks schema validation and ABI.
--

--- Patch [1]: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles ---
commit 86746ff462577b3f827d2ec7f0eb293389e741dc
Author: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>

dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

This commit updates the compatible strings for the Hamoa and Purwa IoT
SOM platforms in the device tree bindings. It renames hamoa-iot-som to
iq-x7181-evk-som and purwa-iot-som to iq-x5121-evk-som to match the
official hardware documentation.

> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862d..f244f547d5114 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -1220,7 +1220,7 @@ properties:
>        - items:
>            - enum:
>                - qcom,hamoa-iot-evk
> -          - const: qcom,hamoa-iot-som
> +          - const: qcom,iq-x7181-evk-som

[Severity: Critical]
Does replacing this compatible string break device tree schema validation for
existing boards?

Since the corresponding device tree files still use the old compatible
string, running make dtbs_check will report that qcom,hamoa-iot-som is
undefined. For example, in arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts:

	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";

Also, does removing a deployed compatible string without retaining backwards
compatibility break the device tree ABI for existing bootloaders?

>            - const: qcom,x1e80100
>  
>        - items:

[ ... ]

> @@ -1235,7 +1235,7 @@ properties:
>        - items:
>            - enum:
>                - qcom,purwa-iot-evk
> -          - const: qcom,purwa-iot-som
> +          - const: qcom,iq-x5121-evk-som

[Severity: Critical]
Will replacing this compatible string also break schema validation for the
Purwa IoT EVK board?

Similar to the Hamoa board, arch/arm64/boot/dts/qcom/purwa-iot-evk.dts still
uses the old string:

	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";

>            - const: qcom,x1p42100

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-hamoa-come-v3-v3-0-20463c43eae1@oss.qualcomm.com?part=1

Re: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

[yuanjiey]

On Wed, Aug 05, 2026 at 10:38:49AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Critical] Renaming device tree compatible strings in the YAML schema without updating the corresponding device tree (.dts) files breaks schema validation and ABI.
> --
> 
> --- Patch [1]: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles ---
> commit 86746ff462577b3f827d2ec7f0eb293389e741dc
> Author: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
> 
> dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles
> 
> This commit updates the compatible strings for the Hamoa and Purwa IoT
> SOM platforms in the device tree bindings. It renames hamoa-iot-som to
> iq-x7181-evk-som and purwa-iot-som to iq-x5121-evk-som to match the
> official hardware documentation.
> 
> > diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> > index ff8a35df7862d..f244f547d5114 100644
> > --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> > +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> > @@ -1220,7 +1220,7 @@ properties:
> >        - items:
> >            - enum:
> >                - qcom,hamoa-iot-evk
> > -          - const: qcom,hamoa-iot-som
> > +          - const: qcom,iq-x7181-evk-som
> 
> [Severity: Critical]
> Does replacing this compatible string break device tree schema validation for
> existing boards?
> 
> Since the corresponding device tree files still use the old compatible
> string, running make dtbs_check will report that qcom,hamoa-iot-som is
> undefined. For example, in arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts:
> 
> 	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";
> 
> Also, does removing a deployed compatible string without retaining backwards
> compatibility break the device tree ABI for existing bootloaders?
> 
> >            - const: qcom,x1e80100
> >  
> >        - items:
> 
> [ ... ]
> 
> > @@ -1235,7 +1235,7 @@ properties:
> >        - items:
> >            - enum:
> >                - qcom,purwa-iot-evk
> > -          - const: qcom,purwa-iot-som
> > +          - const: qcom,iq-x5121-evk-som
> 
> [Severity: Critical]
> Will replacing this compatible string also break schema validation for the
> Purwa IoT EVK board?
> 
> Similar to the Hamoa board, arch/arm64/boot/dts/qcom/purwa-iot-evk.dts still
> uses the old string:
> 
> 	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";
> 
> >            - const: qcom,x1p42100

Patch 1 fix binding qcom.yaml compatible , and Patch 2 fix dts
compatible. So the issue does not occur when Patch 1 and Patch 2
are merged together.

Thanks,
Yuanjie

> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260805-hamoa-come-v3-v3-0-20463c43eae1@oss.qualcomm.com?part=1

Re: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

[Krzysztof Kozlowski]

On Wed, Aug 05, 2026 at 06:30:00PM +0800, Yuanjie Yang wrote:
> The compatible strings for the Hamoa and Purwa IoT SOM platforms do not
> match the naming used in the official hardware documentation.
> 
> The documentation identifies these SOMs using their IQ product names
> rather than hamoa-iot-som or purwa-iot-som style names. In particular,
> there are no SOM products documented with the names:
> 
>   - hamoa-iot-som
>   - purwa-iot-som
> 
> Update the compatible strings to use the correct SOM names as described
> in the hardware documentation:
> 
>   - hamoa-iot-som -> iq-x7181-evk-som
>   - purwa-iot-som -> iq-x5121-evk-som
> 
> This aligns the DT compatible strings with the official product naming
> and documentation.

These are already released, so marketing reasons are not enough to
change the ABI.

Best regards,
Krzysztof

Re: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

[yuanjiey]

On Thu, Aug 06, 2026 at 10:04:23AM +0200, Krzysztof Kozlowski wrote:
> On Wed, Aug 05, 2026 at 06:30:00PM +0800, Yuanjie Yang wrote:
> > The compatible strings for the Hamoa and Purwa IoT SOM platforms do not
> > match the naming used in the official hardware documentation.
> > 
> > The documentation identifies these SOMs using their IQ product names
> > rather than hamoa-iot-som or purwa-iot-som style names. In particular,
> > there are no SOM products documented with the names:
> > 
> >   - hamoa-iot-som
> >   - purwa-iot-som
> > 
> > Update the compatible strings to use the correct SOM names as described
> > in the hardware documentation:
> > 
> >   - hamoa-iot-som -> iq-x7181-evk-som
> >   - purwa-iot-som -> iq-x5121-evk-som
> > 
> > This aligns the DT compatible strings with the official product naming
> > and documentation.
> 
> These are already released, so marketing reasons are not enough to
> change the ABI.

Ok, will drop patch1 and patch2 in next series.

Thanks,
Yuanjue

> Best regards,
> Krzysztof
> 

[PATCH v3 2/4] arm64: dts: qcom: fix PURWA/HAMOA IOT SOM compatibles

[Yuanjie Yang]

The compatible strings used for the Hamoa and Purwa IoT SOMs do not
match the naming used in the corresponding hardware documentation.

The SOMs are documented using their IQ product names and there are no
products identified as hamoa-iot-som or purwa-iot-som. Update the SOM
compatible strings to use the documented hardware names instead.

This keeps the DTS compatible strings aligned with the official
Qualcomm hardware documentation.

Fixes: c11645afb0e2 ("arm64: dts: qcom: Add base HAMOA-IOT-EVK board")
Fixes: 9ed20e877239 ("arm64: dts: qcom: Add base PURWA-IOT-EVK board")
Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
---
 arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts                            | 4 ++--
 .../arm64/boot/dts/qcom/{purwa-iot-som.dtsi => iq-x5121-evk-som.dtsi} | 0
 .../arm64/boot/dts/qcom/{hamoa-iot-som.dtsi => iq-x7181-evk-som.dtsi} | 0
 arch/arm64/boot/dts/qcom/purwa-iot-evk.dts                            | 4 ++--
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
index 9fa86bb6438e..b807079a5ee2 100644
--- a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
+++ b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
@@ -6,12 +6,12 @@
 /dts-v1/;
 
 #include <dt-bindings/leds/common.h>
-#include "hamoa-iot-som.dtsi"
+#include "iq-x7181-evk-som.dtsi"
 #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
 
 / {
 	model = "Qualcomm Technologies, Inc. Hamoa IoT EVK";
-	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";
+	compatible = "qcom,hamoa-iot-evk", "qcom,iq-x7181-evk-som", "qcom,x1e80100";
 	chassis-type = "embedded";
 
 	aliases {
diff --git a/arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi b/arch/arm64/boot/dts/qcom/iq-x5121-evk-som.dtsi
similarity index 100%
rename from arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi
rename to arch/arm64/boot/dts/qcom/iq-x5121-evk-som.dtsi
diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi b/arch/arm64/boot/dts/qcom/iq-x7181-evk-som.dtsi
similarity index 100%
rename from arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi
rename to arch/arm64/boot/dts/qcom/iq-x7181-evk-som.dtsi
diff --git a/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
index ad503beec1d3..d2963af1d762 100644
--- a/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
+++ b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
@@ -6,12 +6,12 @@
 /dts-v1/;
 
 #include <dt-bindings/leds/common.h>
-#include "purwa-iot-som.dtsi"
+#include "iq-x5121-evk-som.dtsi"
 #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
 
 / {
 	model = "Qualcomm Technologies, Inc. Purwa IoT EVK";
-	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";
+	compatible = "qcom,purwa-iot-evk", "qcom,iq-x5121-evk-som", "qcom,x1p42100";
 	chassis-type = "embedded";
 
 	aliases {

-- 
2.43.0

Re: [PATCH v3 2/4] arm64: dts: qcom: fix PURWA/HAMOA IOT SOM compatibles

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing existing device tree board compatible strings breaks backward compatibility with bootloaders and userspace.
--

--- Patch [2]: [PATCH v3 2/4] arm64: dts: qcom: fix PURWA/HAMOA IOT SOM compatibles ---
commit 13bd2c46e7d398444043412a0d95ccdf1938980f
Author: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>

arm64: dts: qcom: fix PURWA/HAMOA IOT SOM compatibles

This commit updates the compatible strings for Hamoa and Purwa IoT SOMs to
match their official IQ product names. It removes the undocumented
hamoa-iot-som and purwa-iot-som strings from the DTS files.

> diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> index 9fa86bb6438ec..b807079a5ee22 100644
> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
[ ... ]
> @@ -6,12 +6,12 @@
>  /dts-v1/;
>  
>  #include <dt-bindings/leds/common.h>
> -#include "hamoa-iot-som.dtsi"
> +#include "iq-x7181-evk-som.dtsi"
>  #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
>  
>  / {
>  	model = "Qualcomm Technologies, Inc. Hamoa IoT EVK";
> -	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";
> +	compatible = "qcom,hamoa-iot-evk", "qcom,iq-x7181-evk-som", "qcom,x1e80100";

[Severity: High]
Does removing the qcom,hamoa-iot-som compatible string break backward
compatibility for existing bootloaders or userspace tools?

Since device tree bindings are generally considered a stable ABI once
released, older bootloaders and userspace scripts (like fwupd or systemd)
identifying the board via qcom,hamoa-iot-som might fail to recognize the
hardware after this update.

Should the new IQ product string be added while keeping the old string
as a fallback?

>  	chassis-type = "embedded";
>  
>  	aliases {

[ ... ]

> diff --git a/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
> index ad503beec1d3d..d2963af1d762d 100644
> --- a/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/purwa-iot-evk.dts
[ ... ]
> @@ -6,12 +6,12 @@
>  /dts-v1/;
>  
>  #include <dt-bindings/leds/common.h>
> -#include "purwa-iot-som.dtsi"
> +#include "iq-x5121-evk-som.dtsi"
>  #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
>  
>  / {
>  	model = "Qualcomm Technologies, Inc. Purwa IoT EVK";
> -	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";
> +	compatible = "qcom,purwa-iot-evk", "qcom,iq-x5121-evk-som", "qcom,x1p42100";

[Severity: High]
Similarly, does the complete removal of qcom,purwa-iot-som here violate
the stable device tree ABI policy?

Bootloaders and userspace tools relying on the previous string will no longer
recognize the board.

>  	chassis-type = "embedded";
>  
>  	aliases {

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-hamoa-come-v3-v3-0-20463c43eae1@oss.qualcomm.com?part=2

[PATCH v3 3/4] dt-bindings: arm: qcom: Add Advantech SOM-DB5830

[Yuanjie Yang]

Document the device tree binding for the Advantech SOM-DB5830 board based
on the Qualcomm X1E80100 SoC.

The platform consists of an Advantech SOM-6820 system-on-module (SoM)
mounted on an Advantech SOM-DB5830 carrier board. The SOM integrates an
IQ X7181 EVK SiP containing the Qualcomm X1E80100 SoC and its supporting
components.

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 f244f547d511..e207feb987df 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1223,6 +1223,13 @@ properties:
           - const: qcom,iq-x7181-evk-som
           - const: qcom,x1e80100
 
+      - items:
+          - enum:
+              - advantech,som-db5830
+          - const: advantech,som-6820
+          - const: qcom,iq-x7181-evk-som
+          - const: qcom,x1e80100
+
       - items:
           - const: microsoft,denali-oled
           - const: microsoft,denali

-- 
2.43.0

Re: [PATCH v3 3/4] dt-bindings: arm: qcom: Add Advantech SOM-DB5830

[Krzysztof Kozlowski]

On Wed, Aug 05, 2026 at 06:30:02PM +0800, Yuanjie Yang wrote:
> Document the device tree binding for the Advantech SOM-DB5830 board based
> on the Qualcomm X1E80100 SoC.
> 
> The platform consists of an Advantech SOM-6820 system-on-module (SoM)
> mounted on an Advantech SOM-DB5830 carrier board. The SOM integrates an
> IQ X7181 EVK SiP containing the Qualcomm X1E80100 SoC and its supporting
> components.
> 
> Signed-off-by: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/arm/qcom.yaml | 7 +++++++
>  1 file changed, 7 insertions(+)

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

[PATCH v3 4/4] arm64: dts: qcom: Add Advantech SOM-DB5830

[Yuanjie Yang]

Add the initial device tree for the Advantech SOM-DB5830 platform based on
the Qualcomm X1E80100 SoC.

The platform consists of an Advantech SOM-6820 system-on-module (SoM)
mounted on an Advantech SOM-DB5830 carrier board. The SOM integrates an
IQ X7181 EVK SiP containing the Qualcomm X1E80100 SoC and its supporting
components.

Compared to the HAMOA IOT 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 iq-x7181-evk-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 +
 arch/arm64/boot/dts/qcom/hamoa-som-6820.dtsi  |  54 ++++++++++++
 arch/arm64/boot/dts/qcom/hamoa-som-db5830.dts | 119 ++++++++++++++++++++++++++
 3 files changed, 174 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
index 1c86e7e98f55..0b5909115c22 100644
--- a/arch/arm64/boot/dts/qcom/Makefile
+++ b/arch/arm64/boot/dts/qcom/Makefile
@@ -24,6 +24,7 @@ hamoa-iot-evk-el2-dtbs	:= hamoa-iot-evk.dtb x1-el2.dtbo
 
 dtb-$(CONFIG_ARCH_QCOM)	+= hamoa-iot-evk-el2.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= hamoa-lenovo-ideacentre-mini-01q8x10.dtb
+dtb-$(CONFIG_ARCH_QCOM)	+= hamoa-som-db5830.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= ipq5018-rdp432-c2.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= ipq5018-tplink-archer-ax55-v1.dtb
 dtb-$(CONFIG_ARCH_QCOM)	+= ipq5210-rdp504.dtb
diff --git a/arch/arm64/boot/dts/qcom/hamoa-som-6820.dtsi b/arch/arm64/boot/dts/qcom/hamoa-som-6820.dtsi
new file mode 100644
index 000000000000..cc7609c33057
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/hamoa-som-6820.dtsi
@@ -0,0 +1,54 @@
+// SPDX-License-Identifier: BSD-3-Clause
+/*
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ *
+ * SoM: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
+ */
+
+#include "iq-x7181-evk-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-som-db5830.dts b/arch/arm64/boot/dts/qcom/hamoa-som-db5830.dts
new file mode 100644
index 000000000000..1697e908fc39
--- /dev/null
+++ b/arch/arm64/boot/dts/qcom/hamoa-som-db5830.dts
@@ -0,0 +1,119 @@
+// SPDX-License-Identifier: BSD-3-Clause
+/*
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ *
+ * SoM: https://advdownload.advantech.com.cn/productfile/PIS/SOM-6820/file/SOM-6820_DS(052925)20250529110758.pdf
+ * carrier board: https://www.advantech.com.cn/zh-cn/products/1-fc23ff/som-db5830/mod_16b1a718-27d6-4a4c-8684-e8f2a8e9c57b
+ */
+
+/dts-v1/;
+
+#include "hamoa-som-6820.dtsi"
+
+/ {
+	model = "Advantech SOM-6820 on SOM-DB5830";
+	compatible = "advantech,som-db5830", "advantech,som-6820",
+		     "qcom,iq-x7181-evk-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

Re: [PATCH v3 4/4] arm64: dts: qcom: Add Advantech SOM-DB5830

[Abel Vesa]

On 26-08-05 18:30:03, Yuanjie Yang wrote:
> Add the initial device tree for the Advantech SOM-DB5830 platform based on
> the Qualcomm X1E80100 SoC.
> 
> The platform consists of an Advantech SOM-6820 system-on-module (SoM)
> mounted on an Advantech SOM-DB5830 carrier board. The SOM integrates an
> IQ X7181 EVK SiP containing the Qualcomm X1E80100 SoC and its supporting
> components.
> 
> Compared to the HAMOA IOT 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 iq-x7181-evk-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>

Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>