public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 6 Nov 2025 14:33:10 +0530	[thread overview]
Message-ID: <9d5de3b8-29d0-4202-a361-4bcbfa166755@gmail.com> (raw)
In-Reply-To: <7tk2hd5qursarvomuwe7yt574vmjixh23zz3iw6nzpzm6x7jlj@7q2vlik3t2h6>



On 05/11/25 20:23, Dmitry Baryshkov wrote:
> On Wed, Nov 05, 2025 at 06:27:42PM +0530, Tessolve Upstream wrote:
>>
>>
>> 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.
> 
> 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.
> 


  reply	other threads:[~2025-11-06  9:03 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
2025-11-05 14:53     ` Dmitry Baryshkov
2025-11-06  9:03       ` Tessolve Upstream [this message]
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=9d5de3b8-29d0-4202-a361-4bcbfa166755@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