From: Tessolve Upstream <tessolveupstream@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board
Date: Wed, 5 Nov 2025 15:31:27 +0530 [thread overview]
Message-ID: <4e3b01fa-174b-4de3-a5ef-67f51f0b2033@gmail.com> (raw)
In-Reply-To: <27f51013-9276-4e41-b57d-fb0baaec5bc6@oss.qualcomm.com>
On 04/11/25 19:57, Konrad Dybcio wrote:
> On 11/4/25 1:51 PM, Sudarshan Shetty wrote:
>> 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.
>
> [...]
>
>> +&mdss_dp_phy {
>> + vdda-phy-supply = <&vreg_l11a>;
>> + vdda-pll-supply = <&vreg_l5a>;
>> + status = "okay";
>
> Please apply a consistent \n before status
okay, will update in v6 patch.
>
> [...]
>
>> + ports {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + port@0 {
>> + reg = <0>;
>> + adv7535_in: endpoint {
>
> and between the last property and the following subnode
>
okay, will update in v6 patch.
> Konrad
>
>> + remote-endpoint = <&mdss_dsi0_out>;
>> + };
>> + };
>> +
>> + port@1 {
>> + reg = <1>;
>> + adv7535_out: endpoint {
>> + remote-endpoint = <&hdmi_con_out>;
>> + };
>> + };
>> + };
>> + };
>> +};
next prev parent reply other threads:[~2025-11-05 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 12:51 [PATCH v5 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-11-04 12:51 ` [PATCH v5 1/2] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-11-04 12:51 ` [PATCH v5 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-11-04 14:27 ` Konrad Dybcio
2025-11-05 10:01 ` Tessolve Upstream [this message]
2025-11-05 11:09 ` Konrad Dybcio
2025-11-05 12:53 ` Tessolve Upstream
2025-11-05 1:05 ` [PATCH v5 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Dmitry Baryshkov
2025-11-05 12:57 ` Tessolve Upstream
2025-11-05 14:53 ` Dmitry Baryshkov
2025-11-06 9:03 ` Tessolve Upstream
2025-11-06 12:17 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e3b01fa-174b-4de3-a5ef-67f51f0b2033@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox