From: Tessolve Upstream <tessolveupstream@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, 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 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support
Date: Wed, 5 Nov 2025 18:27:42 +0530 [thread overview]
Message-ID: <58afe57b-68e8-4de3-841a-df3dbf04ee64@gmail.com> (raw)
In-Reply-To: <xq4jidiffovpg3armhlzrzxloug4irumlycyyvmfaugajbtq4t@cutuj5736ayo>
On 05/11/25 06:35, Dmitry Baryshkov wrote:
> On Tue, Nov 04, 2025 at 06:21:24PM +0530, Sudarshan Shetty wrote:
>> 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.
>
> Common between what?
Introduced talos-evk-cb.dtsi to define carrier board–specific interfaces
common to both HDMI and LVDS top-level DTS variants.
>
>> - 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
>>
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2025-11-05 12:57 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
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 [this message]
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=58afe57b-68e8-4de3-841a-df3dbf04ee64@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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;
as well as URLs for NNTP newsgroup(s).