From: dmunsie@cecropia.com (Dennis Munsie)
To: linux-fbdev-devel@lists.sourceforge.net
Cc: ehustvedt@cecropia.com, airlied@skynet.ie
Subject: [PATCH 2.6.17-rc6-mm2 4/8] intelfb: RESEND - add preliminary i2c support
Date: Tue, 20 Jun 2006 14:55:55 -0400 (EDT) [thread overview]
Message-ID: <20060620185555.2CA8390CFB4@xenon> (raw)
From: Dennis Munsie <dmunsie@cecropia.com>
[04/07] intelfb: add intelfb_output_rec struct and the constants for it's
fields.
Signed-off-by: Dennis Munsie <dmunsie@cecropia.com>
---
drivers/video/intelfb/intelfb.h | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff -Naurp -X linux-2.6.17-rc6-patched/Documentation/dontdiff linux-2.6.17-rc6-patched/drivers/video/intelfb/intelfb.h linux/drivers/video/intelfb/intelfb.h
--- linux-2.6.17-rc6-patched/drivers/video/intelfb/intelfb.h 2006-06-14 11:13:02.000000000 -0500
+++ linux/drivers/video/intelfb/intelfb.h 2006-06-14 11:14:03.000000000 -0500
@@ -119,6 +119,24 @@
/* Intel agpgart driver */
#define AGP_PHYSICAL_MEMORY 2
+/* these are outputs from the chip - integrated only
+ external chips are via DVO or SDVO output */
+#define INTELFB_OUTPUT_UNUSED 0
+#define INTELFB_OUTPUT_ANALOG 1
+#define INTELFB_OUTPUT_DVO 2
+#define INTELFB_OUTPUT_SDVO 3
+#define INTELFB_OUTPUT_LVDS 4
+#define INTELFB_OUTPUT_TVOUT 5
+
+#define INTELFB_DVO_CHIP_NONE 0
+#define INTELFB_DVO_CHIP_LVDS 1
+#define INTELFB_DVO_CHIP_TMDS 2
+#define INTELFB_DVO_CHIP_TVOUT 4
+
+#define INTELFB_OUTPUT_PIPE_NC 0
+#define INTELFB_OUTPUT_PIPE_A 1
+#define INTELFB_OUTPUT_PIPE_B 2
+
/*** Data Types ***/
/* supported chipsets */
@@ -221,6 +239,17 @@ struct intelfb_i2c_chan {
};
#endif
+struct intelfb_output_rec {
+ int type;
+ int pipe;
+ int flags;
+
+#ifdef CONFIG_FB_INTEL_I2C
+ struct intelfb_i2c_chan i2c_bus;
+ struct intelfb_i2c_chan ddc_bus;
+#endif
+};
+
struct intelfb_vsync {
wait_queue_head_t wait;
unsigned int count;
reply other threads:[~2006-06-20 18:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060620185555.2CA8390CFB4@xenon \
--to=dmunsie@cecropia.com \
--cc=airlied@skynet.ie \
--cc=ehustvedt@cecropia.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).