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: [RFC 00/11] OMAPDSS: Add writeback mem to mem mode support
Date: Wed, 07 Nov 2012 14:56:18 +0000 [thread overview]
Message-ID: <1352299469-17609-1-git-send-email-archit@ti.com> (raw)
In-Reply-To: <n>
This series adds a writeback output driver and makes changes in APPLY to get
mem to mem mode working when writeback is connected to an overlay manager.
A user of writeback is supposed to use the fuctions exported by the writeback
output driver to configure writeback and start a mem to mem transfer. The output
driver internally calls function in APPLY to configure the writeback related
DISPC registers.
An example usage of writeback in omapfb is provided as the last patch.
Reference tree:
git://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone.git 3.8/wb_mem_to_mem
Archit Taneja (11):
OMAPDSS: Add writeback output driver
OMAPDSS: APPLY: Add get/set info functions for writeback
OMAPDSS: APPLY: Apply writeback configurations
OMAPDSS: writeback: Configure writeback input size
OMAPDSS: APPLY: Add writeback enable/disable funcs
OMAPDSS: APPLY: configure channel_in for writeback
OMAPDSS: writeback: add mechanism to do mem to mem updates
OMAPDSS: APPLY: Check if overlay is connected in mem to mem mode
OMAPDSS: FEATURES: Add writeback as supported outputs for OMAP4
managers
ARCH: ARM: OMAP: Create a platform device for writeback
Example: OMAPFB: clear framebuffers using writeback
arch/arm/mach-omap2/display.c | 9 +
drivers/video/omap2/dss/Kconfig | 13 ++
drivers/video/omap2/dss/Makefile | 1 +
drivers/video/omap2/dss/apply.c | 321 ++++++++++++++++++++++++++-
drivers/video/omap2/dss/core.c | 6 +
drivers/video/omap2/dss/dss.h | 24 +++
drivers/video/omap2/dss/dss_features.c | 6 +-
drivers/video/omap2/dss/writeback.c | 345 ++++++++++++++++++++++++++++++
drivers/video/omap2/omapfb/omapfb-main.c | 132 +++++++++++-
include/video/omapdss.h | 22 ++
10 files changed, 873 insertions(+), 6 deletions(-)
create mode 100644 drivers/video/omap2/dss/writeback.c
--
1.7.9.5
next reply other threads:[~2012-11-07 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 14:56 Archit Taneja [this message]
2012-11-07 14:56 ` [RFC 01/11] OMAPDSS: Add writeback output driver Archit Taneja
2012-11-07 14:56 ` [RFC 02/11] OMAPDSS: APPLY: Add get/set info functions for writeback Archit Taneja
2012-11-07 14:56 ` [RFC 03/11] OMAPDSS: APPLY: Apply writeback configurations Archit Taneja
2012-11-07 14:56 ` [RFC 04/11] OMAPDSS: writeback: Configure writeback input size Archit Taneja
2012-11-07 14:56 ` [RFC 05/11] OMAPDSS: APPLY: Add writeback enable/disable funcs Archit Taneja
2012-11-07 14:56 ` [RFC 06/11] OMAPDSS: APPLY: configure channel_in for writeback Archit Taneja
2012-11-07 14:56 ` [RFC 07/11] OMAPDSS: writeback: add mechanism to do mem to mem updates Archit Taneja
2012-11-07 14:56 ` [RFC 08/11] OMAPDSS: APPLY: Check if overlay is connected in mem to mem mode Archit Taneja
2012-11-07 14:56 ` [RFC 09/11] OMAPDSS: FEATURES: Add writeback as supported outputs for OMAP4 managers Archit Taneja
2012-11-07 14:56 ` [RFC 10/11] ARCH: ARM: OMAP: Create a platform device for writeback Archit Taneja
2012-11-07 14:56 ` [RFC 11/11] Example: OMAPFB: clear framebuffers using writeback 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=1352299469-17609-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).