1. After wake-up, the system-wide flags register loses its value.
Hence, write the address of secondary startup function to
successfully boot the secondary CPU.
2. Changes SGI1 to SGI0 for secondary CPU boot up
Signed-off-by: Inderpal Singh inderpa...@samsung.com
---
1. The below patch is
1. After wake-up, the system-wide flags register loses its value.
Hence, write the address of secondary startup function to
successfully boot the secondary CPU.
2. Fix to remove the Unknown IPI message 0x1 message when
secondary CPU boots.
Signed-off-by: Inderpal Singh
On 5/30/2011 2:43 PM, Inderpal Singh wrote:
[...]
2. Fix to remove the Unknown IPI message 0x1 message when
secondary CPU boots.
For this one you are avoiding a wakeup IPI and rather
relying on schedule IPI. That just avoiding the issue.
This doesn't seems to be right. Refer below
On Mon, May 30, 2011 at 03:08:17PM +0530, Santosh Shilimkar wrote:
When do you plan to fix the SGI usage as discussed
in above thread. I thought SGI1 usage was ok for OMAP,
realview/versatile and MSM.
I'd like the use of the arbitary SGI1 to fade away, to be replaced with
something a little
On 5/31/2011 3:24 AM, Russell King - ARM Linux wrote:
On Mon, May 30, 2011 at 03:08:17PM +0530, Santosh Shilimkar wrote:
When do you plan to fix the SGI usage as discussed
in above thread. I thought SGI1 usage was ok for OMAP,
realview/versatile and MSM.
I'd like the use of the arbitary SGI1
