From: Taras Kondratiuk <taras.kondratiuk@linaro.org>
To: Tony Lindgren <tony@atomide.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: OMAP4460: cpuidle: Extend PM_OMAP4_ROM_SMP_BOOT_ERRATUM_GICD on cpuidle
Date: Fri, 15 Nov 2013 18:02:13 +0200 [thread overview]
Message-ID: <52864585.6030206@linaro.org> (raw)
In-Reply-To: <20131115153608.GX10317@atomide.com>
On 11/15/2013 05:36 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [131114 10:36]:
>> * Grygorii Strashko <grygorii.strashko@ti.com> [131022 12:09]:
>>> The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
>>> "ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC ..."
>>> need to be applied not only when system is booting, but when MPUSS hits
>>> OSWR state through CPUIdle too. Without this WA the same issue is
>>> reproduced now on boards PandaES and Tablet/Blaze with SOM OMAP4460
>>> when CONFIG_CPU_IDLE is enabled.
>>> After MPUSS has enterred OSWR and waken up:
>>> - GIC distributor became disabled forever
>>> - scheduling is not performed any more
>>>
>>> Cc: Kevin Hilman <khilman@linaro.org>
>>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> Reported-by: Taras Kondratiuk <taras.kondratiuk@linaro.org>
>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Applying into omap-for-v3.13/fixes thanks.
>
> Hmm looks like this breaks the build with randconfigs at least
> with the attached .config, so dropping for now.
Hi Tony
Have you forgot to attach .config?
> arch/arm/mach-omap2/built-in.o: In function `omap_enter_idle_coupled':
> :(.text+0xb48c): undefined reference to `pm44xx_errata'
I assume that .config doesn't have CONFIG_SMP enabled while
pm44xx_errata is defined in omap-smp.c.
I think it should be a separate patch to move pm44xx_errata somewhere
else, so this patch will remain the same.
Btw, do we need omap_enter_idle_coupled() in UP?
--
Taras Kondratiuk
WARNING: multiple messages have this Message-ID (diff)
From: taras.kondratiuk@linaro.org (Taras Kondratiuk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: OMAP4460: cpuidle: Extend PM_OMAP4_ROM_SMP_BOOT_ERRATUM_GICD on cpuidle
Date: Fri, 15 Nov 2013 18:02:13 +0200 [thread overview]
Message-ID: <52864585.6030206@linaro.org> (raw)
In-Reply-To: <20131115153608.GX10317@atomide.com>
On 11/15/2013 05:36 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [131114 10:36]:
>> * Grygorii Strashko <grygorii.strashko@ti.com> [131022 12:09]:
>>> The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
>>> "ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC ..."
>>> need to be applied not only when system is booting, but when MPUSS hits
>>> OSWR state through CPUIdle too. Without this WA the same issue is
>>> reproduced now on boards PandaES and Tablet/Blaze with SOM OMAP4460
>>> when CONFIG_CPU_IDLE is enabled.
>>> After MPUSS has enterred OSWR and waken up:
>>> - GIC distributor became disabled forever
>>> - scheduling is not performed any more
>>>
>>> Cc: Kevin Hilman <khilman@linaro.org>
>>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> Reported-by: Taras Kondratiuk <taras.kondratiuk@linaro.org>
>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Applying into omap-for-v3.13/fixes thanks.
>
> Hmm looks like this breaks the build with randconfigs at least
> with the attached .config, so dropping for now.
Hi Tony
Have you forgot to attach .config?
> arch/arm/mach-omap2/built-in.o: In function `omap_enter_idle_coupled':
> :(.text+0xb48c): undefined reference to `pm44xx_errata'
I assume that .config doesn't have CONFIG_SMP enabled while
pm44xx_errata is defined in omap-smp.c.
I think it should be a separate patch to move pm44xx_errata somewhere
else, so this patch will remain the same.
Btw, do we need omap_enter_idle_coupled() in UP?
--
Taras Kondratiuk
next prev parent reply other threads:[~2013-11-15 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1382467484-16957-1-git-send-email-grygorii.strashko@ti.com>
2013-10-22 19:07 ` [PATCH v2] ARM: OMAP4460: cpuidle: Extend PM_OMAP4_ROM_SMP_BOOT_ERRATUM_GICD on cpuidle Grygorii Strashko
2013-10-22 19:07 ` Grygorii Strashko
2013-11-14 18:35 ` Tony Lindgren
2013-11-14 18:35 ` Tony Lindgren
2013-11-15 15:36 ` Tony Lindgren
2013-11-15 15:36 ` Tony Lindgren
2013-11-15 16:02 ` Taras Kondratiuk [this message]
2013-11-15 16:02 ` Taras Kondratiuk
2013-11-15 16:11 ` Tony Lindgren
2013-11-15 16:11 ` Tony Lindgren
2013-11-15 16:12 ` Santosh Shilimkar
2013-11-15 16:12 ` Santosh Shilimkar
2014-01-14 21:26 ` Kevin Hilman
2014-01-14 21:26 ` Kevin Hilman
2014-01-14 23:28 ` Santosh Shilimkar
2014-01-14 23:28 ` Santosh Shilimkar
2014-01-14 23:28 ` Santosh Shilimkar
2014-01-20 20:06 ` [PATCH] ARM: OMAP4+: move errata initialization to omap4_pm_init_early Nishanth Menon
2014-01-20 20:06 ` Nishanth Menon
2014-01-23 15:48 ` Grygorii Strashko
2014-01-23 15:48 ` Grygorii Strashko
2014-01-23 17:53 ` Kevin Hilman
2014-01-23 17:53 ` Kevin Hilman
2014-01-23 18:49 ` Tony Lindgren
2014-01-23 18:49 ` Tony Lindgren
2014-01-27 20:30 ` Kevin Hilman
2014-01-27 20:30 ` Kevin Hilman
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=52864585.6030206@linaro.org \
--to=taras.kondratiuk@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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 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.