public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/3] davinci: Map sram using MT_MEMORY_NONCACHED instead of MT_DEVICE
Date: Thu, 26 Aug 2010 14:37:28 -0700	[thread overview]
Message-ID: <87hbih2gyv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTi=9k19RUmfnNBO8AfFj_LtyNtsPPVYC_=-AW5yE@mail.gmail.com> (Kevin Hilman's message of "Thu, 19 Aug 2010 11:29:27 -0700")

Kevin Hilman <khilman@deeprootsystems•com> writes:

> On Sun, Aug 8, 2010 at 3:18 AM, Santosh Shilimkar
> <santosh.shilimkar@ti•com> wrote:
>> On Davinci SRAM is mapped as MT_DEVICE becasue of the section
>> mapping pre-requisite instead of intended MT_MEMORY_NONCACHED
>>
>> Since the section mapping limitation gets fixed with first
>> patch in this series, the MT_MEMORY_NONCACHED can be used now.
>>
>> Have not tested this, so somebody with Davinci hardware can
>> try this out
>>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti•com>
>> Cc: davinci-linux-open-source at linux.davincidsp.com
>> Cc: Kevin Hilman <khilman@deeprootsystems•com>
>
> Acked-by: Kevin Hilman <khilman@deeprootsystems•com>

Also, FYI... while not a very thorough test, I boot-tested this series
on DaVinci (dm355, omapl138) and it worked fine.

I'll include in davinci git (in the davinci-testing branch) so it gets a
bit more testing.

Kevin

  reply	other threads:[~2010-08-26 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 10:18 [PATCH 3/3] davinci: Map sram using MT_MEMORY_NONCACHED instead of MT_DEVICE Santosh Shilimkar
2010-08-19 18:29 ` Kevin Hilman
2010-08-26 21:37   ` Kevin Hilman [this message]
2010-08-27  4:46     ` Shilimkar, Santosh
2010-09-04  9:01       ` Shilimkar, Santosh

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=87hbih2gyv.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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