All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap3: Prevent SDRC deadlock when L3 is changing frequency
Date: Wed, 15 Sep 2010 15:38:47 -0600 (MDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1009151537000.458@utopia.booyaka.com> (raw)
In-Reply-To: <1279728155-2643-1-git-send-email-jon-hunter@ti.com>

Jon,

one other brief note:

On Wed, 21 Jul 2010, Jon Hunter wrote:

> diff --git a/arch/arm/mach-omap2/sram34xx.S b/arch/arm/mach-omap2/sram34xx.S
> index de99ba2..e87e730 100644
> --- a/arch/arm/mach-omap2/sram34xx.S
> +++ b/arch/arm/mach-omap2/sram34xx.S
> @@ -129,8 +129,11 @@ ENTRY(omap3_sram_configure_core_dpll)
>  	ldr	r4, [sp, #80]
>  	str     r4, omap_sdrc_mr_1_val
>  skip_cs1_params:
> +	mrc p15, 0, r8, c1, c0, 0	@ read aux ctrl register
> +	bic r10, r8, #0x800		@ clear Z-bit, disable branch prediction
> +	mcr p15, 0, r10, c1, c0, 0	@ write aux ctrl register

Please be careful with the whitespace between the opcode and the 
arguments - I will fix this in the current patch but it seems best to keep 
this consistent.


- Paul

      parent reply	other threads:[~2010-09-15 21:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 16:02 [PATCH] omap3: Prevent SDRC deadlock when L3 is changing frequency Jon Hunter
2010-09-15 19:15 ` Paul Walmsley
2010-09-15 22:40   ` Tony Lindgren
2010-09-15 23:10     ` Paul Walmsley
2010-09-16  4:58       ` Gadiyar, Anand
2010-09-16 18:57         ` Tony Lindgren
2010-09-16 20:23           ` Gadiyar, Anand
2010-09-16 20:49             ` Tony Lindgren
2010-09-17  0:05               ` Woodruff, Richard
2010-09-16  6:05   ` Woodruff, Richard
2010-09-16  6:24     ` Shilimkar, Santosh
2010-09-17 18:30       ` Paul Walmsley
2010-09-15 21:38 ` Paul Walmsley [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=alpine.DEB.2.00.1009151537000.458@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-omap@vger.kernel.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 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.