From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP4460: cpuidle: Workaround for ROM bug because of CA9 r2pX GIC control register change
Date: Thu, 17 Oct 2013 12:23:53 +0300 [thread overview]
Message-ID: <525FACA9.3060405@ti.com> (raw)
In-Reply-To: <1382000776-15897-1-git-send-email-grygorii.strashko@ti.com>
The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
"ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register change."
need to be applied not only when system is booting, but when
MPU hits OSWR state through CPUIdle too.
Now the same issue is reproduced on boards PandaES and Tablet/Blaze with
SOM OMAP4460 ES1.0 when CONFIG_CPU_IDLE is enabled.
- GIC distributor is disabled
- scheduling is not performed any more
Grygorii Strashko (2):
Revert "ARM: OMAP4+: CPUidle: Deprecate use of omap4_mpuss_read_prev_context_state()"
ARM: OMAP4460: cpuidle: WA for ROM bug because of CA9 r2pX gic control register change
arch/arm/mach-omap2/common.h | 6 +++++
arch/arm/mach-omap2/cpuidle44xx.c | 35 +++++++++++++++++++++++++++--
arch/arm/mach-omap2/omap-mpuss-lowpower.c | 14 ++++++++++++
arch/arm/mach-omap2/omap4-common.c | 6 +++++
4 files changed, 59 insertions(+), 2 deletions(-)
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@linaro.org>
Regards,
-grygorii
--
1.7.9.5
next parent reply other threads:[~2013-10-17 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1382000776-15897-1-git-send-email-grygorii.strashko@ti.com>
2013-10-17 9:23 ` Grygorii Strashko [this message]
2013-10-17 9:28 ` [PATCH 0/2] OMAP4460: cpuidle: Workaround for ROM bug because of CA9 r2pX GIC control register change Grygorii Strashko
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=525FACA9.3060405@ti.com \
--to=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).