From: Archit Taneja <archit@ti.com>
To: tomi.valkeinen@ti.com
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
Archit Taneja <archit@ti.com>
Subject: [PATCH 07/11] omapdss: HDMI: add HDMI wrapper IRQ flags
Date: Tue, 17 Sep 2013 12:36:33 +0530 [thread overview]
Message-ID: <1379401597-27222-8-git-send-email-archit@ti.com> (raw)
In-Reply-To: <1379401597-27222-1-git-send-email-archit@ti.com>
Add flags for the interrupts present in HDMI wrapper block, these will be used
to configure HDMI_IRQENABLE_SET/CLEAR and HDMI_IRQSTATUS registers.
Signed-off-by: Archit Taneja <archit@ti.com>
---
drivers/video/omap2/dss/hdmi_phy.c | 3 ---
drivers/video/omap2/dss/ti_hdmi.h | 15 +++++++++++++++
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/video/omap2/dss/hdmi_phy.c b/drivers/video/omap2/dss/hdmi_phy.c
index b79c56b..b7d171c 100644
--- a/drivers/video/omap2/dss/hdmi_phy.c
+++ b/drivers/video/omap2/dss/hdmi_phy.c
@@ -17,9 +17,6 @@
#include "dss.h"
#include "ti_hdmi.h"
-#define HDMI_IRQ_LINK_CONNECT (1 << 25)
-#define HDMI_IRQ_LINK_DISCONNECT (1 << 26)
-
void hdmi_phy_dump(struct hdmi_phy_data *phy, struct seq_file *s)
{
#define DUMPPHY(r) seq_printf(s, "%-35s %08x\n", #r,\
diff --git a/drivers/video/omap2/dss/ti_hdmi.h b/drivers/video/omap2/dss/ti_hdmi.h
index cf096fd..5034080 100644
--- a/drivers/video/omap2/dss/ti_hdmi.h
+++ b/drivers/video/omap2/dss/ti_hdmi.h
@@ -49,6 +49,21 @@
#define HDMI_WP_AUDIO_CTRL 0x88
#define HDMI_WP_AUDIO_DATA 0x8C
+/* HDMI WP IRQ flags */
+
+#define HDMI_IRQ_OCP_TIMEOUT (1 << 4)
+#define HDMI_IRQ_AUDIO_FIFO_UNDERFLOW (1 << 8)
+#define HDMI_IRQ_AUDIO_FIFO_OVERFLOW (1 << 9)
+#define HDMI_IRQ_AUDIO_FIFO_SAMPLE_REQ (1 << 10)
+#define HDMI_IRQ_VIDEO_VSYNC (1 << 16)
+#define HDMI_IRQ_VIDEO_FRAME_DONE (1 << 17)
+#define HDMI_IRQ_PHY_LINE5V_ASSERT (1 << 24)
+#define HDMI_IRQ_LINK_CONNECT (1 << 25)
+#define HDMI_IRQ_LINK_DISCONNECT (1 << 26)
+#define HDMI_IRQ_PLL_LOCK (1 << 29)
+#define HDMI_IRQ_PLL_UNLOCK (1 << 30)
+#define HDMI_IRQ_PLL_RECAL (1 << 31)
+
/* HDMI PLL */
#define PLLCTRL_PLL_CONTROL 0x0
--
1.8.1.2
next prev parent reply other threads:[~2013-09-17 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:06 [PATCH 00/11] omapdss: HDMI: Refactor driver for easier addition of OMAP5/DRA7 hdmi IP Archit Taneja
2013-09-17 7:06 ` [PATCH 01/11] omapdss: HDMI: create a hdmi wrapper library Archit Taneja
2013-09-17 7:06 ` [PATCH 02/11] omapdss: HDMI: create a HDMI PLL library Archit Taneja
2013-09-17 9:38 ` Mike Turquette
2013-09-17 10:02 ` Tomi Valkeinen
2013-09-17 19:40 ` Mike Turquette
2013-09-18 7:00 ` Tomi Valkeinen
2013-09-17 7:06 ` [PATCH 03/11] omapdss: HDMI: create a PHY library Archit Taneja
2013-09-17 7:06 ` [PATCH 04/11] omapdss: HDMI: Use OMAP4 HDMI core functions directly and remove hdmi_ip_ops Archit Taneja
2013-09-17 7:06 ` [PATCH 05/11] omapdss: HDMI: remove hdmi_ip_data struct Archit Taneja
2013-09-17 7:06 ` [PATCH 06/11] omapdss: HDMI: Clean up the header files Archit Taneja
2013-09-17 7:06 ` Archit Taneja [this message]
2013-09-17 7:06 ` [PATCH 09/11] omapdss: OMAP4: HDMI: remove unnecessary edid macros Archit Taneja
2013-09-17 7:06 ` [PATCH 10/11] omapdss: HDMI: move common functions to a separate file Archit Taneja
2013-09-17 7:06 ` [PATCH 11/11] [experimental] arm: omap: omap4 hwmod data: Split hdmi address space Archit Taneja
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=1379401597-27222-8-git-send-email-archit@ti.com \
--to=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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 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).