linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/5 v4] LCDC MERAM runtime PM support
Date: Mon, 11 Jul 2011 05:36:42 +0000	[thread overview]
Message-ID: <20110711053642.GH24169@linux-sh.org> (raw)
In-Reply-To: <1309766728-32419-1-git-send-email-dhobsong@igel.co.jp>

On Mon, Jul 04, 2011 at 05:05:28PM +0900, Damian Hobson-Garcia wrote:
> This patch series is a provides PM runtime support for the LCDC MERAM.
> 
> The runtime_pm_get/put calls are made at the same time as the LCDC calls, so
> that the LCDC MERAM is enabled with the first LCDC device and disabled 
> with the last LCDC device.
> 
> The first 4 patches will apply to rmobile-latest or common/fbdev-meram as-is,
> but the final patch needs to have the "PM / Domains: Support for generic I/O PM
> domains" patch series. 
> 
> Only the first 2 patches of the series have been updated from v3 sent on
> 2011/06/22
> 
> Changes from V3
> 
> * Remove the MERAM callbacks used to runtime_get/runtime_put the device from
>   the LCDC driver.  Instead, just call the functions on the MERAM device
>   directly
> 
> Damian Hobson-Garcia (5):
>   fbdev: sh_mobile_meram: Enable runtime PM
>   fbdev: sh_mobile_meram: Enable/disable MERAM along with LCDC - v4
>   fbdev: sh_mobile_meram: Move private data from .h to .c 
>   fbdev: sh_mobile_meram: Backup/restore device registers on
>     shutdown/resume - v3
>   fbdev: sh_mobile_meram: Assign meram to the SH7372_A4LC power domain
> 
I've applied 1-4, and will roll in the last one once the power domain
stuff hits mainline.

  reply	other threads:[~2011-07-11  5:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04  8:05 [PATCH 0/5 v4] LCDC MERAM runtime PM support Damian Hobson-Garcia
2011-07-11  5:36 ` Paul Mundt [this message]
2011-07-11  5:50 ` Paul Mundt

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=20110711053642.GH24169@linux-sh.org \
    --to=lethal@linux-sh.org \
    --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).