All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] flush I-cache after omap_sram_push()
Date: Fri, 23 Nov 2007 13:15:28 -0800	[thread overview]
Message-ID: <20071123211527.GH559@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274290282BF37@dlee13.ent.ti.com>

* Woodruff, Richard <r-woodruff2@ti.com> [071120 08:16]:
> > This patch implements a suggestion by Richard Woodruff
> > <r-woodruff2@ti.com>.  omap_sram_push() copies executable code into
> > SRAM memory.  Currently this happens before Linux executes anything
> > from the SRAM, so we don't have to worry about evicting any SRAM lines
> > from the I-cache.  But at some point in the future, the SRAM might be
> > used more dynamically, adding and removing code while the system is
> > running.  So we should ensure that the I-cache is clean or at
> > least up-to-date after the copy.
> > 
> > Signed-off-by: Paul Walmsley <paul@pwsan.com>
> 
> Signedoff-by: Richard Woodruff <r-woodruff2@ti.com>
>  
> > ---
> >  arch/arm/plat-omap/sram.c |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > Index: linux-omap/arch/arm/plat-omap/sram.c
> > ===================================================================
> > --- linux-omap.orig/arch/arm/plat-omap/sram.c	2007-11-16
> > 17:41:42.000000000 -0700
> > +++ linux-omap/arch/arm/plat-omap/sram.c	2007-11-16 17:43:18.000000000 -
> > 0700
> > @@ -216,6 +216,7 @@
> >  	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));
> > 
> >  	return (void *)omap_sram_ceil;
> >  }
> 
> Looks good.

Pushing today.

Tony

      reply	other threads:[~2007-11-23 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  8:30 [PATCH 0/5] SRAM patcher: patch register addresses in SRAM code at runtime Paul Walmsley
2007-11-14  8:30 ` [PATCH 1/5] SRAM patcher: add SRAM virtual address patcher Paul Walmsley
2007-11-14  8:30 ` [PATCH 2/5] SRAM patcher: convert omap24xx_sram_suspend to use runtime SRAM patcher Paul Walmsley
2007-11-14  8:30 ` [PATCH 3/5] SRAM patcher: convert sram_ddr_init " Paul Walmsley
2007-11-14  8:30 ` [PATCH 4/5] SRAM patcher: convert sram_reprogram_sdrc " Paul Walmsley
2007-11-14  8:30 ` [PATCH 5/5] SRAM patcher: convert omap2_set_prcm " Paul Walmsley
2007-11-14 17:38 ` [PATCH 0/5] SRAM patcher: patch register addresses in SRAM code at runtime Kevin Hilman
2007-11-14 19:12 ` [PATCH 0/5] SRAM patcher: patch register addresses in SRAM code atruntime Woodruff, Richard
2007-11-16 19:33   ` Paul Walmsley
2007-11-16 19:42     ` Woodruff, Richard
2007-11-16 22:35       ` Tony Lindgren
2007-11-19 19:11       ` [PATCH] flush I-cache after omap_sram_push() Paul Walmsley
2007-11-20 16:14         ` Woodruff, Richard
2007-11-23 21:15           ` 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=20071123211527.GH559@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.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.