linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 00/11] omapdss: HDMI: Refactor driver for easier addition of OMAP5/DRA7 hdmi IP
Date: Tue, 17 Sep 2013 07:18:26 +0000	[thread overview]
Message-ID: <1379401597-27222-1-git-send-email-archit@ti.com> (raw)

The HDMI IP in OMAP4 DSS is present in a few other TI SoCs which don't have a
Display Subsystem similar to what's in OMAP. The original driver was designed
to provide ops such that it could be plugged into a different display subsytem
in some other SoC. These other SoCs, however, never got their baseport code
upstreamed, and the HDMI IP remains exclusive to OMAP DSS.

Refactor the code such that HDMI sub blocks(wrapper, PLL, PHY) are made into
libraries. The HDMI core IP(the encoder) is the only block which varies between
OMAP4 and OMAP5/DRA7 IPs. The rest can be shared by the 2 HDMI drivers.

This will allow more code reuse between the 2 HDMI drivers, and allow easier
addition of the OMAP5/DRA7 HDMI driver. The driver is also simplified now as it
doesn't need to provide ops to different display subsystems.

The new driver needs an address space split according to the HDMI sub blocks.
This requires us to change the OMAP4 hwmod data, or ensure that we add a split
address space when we add support for DSS in DT.

The last patch in the series splits the address space in omap4 hwmod data. If
hwmod changes are disregarded. The driver can temporarily be hacked to contain
the base addresses.

Archit Taneja (11):
  omapdss: HDMI: create a hdmi wrapper library
  omapdss: HDMI: create a HDMI PLL library
  omapdss: HDMI: create a PHY library
  omapdss: HDMI: Use OMAP4 HDMI core functions directly and remove
    hdmi_ip_ops
  omapdss: HDMI: remove hdmi_ip_data struct
  omapdss: HDMI: Clean up the header files
  omapdss: HDMI: add HDMI wrapper IRQ flags
  omapdss: HDMI: Rename hdmi driver files to nicer names
  omapdss: OMAP4: HDMI: remove unnecessary edid macros
  omapdss: HDMI: move common functions to a separate file
  [experimental] arm: omap: omap4 hwmod data: Split hdmi address space

 arch/arm/mach-omap2/omap_hwmod_44xx_data.c |   19 +
 drivers/video/omap2/dss/Makefile           |    3 +-
 drivers/video/omap2/dss/core.c             |    4 +-
 drivers/video/omap2/dss/dss.h              |    4 +-
 drivers/video/omap2/dss/dss_features.c     |   44 -
 drivers/video/omap2/dss/dss_features.h     |    8 -
 drivers/video/omap2/dss/hdmi.c             | 1184 ----------------------
 drivers/video/omap2/dss/hdmi4.c            |  696 +++++++++++++
 drivers/video/omap2/dss/hdmi4_core.c       | 1016 +++++++++++++++++++
 drivers/video/omap2/dss/hdmi4_core.h       |  278 ++++++
 drivers/video/omap2/dss/hdmi_common.c      |  423 ++++++++
 drivers/video/omap2/dss/hdmi_phy.c         |  142 +++
 drivers/video/omap2/dss/hdmi_pll.c         |  212 ++++
 drivers/video/omap2/dss/hdmi_wp.c          |  254 +++++
 drivers/video/omap2/dss/ti_hdmi.h          |  403 ++++++--
 drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c  | 1477 ----------------------------
 drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h  |  488 ---------
 17 files changed, 3377 insertions(+), 3278 deletions(-)
 delete mode 100644 drivers/video/omap2/dss/hdmi.c
 create mode 100644 drivers/video/omap2/dss/hdmi4.c
 create mode 100644 drivers/video/omap2/dss/hdmi4_core.c
 create mode 100644 drivers/video/omap2/dss/hdmi4_core.h
 create mode 100644 drivers/video/omap2/dss/hdmi_common.c
 create mode 100644 drivers/video/omap2/dss/hdmi_phy.c
 create mode 100644 drivers/video/omap2/dss/hdmi_pll.c
 create mode 100644 drivers/video/omap2/dss/hdmi_wp.c
 delete mode 100644 drivers/video/omap2/dss/ti_hdmi_4xxx_ip.c
 delete mode 100644 drivers/video/omap2/dss/ti_hdmi_4xxx_ip.h

-- 
1.8.1.2


             reply	other threads:[~2013-09-17  7:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  7:18 Archit Taneja [this message]
2013-09-17  7:18 ` [PATCH 01/11] omapdss: HDMI: create a hdmi wrapper library Archit Taneja
2013-09-17  7:18 ` [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:18 ` [PATCH 03/11] omapdss: HDMI: create a PHY library Archit Taneja
2013-09-17  7:18 ` [PATCH 04/11] omapdss: HDMI: Use OMAP4 HDMI core functions directly and remove hdmi_ip_ops Archit Taneja
2013-09-17  7:18 ` [PATCH 05/11] omapdss: HDMI: remove hdmi_ip_data struct Archit Taneja
2013-09-17  7:18 ` [PATCH 06/11] omapdss: HDMI: Clean up the header files Archit Taneja
2013-09-17  7:18 ` [PATCH 07/11] omapdss: HDMI: add HDMI wrapper IRQ flags Archit Taneja
2013-09-17  7:18 ` [PATCH 09/11] omapdss: OMAP4: HDMI: remove unnecessary edid macros Archit Taneja
2013-09-17  7:18 ` [PATCH 10/11] omapdss: HDMI: move common functions to a separate file Archit Taneja
2013-09-17  7:18 ` [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-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).