linux-omap.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, Archit Taneja <archit@ti.com>
Subject: [PATCH 0/3] OMAP: DSS2: DISPC register definition clean up
Date: Fri,  6 May 2011 11:45:48 +0530	[thread overview]
Message-ID: <1304662551-23832-1-git-send-email-archit@ti.com> (raw)

With more overlays and overlay managers on OMAP4, and more coming in future
OMAPs, the current way of defining the DISPC overlay and manager register
offsets through macros isn't scalable. Introduce a new dispc.h header which
contains Macros for common DISPC registers and inline functions for overlay and
manager specific registers. Remove usage of struct dispc_reg and use u16
instead.

Note:
Can be tried on:

https://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone/commits/master

Tested on: 4430sdp and 3430sdp.

Archit Taneja (3):
  OMAP: DSS2: Clean up DISPC overlay register definitions
  OMAP: DSS2: Clean up DISPC overlay manager register definitions
  OMAP: DSS2: Remove usage of struct dispc_reg

 drivers/video/omap2/dss/dispc.c | 1086 +++++++++++++++++---------------------
 drivers/video/omap2/dss/dispc.h |  544 ++++++++++++++++++++
 2 files changed, 1030 insertions(+), 600 deletions(-)
 create mode 100644 drivers/video/omap2/dss/dispc.h


             reply	other threads:[~2011-05-06  6:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  6:15 Archit Taneja [this message]
2011-05-06  6:15 ` [PATCH 1/3] OMAP: DSS2: Clean up DISPC overlay register definitions Archit Taneja
2011-05-06  6:15 ` [PATCH 2/3] OMAP: DSS2: Clean up DISPC overlay manager " Archit Taneja
2011-05-06  6:15 ` [PATCH 3/3] OMAP: DSS2: Remove usage of struct dispc_reg Archit Taneja
2011-05-09  6:53 ` [PATCH 0/3] OMAP: DSS2: DISPC register definition clean up 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=1304662551-23832-1-git-send-email-archit@ti.com \
    --to=archit@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).