All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  venkata.valluru@oss.qualcomm.com,
	Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH v3 0/3] arm64: dts: qcom: Add LVDS display overlays for lemans, monaco and rb3gen2
Date: Wed, 16 Sep 2026 18:47:16 -0500	[thread overview]
Message-ID: <aqsqE2-ocdV_W34q@baldur> (raw)
In-Reply-To: <20260905-lvds-support-v3-0-b40a1b03f63c@oss.qualcomm.com>

On Sat, Sep 05, 2026 at 07:00:14AM +0530, Vishnu Saini wrote:
> This series adds LVDS display support via device tree overlays for three
> Qualcomm platforms: Lemans EVK, Monaco EVK, and QCS6490 RB3 Gen2
> industrial mezzanine.
> 
> All three platforms use the Lontium LT9211C DSI-to-LVDS bridge chip, which
> converts DSI output to dual-channel LVDS for driving 1920x1080 panels.
> The overlays are structured to be applied on top of the existing IFP
> mezzanine overlay.
> 
> This series depends on:
>   [PATCH v8 0/2] This series adds LT9211C bridge driver by extending LT9211
>   https://lore.kernel.org/all/20260904-add-lt9211c-bridge-v8-0-36d66168e176@oss.qualcomm.com/
> 
> which adds lontium,lt9211c compatible support to the lontium-lt9211 driver
> and extends the binding YAML accordingly,
> 
>   [PATCH v4 0/2] This series adds BOE DV215FHM-R01 LVDS panel support
>   https://lore.kernel.org/all/20260903-b4-lvds-panel-doc-v4-0-861738a0d5de@oss.qualcomm.com/
> 
> which documents the boe,dv215fhm-r01 panel and adds the timings used by these
> overlays,

Then get those merge first, so that I don't have to spend time figuring
that out for you.

> and:
> 
>   arm64: defconfig: Enable Lontium LT9211 driver
>   https://lore.kernel.org/all/20260904-for-next-lt9211-defconfig-v1-1-97221f0109d7@oss.qualcomm.com/
> 
> which enables the driver in defconfig.

This is not a dependency for your changes to be merged.

Regards,
Bjorn

> 
> Signed-off-by: Vishnu Saini <vishnu.saini@oss.qualcomm.com>
> ---
> Changes in v3:
> - Removed redundant status = "okay" on nodes that are enabled by
>   default [Konrad]
> - Added a blank line between the last property and the following
>   subnode throughout the port@N blocks [Konrad]
> - Link to v2: https://lore.kernel.org/r/20260813-lvds-support-v2-0-6b11035e8ab0@oss.qualcomm.com
> 
> Changes in v2:
> - Updated overlays to make them compatable with panel-simple-lvds-dual-ports.yaml [Rob (in panel series)]
> - Added Empty lines before the status property  [Dmitry]
> - Link to v0: https://lore.kernel.org/r/20260719-lvds-support-v1-0-1f1aca3213ba@oss.qualcomm.com
> 
> ---
> Vishnu Saini (3):
>       arm64: dts: qcom: lemans-evk: Add LVDS display overlay
>       arm64: dts: qcom: monaco-evk: Add LVDS display overlay
>       arm64: dts: qcom: qcs6490-rb3gen2: Add LVDS display overlay
> 
>  arch/arm64/boot/dts/qcom/Makefile                  |  14 +++
>  .../dts/qcom/lemans-evk-lvds-boe,dv215fhm-r01.dtso | 113 ++++++++++++++++++++
>  .../dts/qcom/monaco-evk-lvds-boe,dv215fhm-r01.dtso | 114 +++++++++++++++++++++
>  ...industrial-mezzanine-lvds-boe,dv215fhm-r01.dtso | 106 +++++++++++++++++++
>  4 files changed, 347 insertions(+)
> ---
> base-commit: ba20122d4c311bd9384f38e7ba1d0c122e21745d
> change-id: 20260708-lvds-support-2d40d60654f1
> prerequisite-message-id: <20260904-add-lt9211c-bridge-v8-0-36d66168e176@oss.qualcomm.com>
> prerequisite-patch-id: dbba64d1ace696df388c5df3d1cb05a0701df194
> prerequisite-patch-id: fac2b93f3e250589dffd7c076d2ef1aa7a2519a1
> prerequisite-message-id: <20260903-b4-lvds-panel-doc-v4-0-861738a0d5de@oss.qualcomm.com>
> prerequisite-patch-id: 1d3e40bbefcb2550afd81c5cced812a1d3b943a2
> prerequisite-patch-id: bd3612ce053552e2ae7401a1217c4884413563f4
> prerequisite-message-id: <20260904-for-next-lt9211-defconfig-v1-1-97221f0109d7@oss.qualcomm.com>
> prerequisite-patch-id: 9e3233401819ca53c119e6cfab95b0c471ef254e
> 
> Best regards,
> -- 
> Vishnu Saini <vishnu.saini@oss.qualcomm.com>
> 

  parent reply	other threads:[~2026-09-16 23:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05  1:30 [PATCH v3 0/3] arm64: dts: qcom: Add LVDS display overlays for lemans, monaco and rb3gen2 Vishnu Saini
2026-09-05  1:30 ` [PATCH v3 1/3] arm64: dts: qcom: lemans-evk: Add LVDS display overlay Vishnu Saini
2026-09-05  1:38   ` sashiko-bot
2026-09-07 11:40   ` Konrad Dybcio
2026-09-08 16:33     ` Vishnu Saini
2026-09-09 11:23       ` Konrad Dybcio
2026-09-05  1:30 ` [PATCH v3 2/3] arm64: dts: qcom: monaco-evk: " Vishnu Saini
2026-09-05  1:39   ` sashiko-bot
2026-09-05  1:30 ` [PATCH v3 3/3] arm64: dts: qcom: qcs6490-rb3gen2: " Vishnu Saini
2026-09-05  1:41   ` sashiko-bot
2026-09-16 23:47 ` Bjorn Andersson [this message]
2026-09-17 14:19   ` [PATCH v3 0/3] arm64: dts: qcom: Add LVDS display overlays for lemans, monaco and rb3gen2 Vishnu Saini

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=aqsqE2-ocdV_W34q@baldur \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jesszhan0024@gmail.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 \
    --cc=venkata.valluru@oss.qualcomm.com \
    --cc=vishnu.saini@oss.qualcomm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.