From: Jeff Ohlstein <johlstei@codeaurora.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dwalker@codeaurora.org,
Jeff Ohlstein <johlstei@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Nicolas Pitre <nico@marvell.com>, Tejun Heo <tj@kernel.org>
Subject: [PATCH] arm: dma-mapping: move consistent_init to early_initcall
Date: Thu, 2 Dec 2010 14:11:18 -0800 [thread overview]
Message-ID: <1291327879-28073-1-git-send-email-johlstei@codeaurora.org> (raw)
Some machines require the use of coherent memory to bring up auxillary
cpus, and thus want to use dma_alloc_coherent prior to smp_init
completing.
Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org>
---
arch/arm/mm/dma-mapping.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
index ac6a361..d46ce8d 100644
--- a/arch/arm/mm/dma-mapping.c
+++ b/arch/arm/mm/dma-mapping.c
@@ -177,7 +177,7 @@ static int __init consistent_init(void)
return ret;
}
-core_initcall(consistent_init);
+early_initcall(consistent_init);
static void *
__dma_alloc_remap(struct page *page, size_t size, gfp_t gfp, pgprot_t prot)
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: johlstei@codeaurora.org (Jeff Ohlstein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dma-mapping: move consistent_init to early_initcall
Date: Thu, 2 Dec 2010 14:11:18 -0800 [thread overview]
Message-ID: <1291327879-28073-1-git-send-email-johlstei@codeaurora.org> (raw)
Some machines require the use of coherent memory to bring up auxillary
cpus, and thus want to use dma_alloc_coherent prior to smp_init
completing.
Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org>
---
arch/arm/mm/dma-mapping.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
index ac6a361..d46ce8d 100644
--- a/arch/arm/mm/dma-mapping.c
+++ b/arch/arm/mm/dma-mapping.c
@@ -177,7 +177,7 @@ static int __init consistent_init(void)
return ret;
}
-core_initcall(consistent_init);
+early_initcall(consistent_init);
static void *
__dma_alloc_remap(struct page *page, size_t size, gfp_t gfp, pgprot_t prot)
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Ohlstein <johlstei@codeaurora.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dwalker@codeaurora.org,
Jeff Ohlstein <johlstei@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Nicolas Pitre <nico@marvell.com>, Tejun Heo <tj@kernel.org>
Subject: [PATCH] arm: dma-mapping: move consistent_init to early_initcall
Date: Thu, 2 Dec 2010 14:11:18 -0800 [thread overview]
Message-ID: <1291327879-28073-1-git-send-email-johlstei@codeaurora.org> (raw)
Some machines require the use of coherent memory to bring up auxillary
cpus, and thus want to use dma_alloc_coherent prior to smp_init
completing.
Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org>
---
arch/arm/mm/dma-mapping.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
index ac6a361..d46ce8d 100644
--- a/arch/arm/mm/dma-mapping.c
+++ b/arch/arm/mm/dma-mapping.c
@@ -177,7 +177,7 @@ static int __init consistent_init(void)
return ret;
}
-core_initcall(consistent_init);
+early_initcall(consistent_init);
static void *
__dma_alloc_remap(struct page *page, size_t size, gfp_t gfp, pgprot_t prot)
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2010-12-02 22:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 22:11 Jeff Ohlstein [this message]
2010-12-02 22:11 ` [PATCH] arm: dma-mapping: move consistent_init to early_initcall Jeff Ohlstein
2010-12-02 22:11 ` Jeff Ohlstein
2010-12-02 22:19 ` Russell King - ARM Linux
2010-12-02 22:19 ` Russell King - ARM Linux
2010-12-03 20:06 ` Saravana Kannan
2010-12-03 20:06 ` Saravana Kannan
2010-12-03 20:36 ` Russell King - ARM Linux
2010-12-03 20:36 ` Russell King - ARM Linux
2010-12-03 22:45 ` Jamie Iles
2010-12-03 22:45 ` Jamie Iles
2010-12-07 6:22 ` Saravana Kannan
2010-12-07 6:22 ` Saravana Kannan
2010-12-09 9:23 ` skannan
2010-12-09 9:23 ` skannan
2010-12-09 9:23 ` skannan at codeaurora.org
2010-12-09 10:38 ` Russell King - ARM Linux
2010-12-09 10:38 ` Russell King - ARM Linux
2010-12-10 0:58 ` Saravana Kannan
2010-12-10 0:58 ` Saravana Kannan
2010-12-10 10:00 ` Catalin Marinas
2010-12-10 10:00 ` Catalin Marinas
2010-12-12 4:58 ` Saravana Kannan
2010-12-12 4:58 ` Saravana Kannan
2010-12-13 15:26 ` Catalin Marinas
2010-12-13 15:26 ` Catalin Marinas
2010-12-17 2:55 ` Saravana Kannan
2010-12-17 2:55 ` Saravana Kannan
2010-12-17 2:55 ` Saravana Kannan
2010-12-17 9:48 ` Russell King - ARM Linux
2010-12-17 9:48 ` Russell King - ARM Linux
2010-12-17 10:26 ` Saravana Kannan
2010-12-17 10:26 ` Saravana Kannan
2010-12-17 10:26 ` Saravana Kannan
2010-12-17 10:56 ` Russell King - ARM Linux
2010-12-17 10:56 ` Russell King - ARM Linux
2010-12-17 11:09 ` Saravana Kannan
2010-12-17 11:09 ` Saravana Kannan
2010-12-17 11:09 ` Saravana Kannan
2010-12-17 11:31 ` Catalin Marinas
2010-12-17 11:31 ` Catalin Marinas
2010-12-17 23:14 ` Saravana Kannan
2010-12-17 23:14 ` Saravana Kannan
2010-12-17 23:14 ` Saravana Kannan
2010-12-20 23:22 ` Saravana Kannan
2010-12-20 23:22 ` Saravana Kannan
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=1291327879-28073-1-git-send-email-johlstei@codeaurora.org \
--to=johlstei@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@marvell.com \
--cc=tj@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.