From: Sudarshan Shetty <tessolveupstream@gmail.com>
To: 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,
Sudarshan Shetty <tessolveupstream@gmail.com>
Subject: [PATCH v1 0/1] arm64: dts: qcom: Add dual-channel LVDS support on QCS615 Talos EVK
Date: Tue, 28 Oct 2025 11:46:35 +0530 [thread overview]
Message-ID: <20251028061636.724667-1-tessolveupstream@gmail.com> (raw)
Hi all,
This patch introduces a new device tree for the QCS615 Talos EVK platform
with dual-channel LVDS display support.
The new DTS file (`talos-evk-lvds.dts`) is based on the existing
`talos-evk.dts` and extends it to enable a dual-channel LVDS display
configuration using the TI SN65DSI84 DSI-to-LVDS bridge.
In this setup:
- LVDS Channel A carries odd pixels.
- LVDS Channel B carries even pixels.
This patch only adds the new DTS and corresponding Makefile entry.
Thanks,
Sudarshan
---
Sudarshan Shetty (1):
arm64: dts: qcom: talos-evk: Add support for dual-channel LVDS panel
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/talos-evk-lvds.dts | 128 ++++++++++++++++++++
2 files changed, 129 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/talos-evk-lvds.dts
--
2.34.1
next reply other threads:[~2025-10-28 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 6:16 Sudarshan Shetty [this message]
2025-10-28 6:16 ` [PATCH v1 1/1] arm64: dts: qcom: talos-evk: Add support for dual-channel LVDS panel Sudarshan Shetty
2025-10-28 9:25 ` Konrad Dybcio
2025-10-29 12:20 ` Tessolve Upstream
2025-10-29 12:34 ` Dmitry Baryshkov
2025-10-29 15:48 ` Bjorn Andersson
2025-10-29 15:43 ` [PATCH v1 0/1] arm64: dts: qcom: Add dual-channel LVDS support on QCS615 Talos EVK Bjorn Andersson
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=20251028061636.724667-1-tessolveupstream@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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).