Add Qualcomm Technologies, Inc. Talos EVK SMARC support

Introduce the device tree support for the QCS615-based talos-evk platform, which follows the SMARC (Smart Mobility ARChitecture) standard. The platform is composed of two main hardware
components: the talos-evk-som and the talos-evk carrier board.

arch/arm64/boot/dts/qcom/talos-evk.dts new file +13 -0

+					remote-endpoint = <&mdss_dsi0_out>;
+				};
+			};
+
+			port@1 {
+				reg = <1>;
+				adv7535_out: endpoint {
+					remote-endpoint = <&hdmi_con_out>;
+				};
+			};
+		};
+	};
+};

Quoted 4 lines · Sudarshan Shetty

Introduce the device tree support for the QCS615-based talos-evk platform, which follows the SMARC (Smart Mobility ARChitecture) standard. The platform is composed of two main hardware
components: the talos-evk-som and the talos-evk carrier board.

How is the carrier board a separate entity from the "talos-evk.dts"?

[...]

arch/arm64/boot/dts/qcom/talos-evk-som.dtsi line 255

Quoted 4 lines

+&mdss_dp_phy {

arch/arm64/boot/dts/qcom/talos-evk-som.dtsi new file +3 -0

+	vdda-phy-supply = <&vreg_l11a>;
+	vdda-pll-supply = <&vreg_l5a>;
+	status = "okay";

Please apply a consistent \n before status

[...]

arch/arm64/boot/dts/qcom/talos-evk.dts line 74

Quoted 7 lines

arch/arm64/boot/dts/qcom/talos-evk.dts new file +7 -0

+		ports {
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			port@0 {
+				reg = <0>;
+				adv7535_in: endpoint {

and between the last property and the following subnode

Konrad

Quoted 13 lines

arch/arm64/boot/dts/qcom/talos-evk.dts new file +13 -0

+					remote-endpoint = <&mdss_dsi0_out>;
+				};
+			};
+
+			port@1 {
+				reg = <1>;
+				adv7535_out: endpoint {
+					remote-endpoint = <&hdmi_con_out>;
+				};
+			};
+		};
+	};
+};

Quoted 7 lines · Konrad Dybcio

Quoted 4 lines · Sudarshan Shetty

Introduce the device tree support for the QCS615-based talos-evk platform, which follows the SMARC (Smart Mobility ARChitecture) standard. The platform is composed of two main hardware
components: the talos-evk-som and the talos-evk carrier board.

How is the carrier board a separate entity from the "talos-evk.dts"?

The talos-evk platform follows a modular SoM + carrier design. In our current implementation:
talos-evk-som.dtsi — describes SoM-specific components. talos-evk-cb.dtsi — represents the carrier board and includes the SoM file, adding carrier-specific interfaces (micro SD, power button etc.). talos-evk.dts — includes both the SoM and CB DTSIs and enables HDMI display configuration.
talos-evk-lvds.dts — also includes both the SoM and CB DTSIs but enables LVDS instead of HDMI.

HDMI and LVDS share the same DSI output and cannot be used simultaneously. Therefore, we provide separate top-level DTS files (talos-evk.dts for HDMI and talos-evk-lvds.dts for LVDS), while keeping common board logic in talos-evk-cb.dtsi.

Hence, layer looks as below:

talos-evk-som.dtsi

├── talos-evk-cb.dtsi (includes som)
│    ├── talos-evk.dts (HDMI)
│    └── talos-evk-lvds.dts (LVDS)

This ensures modularity, and properly models mutually exclusive display configurations.

Quoted 33 lines · Tessolve Upstream

Quoted 7 lines · Konrad Dybcio

Quoted 4 lines · Sudarshan Shetty

Introduce the device tree support for the QCS615-based talos-evk platform, which follows the SMARC (Smart Mobility ARChitecture) standard. The platform is composed of two main hardware
components: the talos-evk-som and the talos-evk carrier board.

How is the carrier board a separate entity from the "talos-evk.dts"?

The talos-evk platform follows a modular SoM + carrier design. In our current implementation:
talos-evk-som.dtsi — describes SoM-specific components. talos-evk-cb.dtsi — represents the carrier board and includes the SoM file, adding carrier-specific interfaces (micro SD, power button etc.). talos-evk.dts — includes both the SoM and CB DTSIs and enables HDMI display configuration.
talos-evk-lvds.dts — also includes both the SoM and CB DTSIs but enables LVDS instead of HDMI.

HDMI and LVDS share the same DSI output and cannot be used simultaneously. Therefore, we provide separate top-level DTS files (talos-evk.dts for HDMI and talos-evk-lvds.dts for LVDS), while keeping common board logic in talos-evk-cb.dtsi.

Hence, layer looks as below:

talos-evk-som.dtsi

├── talos-evk-cb.dtsi (includes som)
│    ├── talos-evk.dts (HDMI)
│    └── talos-evk-lvds.dts (LVDS)

Quoted 2 lines

This ensures modularity, and properly models mutually exclusive display configurations.

And are both the LVDS display and HDMI converter on separate add-in boards?

Konrad

Hi all,

This patch series adds device tree binding and board support for the Qualcomm Technologies, Inc. Talos EVK SMARC platform based on the QCS615 SoC.

The first patch introduces the DT binding entry for the Talos EVK SMARC board, and the second patch adds the corresponding DTS files for the platform.

Note:
USB(usb_1_dwc3) supports host-only mode based on the switch SW1 on the SoM, which is purely a hardware controlled as USB-ID and USB-VBUS is not connected the switching cannot be handled from SW. Hence from SW Host-only mode is supported on Linux boot up.

Changes in v5:
- Updated commit message. (suggested by Krzysztof)
- Introduced generic node name for can, dp, hdmi-bridge. (suggested by Krzysztof)
- Introduced talos-evk-cb.dtsi, which has common carrier board interfaces.

- No functional change in bindings file.

Changes in v4:
- Updated product name to full form per Krzysztof’s feedback in dt-binding comment.
- Hook up the ADV7535 DSI-to-HDMI bridge to base DTS file.
- Add DP connector node and MDSS DisplayPort controller.
- Added USB note in the cover letter for maintainers' awareness.

Changes in v3:
- Addressed comments from Dmitry regarding USB1 dr_mode and added a DTS comment.
- No functional change in bindings file.

Changes in v2:
- Renamed compatible to "qcom,talos-evk" (suggested by Dmitry/Bjorn)
- Merged enum entry with existing qcs615-ride block (Krzysztof)
- Fixed subject and commit message to use imperative mood.

Thanks,
Sudarshan

Sudarshan Shetty (2):
dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform
arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board

 .../devicetree/bindings/arm/qcom.yaml         |   1 +
 arch/arm64/boot/dts/qcom/Makefile             |   1 +
 arch/arm64/boot/dts/qcom/talos-evk-cb.dtsi    |  56 +++
 arch/arm64/boot/dts/qcom/talos-evk-som.dtsi   | 442 ++++++++++++++++++
 arch/arm64/boot/dts/qcom/talos-evk.dts        |  87 ++++
 5 files changed, 587 insertions(+)
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk-cb.dtsi
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk-som.dtsi
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk.dts

Signature · 1 line

2.34.1

Quoted 16 lines · Sudarshan Shetty

Hi all,

This patch series adds device tree binding and board support for the Qualcomm Technologies, Inc. Talos EVK SMARC platform based on the QCS615 SoC.

The first patch introduces the DT binding entry for the Talos EVK SMARC board, and the second patch adds the corresponding DTS files for the platform.

Note:
USB(usb_1_dwc3) supports host-only mode based on the switch SW1 on the SoM, which is purely a hardware controlled as USB-ID and USB-VBUS is not connected the switching cannot be handled from SW. Hence from SW Host-only mode is supported on Linux boot up.

Quoted 6 lines

Changes in v5:
- Updated commit message. (suggested by Krzysztof)
- Introduced generic node name for can, dp, hdmi-bridge. (suggested by Krzysztof)
- Introduced talos-evk-cb.dtsi, which has common carrier board interfaces.

Common between what?

Quoted 40 lines

- No functional change in bindings file.

Changes in v4:
- Updated product name to full form per Krzysztof’s feedback in dt-binding comment.
- Hook up the ADV7535 DSI-to-HDMI bridge to base DTS file.
- Add DP connector node and MDSS DisplayPort controller.
- Added USB note in the cover letter for maintainers' awareness.

Changes in v3:
- Addressed comments from Dmitry regarding USB1 dr_mode and added a DTS comment.
- No functional change in bindings file.

Changes in v2:
- Renamed compatible to "qcom,talos-evk" (suggested by Dmitry/Bjorn)
- Merged enum entry with existing qcs615-ride block (Krzysztof)
- Fixed subject and commit message to use imperative mood.

Thanks,
Sudarshan

Sudarshan Shetty (2):
dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform
arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board

 .../devicetree/bindings/arm/qcom.yaml         |   1 +
 arch/arm64/boot/dts/qcom/Makefile             |   1 +
 arch/arm64/boot/dts/qcom/talos-evk-cb.dtsi    |  56 +++
 arch/arm64/boot/dts/qcom/talos-evk-som.dtsi   | 442 ++++++++++++++++++
 arch/arm64/boot/dts/qcom/talos-evk.dts        |  87 ++++
 5 files changed, 587 insertions(+)
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk-cb.dtsi
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk-som.dtsi
 create mode 100644 arch/arm64/boot/dts/qcom/talos-evk.dts

Signature · 1 line

2.34.1

Quoted 24 lines · Dmitry Baryshkov

Quoted 22 lines · Sudarshan Shetty

Hi all,

This patch series adds device tree binding and board support for the Qualcomm Technologies, Inc. Talos EVK SMARC platform based on the QCS615 SoC.

The first patch introduces the DT binding entry for the Talos EVK SMARC board, and the second patch adds the corresponding DTS files for the platform.

Note:
USB(usb_1_dwc3) supports host-only mode based on the switch SW1 on the SoM, which is purely a hardware controlled as USB-ID and USB-VBUS is not connected the switching cannot be handled from SW. Hence from SW Host-only mode is supported on Linux boot up.

Changes in v5:
- Updated commit message. (suggested by Krzysztof)
- Introduced generic node name for can, dp, hdmi-bridge. (suggested by Krzysztof)
- Introduced talos-evk-cb.dtsi, which has common carrier board interfaces.

Quoted 1 line

Common between what?

Introduced talos-evk-cb.dtsi to define carrier board–specific interfaces common to both HDMI and LVDS top-level DTS variants.

Quoted 27 lines · Tessolve Upstream

Quoted 24 lines · Dmitry Baryshkov

Quoted 22 lines · Sudarshan Shetty

Hi all,

This patch series adds device tree binding and board support for the Qualcomm Technologies, Inc. Talos EVK SMARC platform based on the QCS615 SoC.

The first patch introduces the DT binding entry for the Talos EVK SMARC board, and the second patch adds the corresponding DTS files for the platform.

Note:
USB(usb_1_dwc3) supports host-only mode based on the switch SW1 on the SoM, which is purely a hardware controlled as USB-ID and USB-VBUS is not connected the switching cannot be handled from SW. Hence from SW Host-only mode is supported on Linux boot up.

Changes in v5:
- Updated commit message. (suggested by Krzysztof)
- Introduced generic node name for can, dp, hdmi-bridge. (suggested by Krzysztof)
- Introduced talos-evk-cb.dtsi, which has common carrier board interfaces.

Quoted 4 lines

Quoted 1 line

Common between what?

Introduced talos-evk-cb.dtsi to define carrier board–specific interfaces common to both HDMI and LVDS top-level DTS variants.

Are those two different carrier boards? Is it a single carrier board with mezzanines? With extension boards? With a DIP switch?

Quoted 28 lines · Dmitry Baryshkov

Quoted 27 lines · Tessolve Upstream

Quoted 24 lines · Dmitry Baryshkov

Quoted 22 lines · Sudarshan Shetty

Hi all,

This patch series adds device tree binding and board support for the Qualcomm Technologies, Inc. Talos EVK SMARC platform based on the QCS615 SoC.

The first patch introduces the DT binding entry for the Talos EVK SMARC board, and the second patch adds the corresponding DTS files for the platform.

Note:
USB(usb_1_dwc3) supports host-only mode based on the switch SW1 on the SoM, which is purely a hardware controlled as USB-ID and USB-VBUS is not connected the switching cannot be handled from SW. Hence from SW Host-only mode is supported on Linux boot up.

Changes in v5:
- Updated commit message. (suggested by Krzysztof)
- Introduced generic node name for can, dp, hdmi-bridge. (suggested by Krzysztof)
- Introduced talos-evk-cb.dtsi, which has common carrier board interfaces.

Quoted 7 lines

Quoted 4 lines

Quoted 1 line

Common between what?

Introduced talos-evk-cb.dtsi to define carrier board–specific interfaces common to both HDMI and LVDS top-level DTS variants.

Are those two different carrier boards? Is it a single carrier board with mezzanines? With extension boards? With a DIP switch?

It’s a single carrier board.
HDMI and LVDS share the same DSI interface, and only one can be active at a time depending on a DIP switch.

Quoted 1 line