linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/5] ARM: move VFP init to an earlier boot stage
Date: Mon,  8 Jul 2013 23:11:57 +0100	[thread overview]
Message-ID: <1373321521-15485-2-git-send-email-ard.biesheuvel@linaro.org> (raw)
In-Reply-To: <1373321521-15485-1-git-send-email-ard.biesheuvel@linaro.org>

In order to use the NEON unit in the kernel, we should
initialize it a bit earlier in the boot process so NEON users
that like to do a quick benchmark at load time (like the
xor_blocks or RAID-6 code) find the NEON/VFP unit already
enabled.

Replaced late_initcall() with core_initcall().

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Nicolas Pitre <nico@linaro.org>
---
 arch/arm/vfp/vfpmodule.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/vfp/vfpmodule.c b/arch/arm/vfp/vfpmodule.c
index 5dfbb0b..791993a 100644
--- a/arch/arm/vfp/vfpmodule.c
+++ b/arch/arm/vfp/vfpmodule.c
@@ -731,4 +731,4 @@ static int __init vfp_init(void)
 	return 0;
 }
 
-late_initcall(vfp_init);
+core_initcall(vfp_init);
-- 
1.8.1.2

  reply	other threads:[~2013-07-08 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 22:11 [PATCH v3 0/5] kernel mode NEON support Ard Biesheuvel
2013-07-08 22:11 ` Ard Biesheuvel [this message]
2013-07-08 22:11 ` [PATCH v3 2/5] ARM: be strict about FP exceptions in kernel mode Ard Biesheuvel
2013-07-08 22:11 ` [PATCH v3 3/5] ARM: add support for kernel mode NEON Ard Biesheuvel
2013-07-08 22:12 ` [PATCH v3 4/5] ARM: crypto: add NEON accelerated XOR implementation Ard Biesheuvel
2013-07-08 22:12 ` [PATCH v3 5/5] lib/raid6: add ARM-NEON accelerated syndrome calculation Ard Biesheuvel
2013-07-08 22:16   ` H. Peter Anvin
2013-09-22 10:11 ` [PATCH v3 0/5] kernel mode NEON support Russell King - ARM Linux
2013-09-22 10:24   ` Ard Biesheuvel

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=1373321521-15485-2-git-send-email-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.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).