From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: ye janboe <janboe.ye@gmail.com>,
khilman@deeprootsystems.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP SRAM: flush the right address after memcpy in omap_sram_push
Date: Fri, 28 Aug 2009 09:03:10 -0700 [thread overview]
Message-ID: <20090828160310.GJ25828@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908280443110.15963@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [090828 03:43]:
> On Fri, 28 Aug 2009, ye janboe wrote:
>
> > the original flush operation is to flush the function address which is
> > copied from.
> > But we do not change the function code and it is not necessary to flush it.
> >
> > Signed-off-by: janboe <janboe.ye@gmail.com>
>
> Acked-by: Paul Walmsley <paul@pwsan.com>
>
> thanks Janboe.
>
> Tony, you want to take this one, or do you want me to?
I can add it to my omap-fixes unless you have a fixes series of your
own coming up.
Tony
> - Paul
>
>
> > ---
> > arch/arm/plat-omap/sram.c | 3 ++-
> > 1 files changed, 2 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
> > index f2b0fa6..f549d8a 100644
> > --- a/arch/arm/plat-omap/sram.c
> > +++ b/arch/arm/plat-omap/sram.c
> > @@ -270,7 +270,8 @@ void * omap_sram_push(void * start, unsigned long size)
> > omap_sram_ceil -= size;
> > omap_sram_ceil = ROUND_DOWN(omap_sram_ceil, sizeof(void *));
> > memcpy((void *)omap_sram_ceil, start, size);
> > - flush_icache_range((unsigned long)start, (unsigned long)(start + size));
> > + flush_icache_range((unsigned long)omap_sram_ceil,
> > + (unsigned long)(omap_sram_ceil + size));
> >
> > return (void *)omap_sram_ceil;
> > }
> >
>
>
prev parent reply other threads:[~2009-08-28 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 9:26 [PATCH] OMAP SRAM: flush the right address after memcpy in omap_sram_push ye janboe
2009-08-28 10:43 ` Paul Walmsley
2009-08-28 16:03 ` Tony Lindgren [this message]
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=20090828160310.GJ25828@atomide.com \
--to=tony@atomide.com \
--cc=janboe.ye@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.