linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	frieder.schrempf@kontron.de, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v2 2/2] arm64: defconfig: Enable the TI SN65DSI83 driver
Date: Tue, 30 May 2023 10:11:13 -0300	[thread overview]
Message-ID: <20230530131113.1024426-2-festevam@gmail.com> (raw)
In-Reply-To: <20230530131113.1024426-1-festevam@gmail.com>

From: Fabio Estevam <festevam@denx.de>

There are some imx8mm-based boards that contain an SN65DSI83 MIPI
DSI to LVDS bridge chip.

Add support for it so that the LVDS output can be functional by default.

Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v1:
- Fixed the commit log HDMI-->LVDS (Frieder).

 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 53fb665078db..479556b3d6be 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -819,6 +819,7 @@ CONFIG_DRM_SII902X=m
 CONFIG_DRM_SIMPLE_BRIDGE=m
 CONFIG_DRM_THINE_THC63LVD1024=m
 CONFIG_DRM_TI_TFP410=m
+CONFIG_DRM_TI_SN65DSI83=m
 CONFIG_DRM_TI_SN65DSI86=m
 CONFIG_DRM_ANALOGIX_ANX7625=m
 CONFIG_DRM_I2C_ADV7511=m
-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-05-30 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 13:11 [PATCH v2 1/2] arm64: dts: imx8mm-evk: Add HDMI support Fabio Estevam
2023-05-30 13:11 ` Fabio Estevam [this message]
2023-05-30 14:55   ` [PATCH v2 2/2] arm64: defconfig: Enable the TI SN65DSI83 driver Frieder Schrempf
2023-06-04 13:15 ` [PATCH v2 1/2] arm64: dts: imx8mm-evk: Add HDMI support Shawn Guo

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=20230530131113.1024426-2-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=festevam@denx.de \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=shawnguo@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).