devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 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 v7 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board
Date: Mon, 24 Nov 2025 10:37:36 +0530	[thread overview]
Message-ID: <2e0a7e3e-eb20-449a-84a5-6d4e2f147ef9@gmail.com> (raw)
In-Reply-To: <46k4uvtoit5tty3ojh7da7yliqz27tdcscu2co5tuowy33uicc@v3f3cojpwvzp>



On 21-11-2025 22:16, Dmitry Baryshkov wrote:
> On Thu, Nov 20, 2025 at 01:02:39PM +0530, tessolveupstream@gmail.com wrote:
>>
>>
>> On 19-11-2025 15:55, Dmitry Baryshkov wrote:
>>> On Tue, Nov 18, 2025 at 06:38:14PM +0530, Sudarshan Shetty wrote:
>>>> Add the device tree for the QCS615-based Talos EVK platform. The
>>>> platform is composed of a System-on-Module following the SMARC
>>>> standard, and a Carrier Board.
>>>>
>>>> The Carrier Board supports several display configurations, HDMI and
>>>> LVDS. Both configurations use the same base hardware, with the display
>>>> selection controlled by a DIP switch.
>>>>
>>>> To avoid duplication, use an include file, talos-evk-cb.dtsi, which
>>>> defines the interfaces and peripherals common to both display
>>>> variants. Two additional DTs (e.g. talos-evk and talos-evk-lvds)
>>>> can describe the selected display configuration.
>>>>
>>>> The initial device tree includes support for:
>>>> - CPU and memory
>>>> - UART
>>>> - GPIOs
>>>> - Regulators
>>>> - PMIC
>>>> - Early console
>>>> - AT24MAC602 EEPROM
>>>> - MCP2515 SPI to CAN
>>>> - ADV7535 DSI-to-HDMI bridge
>>>> - DisplayPort interface
>>>
>>> You got the question for v6, responded there but didn't update commit
>>> message. What is not enabled here? E.g. why isn't venus enabled?
>>
>> In earlier patch, we have added 'Wi-Fi/BT and ethernet is not 
>> supported'as a commit message. Later,based on 
>> Krzysztof Kozlowski’s review comments, we removed the same. 
>> Please find the below review comment for your reference.
>> https://lore.kernel.org/all/20251028053248.723560-1-tessolveupstream@gmail.com/T/#mda58996a7abac13780f8ce2cd49b84c32d4c50a6
>>
>> We are not clear whether 'Wi-Fi/BT and ethernet is not supported'
>> should be added back to the commit message or not. 
>> Could you please confirm your preference?
> 
> If you are unsure, you can add this info to the cover letter. Or you can
> write something like 'Ethernet and WiFi/BT are not (yet) supported.'.

Okay, we will add the info 'Ethernet and WiFi/BT are not (yet) 
supported' to the cover letter.
> 
>>
>> Venus is enabled in this patch.
> 
> Ack, excuse me.
> 
>>>
>>>> Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>
>>>> ---
>>>>  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 | 447 ++++++++++++++++++++
>>>>  arch/arm64/boot/dts/qcom/talos-evk.dts      |  94 ++++
>>>>  4 files changed, 598 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
>>>>
>>>
>>
> 


      reply	other threads:[~2025-11-24  5:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 13:08 [PATCH v7 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-11-18 13:08 ` [PATCH v7 1/2] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-11-18 13:08 ` [PATCH v7 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-11-18 15:30   ` Bjorn Andersson
2025-11-19 10:25   ` Dmitry Baryshkov
2025-11-20  7:32     ` tessolveupstream
2025-11-21 16:46       ` Dmitry Baryshkov
2025-11-24  5:07         ` tessolveupstream [this message]

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=2e0a7e3e-eb20-449a-84a5-6d4e2f147ef9@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).