Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-fbdev@vger.kernel.org
Subject: [RFC/PATCH 0/6] SH Mobile LCDC MERAM-based frame buffer backing store
Date: Thu, 15 Mar 2012 17:43:48 +0000	[thread overview]
Message-ID: <1331833434-11934-1-git-send-email-laurent.pinchart@ideasonboard.com> (raw)

Hi everybody,

This patch set implements support for storing the frame buffer contents in the
on-chip SRAM (MERAM). This will allow keeping the display on while putting
system memory in a low-power mode (assuming the CPU is idle). The main use case
is to reduce power consumption on mobile platforms when the user doesn't
interact with the device and lets it lock itself automatically after a short
timeout.

This is a first implementation and improvements are possible (such as copying
the frame buffer content using DMA, possibly through the VEU to handle format
conversion). I've tested it on a Mackerel board.

Laurent Pinchart (6):
  sh_mobile_meram: Rename operations to cache_[alloc|free|update]
  sh_mobile_meram: Use direct function calls for the public API
  sh_mobile_meram: Add direct MERAM allocation API
  fbdev: sh_mobile_lcdc: Fix pan offset computation in YUV mode
  fbdev: sh_mobile_lcdc: Destroy mutex at remove time
  fbdev: sh_mobile_lcdc: Added MERAM-backed frame buffer support

 drivers/video/sh_mobile_lcdcfb.c |  254 +++++++++++++++++++++++++++----------
 drivers/video/sh_mobile_lcdcfb.h |   10 ++-
 drivers/video/sh_mobile_meram.c  |  227 +++++++++++++++++++---------------
 include/video/sh_mobile_lcdc.h   |    1 +
 include/video/sh_mobile_meram.h  |   71 ++++++++---
 5 files changed, 370 insertions(+), 193 deletions(-)

-- 
Regards,

Laurent Pinchart


                 reply	other threads:[~2012-03-15 17:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1331833434-11934-1-git-send-email-laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox