From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] OMAP4: CPUidle: Add coupled idle support
Date: Mon, 02 Apr 2012 22:04:43 -0700 [thread overview]
Message-ID: <87obr9s8wk.fsf@ti.com> (raw)
In-Reply-To: 1333114048-26136-1-git-send-email-santosh.shilimkar@ti.com
Hi Santosh,
Santosh Shilimkar <santosh.shilimkar@ti•com> writes:
> The series adds the coupled cpuidle support for OMAP4 based on the v2
> series posted [1]. This makes OMAP4 to support SMP cpuidle and also
> removes the hard dependency of off-lining CPU1 to trigger deeper
> C-states.
>
> I have put together a branch which is based on 3.3 kernel with
> Len Browns next branch [2] which has time keeping and other cpuidle
> patches which will mostly get merged by 3.4-rc1 and rebased coupled
> idle series from [1].
Thanks for rebasing this.
> git://gitorious.org/omap-sw-develoment/linux-omap-dev.git
> for_3.5/omap4_coupled_cpuidle-rebase
This branch by itself seems to work fine. However, when combining with
other stuff that has merged for v3.4, it hangs during boot. I haven't
yet isolated the problem, but it's easy to reproduce by combining your
branch with v3.4-rc1:
git checkout -b test/coupled-v3.4 v3.4-rc1
git merge -s recursive -X ours santosh/for_3.5/omap4_coupled_cpuidle-rebase [1]
This hangs on boot, and it seems like a coupled state deadlock because
commenting out the coupled states in the C-state creation of
cpuidle44xx.c makes it boot just fine.
Kevin
[1] There were a couple conflicts in your branch with ACPI stuff from
v3.4-rc1 (maybe Len updated his branch?), so I just threw them
away with a recursive/ours merge.
next prev parent reply other threads:[~2012-04-03 5:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:27 [PATCH 0/3] OMAP4: CPUidle: Add coupled idle support Santosh Shilimkar
2012-03-30 13:27 ` [PATCH 1/3] ARM: OMAP: timer: allow gp timer clock-event to be used on both cpus Santosh Shilimkar
2012-08-03 7:16 ` Daniel Mack
2012-08-03 7:21 ` Koen Kooi
2012-08-03 8:30 ` Koen Kooi
2012-08-03 9:27 ` Shilimkar, Santosh
2012-08-03 9:33 ` Koen Kooi
2012-08-03 9:42 ` Hiremath, Vaibhav
2012-08-03 9:48 ` Shilimkar, Santosh
2012-08-03 10:32 ` Hiremath, Vaibhav
2012-08-03 10:33 ` Shilimkar, Santosh
2012-08-03 10:04 ` Koen Kooi
2012-08-03 10:14 ` Shilimkar, Santosh
2012-08-03 10:34 ` Hiremath, Vaibhav
2012-08-07 6:50 ` Tony Lindgren
2012-08-03 10:23 ` Hiremath, Vaibhav
2012-08-03 8:22 ` Hiremath, Vaibhav
2012-03-30 13:27 ` [PATCH 2/3] ARM: OMAP4: cpuidle: Use coupled cpuidle states to implement SMP cpuidle Santosh Shilimkar
2012-03-30 19:43 ` Colin Cross
2012-03-31 6:37 ` Shilimkar, Santosh
2012-03-30 13:27 ` [PATCH 3/3] ARM: OMAP4: CPUidle: add synchronization for coupled idle states Santosh Shilimkar
2012-04-03 5:04 ` Kevin Hilman [this message]
2012-04-03 15:06 ` [PATCH 0/3] OMAP4: CPUidle: Add coupled idle support Santosh Shilimkar
2012-04-09 6:54 ` Santosh Shilimkar
2012-04-17 10:23 ` 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=87obr9s8wk.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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