linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dmunsie@cecropia.com (Dennis Munsie)
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 2.6.17-rc6-mm2 1/5] intelfb: RESEND - add vsync interrupt support
Date: Tue, 20 Jun 2006 14:31:38 -0400 (EDT)	[thread overview]
Message-ID: <20060620183138.2763890CE10@xenon> (raw)

From: Eric Hustvedt <ehustvedt@cecropia.com>

[01/05] intelfb: Add 16-bit register access macros

This patch adds macros to read and write two-byte MMIO registers. The interrupt-related registers are all word-sized, rather than long-sized.

Signed-off-by: Eric Hustvedt <ehustvedt@cecropia.com>
---

 drivers/video/intelfb/intelfbhw.h |    3 +++
 1 file changed, 3 insertions(+)

diff -X linux-2.6.17-rc4-cecropia/Documentation/dontdiff -Naurp linux-2.6.17-rc4-cecropia/drivers/video/intelfb/intelfbhw.h linux-2.6.17-rc4-stable/drivers/video/intelfb/intelfbhw.h
--- linux-2.6.17-rc4-cecropia/drivers/video/intelfb/intelfbhw.h	2006-05-26 10:06:30.000000000 -0600
+++ linux-2.6.17-rc4-stable/drivers/video/intelfb/intelfbhw.h	2006-06-07 11:14:18.000000000 -0600
@@ -468,9 +474,12 @@
 
 /* I/O macros */
 #define INREG8(addr)	      readb((u8 __iomem *)(dinfo->mmio_base + (addr)))
+#define INREG16(addr)	      readw((u16 __iomem *)(dinfo->mmio_base + (addr)))
 #define INREG(addr)	      readl((u32 __iomem *)(dinfo->mmio_base + (addr)))
 #define OUTREG8(addr, val)    writeb((val),(u8 __iomem *)(dinfo->mmio_base + \
 							   (addr)))
+#define OUTREG16(addr, val)    writew((val),(u16 __iomem *)(dinfo->mmio_base + \
+							   (addr)))
 #define OUTREG(addr, val)     writel((val),(u32 __iomem *)(dinfo->mmio_base + \
                                      (addr)))

                 reply	other threads:[~2006-06-20 18:47 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=20060620183138.2763890CE10@xenon \
    --to=dmunsie@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).