From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Inderpal Singh <inderpal.singh@linaro.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Inderpal Singh <inderpal.s@samsung.com>,
kgene.kim@samsung.com, samsung@lists.linaro.org,
patches@linaro.org
Subject: Re: [PATCH] ARM: EXYNOS4: Fix secondary CPU boot after wake-up
Date: Tue, 31 May 2011 10:30:52 +0530 [thread overview]
Message-ID: <4DE47604.6070405@ti.com> (raw)
In-Reply-To: <20110530215404.GB21382@n2100.arm.linux.org.uk>
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 to fade away, to be replaced with
> something a little saner (eg, SGI0 being the first SGI). That just
> means you'll end up with a warning about SGI0 instead. Let's just
> ignore them for the time being (but please change to SGI0 anyway.)
I mean SGIO. SGI1 was typo. Ignoring that warning isn't good idea.
Platforms which do aggressive CPU offline/online, will keep
getting this noise and hence need to be fixed.
How about my patch which was marking this as a wakeup
IPI instead of unknown one. Ofcourse with wakeup SGI
being used will be SGI0 instead of current SGI1.
If you are ok with it I can send an RFC patch ?
Regards
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: EXYNOS4: Fix secondary CPU boot after wake-up
Date: Tue, 31 May 2011 10:30:52 +0530 [thread overview]
Message-ID: <4DE47604.6070405@ti.com> (raw)
In-Reply-To: <20110530215404.GB21382@n2100.arm.linux.org.uk>
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 to fade away, to be replaced with
> something a little saner (eg, SGI0 being the first SGI). That just
> means you'll end up with a warning about SGI0 instead. Let's just
> ignore them for the time being (but please change to SGI0 anyway.)
I mean SGIO. SGI1 was typo. Ignoring that warning isn't good idea.
Platforms which do aggressive CPU offline/online, will keep
getting this noise and hence need to be fixed.
How about my patch which was marking this as a wakeup
IPI instead of unknown one. Ofcourse with wakeup SGI
being used will be SGI0 instead of current SGI1.
If you are ok with it I can send an RFC patch ?
Regards
Santosh
next prev parent reply other threads:[~2011-05-31 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 9:13 [PATCH] ARM: EXYNOS4: Fix secondary CPU boot after wake-up Inderpal Singh
2011-05-30 9:13 ` Inderpal Singh
2011-05-30 9:38 ` Santosh Shilimkar
2011-05-30 9:38 ` Santosh Shilimkar
2011-05-30 21:54 ` Russell King - ARM Linux
2011-05-30 21:54 ` Russell King - ARM Linux
2011-05-31 5:00 ` Santosh Shilimkar [this message]
2011-05-31 5:00 ` Santosh Shilimkar
-- strict thread matches above, loose matches on Subject: below --
2011-06-21 5:33 Inderpal Singh
2011-06-21 5:33 ` Inderpal Singh
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=4DE47604.6070405@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=inderpal.s@samsung.com \
--cc=inderpal.singh@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.org \
--cc=samsung@lists.linaro.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.