linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: felipe.contreras@gmail.com (Felipe Contreras)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] tidspbridge: use a parameter to allocate shared memory
Date: Fri, 8 Oct 2010 11:20:24 +0300	[thread overview]
Message-ID: <AANLkTikHMewD94ZBb9P4AF9oM2ZfnpA-yjO67Dx2Lg9r@mail.gmail.com> (raw)
In-Reply-To: <4CAE1CA1.4050006@ti.com>

On Thu, Oct 7, 2010 at 10:16 PM, Omar Ramirez Luna <omar.ramirez@ti.com> wrote:
> On 10/7/2010 1:22 PM, Felipe Contreras wrote:
>> Anyway, we will not know for sure until we try... Right?
>
> yes we can try, at least we now for sure arm side can be done.

The only thing that changes is the cacheability of the ARM side
memory, so of course only the ARM side matters. The DSP side will
continue to do what it's doing and would not notice any difference if
the memory is flushed, or is non-cacheable.

-- 
Felipe Contreras

  parent reply	other threads:[~2010-10-08  8:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07  5:45 [RFC] tidspbridge: use a parameter to allocate shared memory Omar Ramirez Luna
2010-10-07  7:40 ` Laurent Pinchart
2010-10-07  8:32   ` Russell King - ARM Linux
2010-10-07 14:01     ` Laurent Pinchart
2010-10-07 17:13       ` Omar Ramirez Luna
2010-10-07 19:07       ` Russell King - ARM Linux
2010-10-07 17:01   ` Omar Ramirez Luna
2010-10-07 18:22     ` Felipe Contreras
2010-10-07 19:16       ` Omar Ramirez Luna
2010-10-08  8:18         ` Felipe Contreras
2010-10-08 17:20           ` Omar Ramirez Luna
2010-10-08  8:20         ` Felipe Contreras [this message]
2010-10-08 17:31           ` Omar Ramirez Luna

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=AANLkTikHMewD94ZBb9P4AF9oM2ZfnpA-yjO67Dx2Lg9r@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).