SUPERH platform development
 help / color / mirror / Atom feed
From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6 v2] MERAM support for LCDC
Date: Tue, 24 May 2011 02:53:59 +0000	[thread overview]
Message-ID: <4DDB1DC7.6080809@igel.co.jp> (raw)
In-Reply-To: <1305717011-20742-1-git-send-email-dhobsong@igel.co.jp>

Hi Paul,

On 2011/05/23 15:51, Paul Mundt wrote:
> On Wed, May 18, 2011 at 08:10:05PM +0900, Damian Hobson-Garcia wrote:
>> This patch series adds support for read-ahead cache-access from the 
>> LCDC to the main memory.  These patches enabled the LCDC to access
>> the MERAM memory via ICB.  The specific ICBs to use are chip dependent
>> and defined in the platform data.
>>
>> The MERAM clock will enable when the LCDC clocks do, and are allowed to 
>> be disbled when the LCDC clocks are.
>>
>> Changes from V1
>> ---------------
>> * Specified meram info data (struct sh_mobile_meram_info *meram_dev) as
>>   part of the LCDC device data, not the LCDC channel data, since the info
>>   data corresponds to the whole device, not just one configuration.
>>
>> * Added dynamic clock enable/disable via runtime_pm.
>>
>> * Changed .id from -1 to 0 in platform data
>>
>> Damian Hobson-Garcia (6):
>>   sh_mobile: Add MSTP clock for MERAM
>>   sh_mobile_meram: MERAM framework for LCDC
>>   sh_mobile_meram: Add support for NV24 framebuffers
> 
> These basically seem to be fine, and make up for the bulk of the new
> code, so I'll take them as-is. I'll let you and Magnus hash out the
> remaining bits after this.

Ok great, thanks a lot. I'll submit any further patches to apply on top
of these three.

Damian

  parent reply	other threads:[~2011-05-24  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 11:10 [PATCH 0/6 v2] MERAM support for LCDC Damian Hobson-Garcia
2011-05-23  6:51 ` Paul Mundt
2011-05-24  2:53 ` Damian Hobson-Garcia [this message]
2011-05-26  4:10 ` Magnus Damm
2011-05-26  6:31 ` Damian Hobson-Garcia

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=4DDB1DC7.6080809@igel.co.jp \
    --to=dhobsong@igel.co.jp \
    --cc=linux-sh@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