From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Russell King <linux@arm.linux.org.uk>,
"Gomez Castellanos, Ivan" <ivan.gomez@ti.com>,
"Ramos Falcon, Ernesto" <ernesto@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] tidspbridge: use a parameter to allocate shared memory
Date: Fri, 8 Oct 2010 12:31:14 -0500 [thread overview]
Message-ID: <4CAF5562.9060107@ti.com> (raw)
In-Reply-To: <AANLkTikHMewD94ZBb9P4AF9oM2ZfnpA-yjO67Dx2Lg9r@mail.gmail.com>
On 10/8/2010 3:20 AM, Felipe Contreras wrote:
> 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.
>
Please find my reply for the previous mail:
http://marc.info/?l=linux-omap&m=128655845213913&w=2
Regards,
Omar
WARNING: multiple messages have this Message-ID (diff)
From: omar.ramirez@ti.com (Omar Ramirez Luna)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] tidspbridge: use a parameter to allocate shared memory
Date: Fri, 8 Oct 2010 12:31:14 -0500 [thread overview]
Message-ID: <4CAF5562.9060107@ti.com> (raw)
In-Reply-To: <AANLkTikHMewD94ZBb9P4AF9oM2ZfnpA-yjO67Dx2Lg9r@mail.gmail.com>
On 10/8/2010 3:20 AM, Felipe Contreras wrote:
> 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.
>
Please find my reply for the previous mail:
http://marc.info/?l=linux-omap&m=128655845213913&w=2
Regards,
Omar
next prev parent reply other threads:[~2010-10-08 17:31 UTC|newest]
Thread overview: 26+ 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 5:45 ` Omar Ramirez Luna
2010-10-07 7:40 ` Laurent Pinchart
2010-10-07 7:40 ` Laurent Pinchart
2010-10-07 8:32 ` Russell King - ARM Linux
2010-10-07 8:32 ` Russell King - ARM Linux
2010-10-07 14:01 ` Laurent Pinchart
2010-10-07 14:01 ` Laurent Pinchart
2010-10-07 17:13 ` Omar Ramirez Luna
2010-10-07 17:13 ` Omar Ramirez Luna
2010-10-07 19:07 ` Russell King - ARM Linux
2010-10-07 19:07 ` Russell King - ARM Linux
2010-10-07 17:01 ` Omar Ramirez Luna
2010-10-07 17:01 ` Omar Ramirez Luna
2010-10-07 18:22 ` Felipe Contreras
2010-10-07 18:22 ` Felipe Contreras
2010-10-07 19:16 ` Omar Ramirez Luna
2010-10-07 19:16 ` Omar Ramirez Luna
2010-10-08 8:18 ` Felipe Contreras
2010-10-08 8:18 ` Felipe Contreras
2010-10-08 17:20 ` Omar Ramirez Luna
2010-10-08 17:20 ` Omar Ramirez Luna
2010-10-08 8:20 ` Felipe Contreras
2010-10-08 8:20 ` Felipe Contreras
2010-10-08 17:31 ` Omar Ramirez Luna [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=4CAF5562.9060107@ti.com \
--to=omar.ramirez@ti.com \
--cc=ernesto@ti.com \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@suse.de \
--cc=ivan.gomez@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.