linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] MERAM support for LCDC
Date: Tue, 26 Apr 2011 05:46:02 +0000	[thread overview]
Message-ID: <BANLkTinoRDza1WKsYdwKTJvumoUaqeYr3g@mail.gmail.com> (raw)
In-Reply-To: <1301369758-18394-1-git-send-email-dhobsong@igel.co.jp>

Hi Damian,

Thanks for your work on this!

On Tue, Mar 29, 2011 at 12:35 PM, Damian Hobson-Garcia
<dhobsong@igel.co.jp> wrote:
> This patch series is based on the fbdev tree.
>
> This series adds support for read-ahead cache access through the ICBs and
> MERAM available on SH devices.  The exact ICBs to use are chip specific
> and are specified in the platform data.
>
> Damian Hobson-Garcia (3):
>  sh_mobile_meram: MERAM framework for LCDC
>  sh_mobile_meram: Add support for NV24 framebuffers
>  sh_mobile_meram: MERAM platform data for LCDC

I think these patches look very good in general. I have one request
and some general comments:

Please add Runtime PM support to the MERAM driver. The MSTP113 bit of
SMSTPCR1 should be dynamically controlled using pm_runtime_get_sync()
and pm_runtime_put_sync().

I also wonder if we can chose to use MERAM dynamically somehow. I know
the sh7372 MERAM can be used to back the entire frame buffer memory
(controlled by the LRCTRL register, see the MERAM section in the
sh7372 data sheet). This fully-backed mode can perhaps be used to save
power for regular low-performance operation and/or semi-standby.

For low-performance operation I imagine that by using MERAM for frame
buffer memory we can put the SDRAM in self-refresh mode and that way
enter deep idle modes even though the screen is still operating.

The semi-standby would be that the "real" framebuffer is in say 32-bit
RGB in SDRAM, but we keep a 8-bit RGB shadow buffer in MERAM and
switch to that at the same instant we move from full backlight to low
backlight. This is most likely useful only when combined with
switching the LCD panel itself to 8-bit mode as well to save
bandwidth.

Then you have your full-performance mode that I guess is what these
patches implement. =)

Any ideas/suggestions about the low power LCDC modes?

Thanks,

/ magnus

  reply	other threads:[~2011-04-26  5:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  3:35 [RFC][PATCH 0/3] MERAM support for LCDC Damian Hobson-Garcia
2011-04-26  5:46 ` Magnus Damm [this message]
2011-04-28  6:08 ` Damian Hobson-Garcia
2011-05-09  7:03 ` Damian Hobson-Garcia
2011-05-09 16:22 ` Magnus Damm

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=BANLkTinoRDza1WKsYdwKTJvumoUaqeYr3g@mail.gmail.com \
    --to=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).