linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v2 3/5] ARM: kernel: update cpu_suspend code to use cache LoUIS operations
Date: Tue, 11 Dec 2012 23:27:39 +0000	[thread overview]
Message-ID: <50C7C16B.7050106@codeaurora.org> (raw)
In-Reply-To: <20121211163843.GH16759@mudshark.cambridge.arm.com>

On 12/11/12 08:38, Will Deacon wrote:
> diff --git a/arch/arm/mm/cache-v7.S b/arch/arm/mm/cache-v7.S
> index cd95664..f58248f 100644
> --- a/arch/arm/mm/cache-v7.S
> +++ b/arch/arm/mm/cache-v7.S
> @@ -44,7 +44,8 @@ ENDPROC(v7_flush_icache_all)
>  ENTRY(v7_flush_dcache_louis)
>         dmb                                     @ ensure ordering with previous memory accesses
>         mrc     p15, 1, r0, c0, c0, 1           @ read clidr, r0 = clidr
> -       ands    r3, r0, #0xe00000               @ extract LoUIS from clidr
> +       ALT_SMP(ands    r3, r0, #(7 << 21))     @ extract LoUIS from clidr
> +       ALT_UP(ands     r3, r0, #(7 << 27))     @ extract LoUU from clidr
>         mov     r3, r3, lsr #20                 @ r3 = LoUIS * 2

You need to fix this mov as well, right?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation


  parent reply	other threads:[~2012-12-11 23:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347986135-17979-1-git-send-email-lorenzo.pieralisi@arm.com>
     [not found] ` <1347986135-17979-4-git-send-email-lorenzo.pieralisi@arm.com>
     [not found]   ` <20120919134658.GA2111@linaro.org>
     [not found]     ` <20120920102514.GD4588@e102568-lin.cambridge.arm.com>
     [not found]       ` <20120920110439.GB2117@linaro.org>
2012-12-11 16:07         ` [RFC PATCH v2 3/5] ARM: kernel: update cpu_suspend code to use cache LoUIS operations Guennadi Liakhovetski
2012-12-11 16:33           ` Will Deacon
2012-12-11 16:38             ` Will Deacon
2012-12-11 17:07               ` Guennadi Liakhovetski
2012-12-11 17:47                 ` Will Deacon
2012-12-11 17:55               ` Guennadi Liakhovetski
2012-12-11 23:27               ` Stephen Boyd [this message]
2012-12-12 10:31                 ` Will Deacon
2012-12-12 16:43                   ` Guennadi Liakhovetski
2012-12-12 10:33                 ` Lorenzo Pieralisi
2012-12-12 13:36                   ` Will Deacon
2012-12-13  8:09                     ` Guennadi Liakhovetski
2012-12-13 10:51                       ` Will Deacon
2012-12-13 14:32                         ` Guennadi Liakhovetski
2012-12-13 14:39                           ` Santosh Shilimkar
2012-12-28 11:32                             ` [PATCH v2] ARM: sh7372: fix cache clean / invalidate order Guennadi Liakhovetski
2012-12-28 21:50                               ` Simon Horman
2012-12-13 14:52                           ` [RFC PATCH v2 3/5] ARM: kernel: update cpu_suspend code to use cache LoUIS operations Will Deacon
2012-12-12 16:43                   ` Guennadi Liakhovetski

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=50C7C16B.7050106@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).