From: Archit Taneja <archit@ti.com>
To: tomi.valkeinen@ti.com
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
Archit Taneja <archit@ti.com>
Subject: [PATCH 0/6] omapdss: hdmi: Add support for hdmi on OMAP5 and DRA7x SoCs
Date: Thu, 17 Oct 2013 11:38:36 +0000 [thread overview]
Message-ID: <1382009202-18984-1-git-send-email-archit@ti.com> (raw)
The HDMI IP on OMAP5/DRA7xx has very similar wrapper, PLL and PHY sub blocks
found in OMAP4 DSS. However, the HDMI core IP(which implements the HDMI
protocol) is completely new.
Create a library for configuring the new HDMI core IP, make minor modifications
in PLL and PHY. And finally, add a hdmi5 driver. This driver can eventually be
merged with the hdmi4 driver such that both of them use the same driver, we
would need to create core IP ops for that, we've left that for later.
Archit Taneja (6):
omapdss: hdmi: support larger register offsets for OMAP5 HDMI core
omapdss: hdmi: Add initial OMAP5/DRA7x HDMI core IP library
omapdss: hdmi phy: Incorporate changes for OMAP5/DRA7x
omapdss: hdmi pll: Incorporate changes for OMAP5/DRA7x
omapdss: hdmi: add OMAP5/DRA7x hdmi driver
omapdss: hdmi4/hdmi5: set regulator voltage to required level
drivers/video/omap2/dss/Kconfig | 10 +
drivers/video/omap2/dss/Makefile | 2 +
drivers/video/omap2/dss/core.c | 6 +
drivers/video/omap2/dss/dss.h | 3 +
drivers/video/omap2/dss/hdmi.h | 7 +-
drivers/video/omap2/dss/hdmi4.c | 5 +
drivers/video/omap2/dss/hdmi5.c | 704 ++++++++++++++++++++++++++++++
drivers/video/omap2/dss/hdmi5_core.c | 812 +++++++++++++++++++++++++++++++++++
drivers/video/omap2/dss/hdmi5_core.h | 298 +++++++++++++
drivers/video/omap2/dss/hdmi_phy.c | 94 +++-
drivers/video/omap2/dss/hdmi_pll.c | 74 +++-
drivers/video/omap2/dss/hdmi_wp.c | 2 +-
12 files changed, 2008 insertions(+), 9 deletions(-)
create mode 100644 drivers/video/omap2/dss/hdmi5.c
create mode 100644 drivers/video/omap2/dss/hdmi5_core.c
create mode 100644 drivers/video/omap2/dss/hdmi5_core.h
--
1.8.1.2
next reply other threads:[~2013-10-17 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 11:38 Archit Taneja [this message]
2013-10-17 11:38 ` [PATCH 1/6] omapdss: hdmi: support larger register offsets for OMAP5 HDMI core Archit Taneja
2013-10-17 11:38 ` [PATCH 2/6] omapdss: hdmi: Add initial OMAP5/DRA7x HDMI core IP library Archit Taneja
2013-10-17 11:38 ` [PATCH 3/6] omapdss: hdmi phy: Incorporate changes for OMAP5/DRA7x Archit Taneja
2013-10-17 11:38 ` [PATCH 4/6] omapdss: hdmi pll: " Archit Taneja
2013-10-17 11:38 ` [PATCH 5/6] omapdss: hdmi: add OMAP5/DRA7x hdmi driver Archit Taneja
2013-10-17 11:38 ` [PATCH 6/6] omapdss: hdmi4/hdmi5: set regulator voltage to required level 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=1382009202-18984-1-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).