public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hemanth V" <hemanthv@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux-arm-kernel@lists.arm.linux.org.uk
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] OMAP4: SMP: Add OMAP4430 SMP board files
Date: Fri, 8 May 2009 11:15:59 +0530	[thread overview]
Message-ID: <04c801c9cfa0$4563dfa0$LocalHost@wipultra793> (raw)
In-Reply-To: 1241681366-21094-1-git-send-email-santosh.shilimkar@ti.com

---- Original Message ----- 
From: "Santosh Shilimkar" <santosh.shilimkar@ti.com>
Subject: [PATCH 1/3] OMAP4: SMP: Add OMAP4430 SMP board files


> diff --git a/arch/arm/mach-omap2/omap-headsmp.S 
> b/arch/arm/mach-omap2/omap-headsmp.S
> new file mode 100644
> index 0000000..0afe039
> --- /dev/null
> +++ b/arch/arm/mach-omap2/omap-headsmp.S
> @@ -0,0 +1,49 @@
> +/*
> + * Secondary CPU startup routine source file.
> + *
> + * Copyright (C) 2009 Texas Instruments, Inc.
> + *
> + * Author:
> + *      Santosh Shilimkar <santosh.shilimkar@ti.com>
> + *
> + * Interface functions needed for the SMP. This file is based on arm
> + * realview smp platform.
> + * Copyright (c) 2003 ARM Limited.
> + *
> + * This program is free software,you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +
> +#include <linux/linkage.h>
> +#include <linux/init.h>
> +
> + __INIT
> +
> +/*
> + * OMAP4 specific entry point for secondary CPU to jump from ROM
> + * code.  This routine also provides a holding flag into which
> + * secondary core is held until we're ready for it to initialise.
> + * The primary core will update the this flag using a hardware
> + * register AuxCoreBoot1.
> + */

Is initialization done by u-boot like icache_enable taken care somewhere
for the secondary cpu.




  parent reply	other threads:[~2009-05-08  5:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  7:29 [PATCH 1/3] OMAP4: SMP: Add OMAP4430 SMP board files Santosh Shilimkar
2009-05-07  7:29 ` [PATCH 2/3] OMAP4: SMP: Add mpu timer support for OMAP4430 Santosh Shilimkar
2009-05-07  7:29   ` [PATCH 3/3] OMAP4: SMP: Enable SMP " Santosh Shilimkar
2009-05-07 20:46 ` [PATCH 1/3] OMAP4: SMP: Add OMAP4430 SMP board files Tony Lindgren
2009-05-08  5:09   ` Shilimkar, Santosh
2009-05-08 15:17     ` Tony Lindgren
2009-05-08 16:44       ` Shilimkar, Santosh
2009-05-13 14:53       ` [PATCH] OMAP: Remove IRQ hardcoding from serial.c Shilimkar, Santosh
     [not found]         ` <d6a0f7aa0905150325u51104b24t945a7841074bb913@mail.gmail.com>
2009-05-15 10:30           ` Govindraj.R
2009-05-18 21:45         ` [PATCH] " Tony Lindgren
2009-05-19  4:22           ` Shilimkar, Santosh
2009-05-16 10:30   ` [PATCH 1/3] OMAP4: SMP: Add OMAP4430 SMP board files Russell King - ARM Linux
2009-05-07 20:51 ` Tony Lindgren
2009-05-08  5:45 ` Hemanth V [this message]
2009-05-08  5:48   ` Shilimkar, Santosh
2009-05-08  6:13     ` Hemanth V
2009-05-08  6:57       ` Shilimkar, Santosh
2009-05-16 10:31         ` Russell King - ARM Linux
2009-05-16 10:28 ` Russell King - ARM Linux
2009-05-16 21:21   ` Shilimkar, Santosh

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='04c801c9cfa0$4563dfa0$LocalHost@wipultra793' \
    --to=hemanthv@ti.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    /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