All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: [PATCH 0/3] OMAPFB: Move auto-update to omapfb
Date: Mon, 13 Jun 2011 09:12:51 +0000	[thread overview]
Message-ID: <1307956374-1107-1-git-send-email-tomi.valkeinen@ti.com> (raw)

OMAP DSS driver has currently support to change the display's update mode from
manual to auto, but it's up to the display to implement support for this.
Normally displays only support one update mode.

As the the update mode support adds extra code to a place where it doesn't
really belong, this patch set removes update mode support from omapdss, and
implements a simple version of it in omapfb.

This will:
* Clean up omapdss
* Keep the omapfb's ioctl interface intact with functional update-mode ioctls
* Allow us to support auto-update for manual update displays for testing
* Allow us to do the above with the code in single place, for all manual-update
  displays, without any changes needed in display drivers

Auto-update for manual-update displays should be considered a hack, used only
for testing or temporarily running a userspace that doesn't properly support
manual-update displays. It should not be used in production systems.

The patches create a private workqueue for the update work to minimize impact
on other parts of the system. As this auto-update feature is not normally used,
the workqueue is only created when needed.

 Tomi

Tomi Valkeinen (3):
  OMAP: DSS2: OMAPFB: Add struct to store per-display data
  OMAP: DSS2: OMAPFB: Implement auto-update mode
  OMAP: DSS2: remove update_mode from omapdss

 drivers/video/omap2/displays/panel-taal.c |   17 ---
 drivers/video/omap2/dss/display.c         |   45 --------
 drivers/video/omap2/dss/manager.c         |   59 +++--------
 drivers/video/omap2/dss/venc.c            |   17 ---
 drivers/video/omap2/omapfb/omapfb-ioctl.c |   72 +++++++-------
 drivers/video/omap2/omapfb/omapfb-main.c  |  159 +++++++++++++++++++++++------
 drivers/video/omap2/omapfb/omapfb-sysfs.c |   34 ++++++
 drivers/video/omap2/omapfb/omapfb.h       |   37 ++++++-
 include/video/omapdss.h                   |   11 --
 9 files changed, 241 insertions(+), 210 deletions(-)

-- 
1.7.4.1


WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: [PATCH 0/3] OMAPFB: Move auto-update to omapfb
Date: Mon, 13 Jun 2011 12:12:51 +0300	[thread overview]
Message-ID: <1307956374-1107-1-git-send-email-tomi.valkeinen@ti.com> (raw)

OMAP DSS driver has currently support to change the display's update mode from
manual to auto, but it's up to the display to implement support for this.
Normally displays only support one update mode.

As the the update mode support adds extra code to a place where it doesn't
really belong, this patch set removes update mode support from omapdss, and
implements a simple version of it in omapfb.

This will:
* Clean up omapdss
* Keep the omapfb's ioctl interface intact with functional update-mode ioctls
* Allow us to support auto-update for manual update displays for testing
* Allow us to do the above with the code in single place, for all manual-update
  displays, without any changes needed in display drivers

Auto-update for manual-update displays should be considered a hack, used only
for testing or temporarily running a userspace that doesn't properly support
manual-update displays. It should not be used in production systems.

The patches create a private workqueue for the update work to minimize impact
on other parts of the system. As this auto-update feature is not normally used,
the workqueue is only created when needed.

 Tomi

Tomi Valkeinen (3):
  OMAP: DSS2: OMAPFB: Add struct to store per-display data
  OMAP: DSS2: OMAPFB: Implement auto-update mode
  OMAP: DSS2: remove update_mode from omapdss

 drivers/video/omap2/displays/panel-taal.c |   17 ---
 drivers/video/omap2/dss/display.c         |   45 --------
 drivers/video/omap2/dss/manager.c         |   59 +++--------
 drivers/video/omap2/dss/venc.c            |   17 ---
 drivers/video/omap2/omapfb/omapfb-ioctl.c |   72 +++++++-------
 drivers/video/omap2/omapfb/omapfb-main.c  |  159 +++++++++++++++++++++++------
 drivers/video/omap2/omapfb/omapfb-sysfs.c |   34 ++++++
 drivers/video/omap2/omapfb/omapfb.h       |   37 ++++++-
 include/video/omapdss.h                   |   11 --
 9 files changed, 241 insertions(+), 210 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2011-06-13  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  9:12 Tomi Valkeinen [this message]
2011-06-13  9:12 ` [PATCH 0/3] OMAPFB: Move auto-update to omapfb Tomi Valkeinen
2011-06-13  9:12 ` [PATCH 1/3] OMAP: DSS2: OMAPFB: Add struct to store per-display data Tomi Valkeinen
2011-06-13  9:12   ` Tomi Valkeinen
2011-06-13  9:12 ` [PATCH 2/3] OMAP: DSS2: OMAPFB: Implement auto-update mode Tomi Valkeinen
2011-06-13  9:12   ` Tomi Valkeinen
2011-06-13  9:12 ` [PATCH 3/3] OMAP: DSS2: remove update_mode from omapdss Tomi Valkeinen
2011-06-13  9:12   ` 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=1307956374-1107-1-git-send-email-tomi.valkeinen@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.