From: Lucas Stach <l.stach@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 03/10] video: tc358767: depend on EDID helpers
Date: Fri, 30 Sep 2016 12:36:00 +0200 [thread overview]
Message-ID: <20160930103607.15791-3-l.stach@pengutronix.de> (raw)
In-Reply-To: <20160930103607.15791-1-l.stach@pengutronix.de>
The eDP part need to be able to read the panel EDID.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
drivers/video/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
index 2457bb9e45f9..8f31f5af745e 100644
--- a/drivers/video/Kconfig
+++ b/drivers/video/Kconfig
@@ -130,6 +130,7 @@ config DRIVER_VIDEO_MTL017
config DRIVER_VIDEO_TC358767
bool "TC358767A Display Port encoder"
select VIDEO_VPL
+ depends on DRIVER_VIDEO_EDID
depends on I2C
depends on OFTREE
help
--
2.9.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-09-30 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 10:35 [PATCH 01/10] serial: arm_dcc: depend on !CPU_V8 Lucas Stach
2016-09-30 10:35 ` [PATCH 02/10] mfd: syscon: drop EXPORT_SYMBOL for static function Lucas Stach
2016-09-30 10:36 ` Lucas Stach [this message]
2016-09-30 10:36 ` [PATCH 04/10] arm64: select ARM_EXCEPTIONS Lucas Stach
2016-09-30 10:36 ` [PATCH 05/10] arm(64): move HAS_DMA and HAS_MODULES to CPU_32 Lucas Stach
2016-09-30 10:36 ` [PATCH 06/10] arm(64): don't advertise stack_dumping capabilities for ARM64 Lucas Stach
2016-09-30 10:36 ` [PATCH 07/10] arm: semihosting support is not implemented " Lucas Stach
2016-09-30 10:36 ` [PATCH 08/10] arm64: include correct setupc file in ARM64 PBL Lucas Stach
2016-09-30 10:36 ` [PATCH 09/10] arm64: drop unneeded files from Makefile Lucas Stach
2016-09-30 10:36 ` [PATCH 10/10] arm64: don't allow to build relocatable image Lucas Stach
2016-10-04 6:13 ` [PATCH 01/10] serial: arm_dcc: depend on !CPU_V8 Sascha Hauer
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=20160930103607.15791-3-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.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