From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: Use a CR_C constant instead of a hard-coded one
Date: Tue, 29 Sep 2015 18:02:09 +0200 [thread overview]
Message-ID: <87twqdqkn2.fsf@free-electrons.com> (raw)
In-Reply-To: <1439214471-25902-1-git-send-email-gregory.clement@free-electrons.com> (Gregory CLEMENT's message of "Mon, 10 Aug 2015 15:47:51 +0200")
On lun., ao?t 10 2015, Gregory CLEMENT <gregory.clement@free-electrons.com> wrote:
> Fix the armada_370_xp_pmsu_idle_enter() function to use a CR_C
> constant instead of a hard-coded constant in the assembly part.
> This clean-up was suggested by Russell King.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Applied on mvebu/cleanup
> ---
> Hi,
>
> this clean-up is not for 4.2 neither for 4.3 (the rc6 had just been
> released), but for 4.4. I send it now to not forget it.
>
> Gregory
>
> arch/arm/mach-mvebu/pmsu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-mvebu/pmsu.c b/arch/arm/mach-mvebu/pmsu.c
> index 4f4e22206ae5..8efb83cea83d 100644
> --- a/arch/arm/mach-mvebu/pmsu.c
> +++ b/arch/arm/mach-mvebu/pmsu.c
> @@ -296,11 +296,11 @@ int armada_370_xp_pmsu_idle_enter(unsigned long deepidle)
> /* Test the CR_C bit and set it if it was cleared */
> asm volatile(
> "mrc p15, 0, r0, c1, c0, 0 \n\t"
> - "tst r0, #(1 << 2) \n\t"
> + "tst r0, %0 \n\t"
> "orreq r0, r0, #(1 << 2) \n\t"
> "mcreq p15, 0, r0, c1, c0, 0 \n\t"
> "isb "
> - : : : "r0");
> + : : "Ir" (CR_C) : "r0");
>
> pr_debug("Failed to suspend the system\n");
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2015-09-29 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 13:47 [PATCH] ARM: mvebu: Use a CR_C constant instead of a hard-coded one Gregory CLEMENT
2015-09-29 16:02 ` Gregory CLEMENT [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=87twqdqkn2.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--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 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.