From: <mythripk@ti.com>
To: linux-omap@vger.kernel.org
Cc: tomi.valkeinen@ti.com, Mythri P K <mythripk@ti.com>
Subject: [PATCH 0/3] OMAPDSS: HDMI: Interrupt and PHY state handling support
Date: Tue, 20 Mar 2012 18:45:04 +0530 [thread overview]
Message-ID: <1332249307-26875-1-git-send-email-mythripk@ti.com> (raw)
From: Mythri P K <mythripk@ti.com>
Add support for handling the DSS_HDMI interrupt in HDMI, A line that serves to
notify HDMI of status change in PHY, PLL and CORE based on the registration.
Also logic to support enabling of the PHY in TX_ON state only when a PHY_CONNECT
which would make sure that TMDS lines are high before putting it in TX_ON state.
Mythri P K (3):
OMAPDSS: HDMI: support for interrupt enabling
OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt
OMAPDSS: HDMI: wait for TMDS to be high before putting phy in TX_ON
drivers/video/omap2/dss/dss_features.c | 1 +
drivers/video/omap2/dss/hdmi.c | 21 +++++
drivers/video/omap2/dss/ti_hdmi.h | 20 +++++
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c | 117 +++++++++++++++++++++++++++-
drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h | 3 +
5 files changed, 157 insertions(+), 5 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-03-20 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 13:15 mythripk [this message]
2012-03-20 13:15 ` [PATCH 1/3] OMAPDSS: HDMI: support for interrupt enabling mythripk
2012-03-20 13:15 ` [PATCH 2/3] OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt mythripk
2012-03-20 13:15 ` [PATCH 3/3] OMAPDSS: HDMI: wait for TMDS to be high before putting mythripk
2012-03-27 10:30 ` Tomi Valkeinen
2012-03-27 10:30 ` [PATCH 2/3] OMAPDSS: HDMI: Add support for DSS_HDMI Interrupt Tomi Valkeinen
2012-03-27 10:29 ` [PATCH 1/3] OMAPDSS: HDMI: support for interrupt enabling Tomi Valkeinen
2012-03-27 10:29 ` [PATCH 0/3] OMAPDSS: HDMI: Interrupt and PHY state handling support Tomi Valkeinen
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=1332249307-26875-1-git-send-email-mythripk@ti.com \
--to=mythripk@ti.com \
--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).