From: santosh.shilimkar@oracle.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Minimal cpuidle fixes for omap5 and dra7
Date: Wed, 26 Oct 2016 12:53:20 -0700 [thread overview]
Message-ID: <ecf2d8f9-c385-26db-7ffd-49026ecbc380@oracle.com> (raw)
In-Reply-To: <20161026151703.24730-1-tony@atomide.com>
On 10/26/2016 8:16 AM, Tony Lindgren wrote:
> Hi all,
>
> Here are some fixes to get minimal cpuidle support working with omap5
> and dra7. Not sure if there are still some unsorted issues on enabling
> this on dra7, but at least omap5 has been behving for me for few
> weeks with these.
>
> Regards,
>
> Tony
>
>
> Santosh Shilimkar (1):
> ARM: DRA7: PM: cpuidle MPU CSWR support
>
> Tony Lindgren (4):
> ARM: OMAP5: Fix build for PM code
> ARM: OMAP5: Fix mpuss_early_init
> ARM: OMAP4+: Fix bad fallthrough for cpuidle
> ARM: OMAP5: Enable minimal cpuidle for omap5 retention
>
Feel free to add my ack if you need one.
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
next prev parent reply other threads:[~2016-10-26 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:16 [PATCH 0/5] Minimal cpuidle fixes for omap5 and dra7 Tony Lindgren
2016-10-26 15:16 ` [PATCH 1/5] ARM: OMAP5: Fix build for PM code Tony Lindgren
2016-10-26 15:17 ` [PATCH 2/5] ARM: OMAP5: Fix mpuss_early_init Tony Lindgren
2016-10-26 20:21 ` Tony Lindgren
2016-10-26 15:17 ` [PATCH 3/5] ARM: OMAP4+: Fix bad fallthrough for cpuidle Tony Lindgren
2016-10-26 15:17 ` [PATCH 4/5] ARM: DRA7: PM: cpuidle MPU CSWR support Tony Lindgren
2016-10-27 16:15 ` Tony Lindgren
2016-10-26 15:17 ` [PATCH 5/5] ARM: OMAP5: Enable minimal cpuidle for omap5 retention Tony Lindgren
2016-10-26 19:53 ` Santosh Shilimkar [this message]
2016-10-26 20:56 ` [PATCH 0/5] Minimal cpuidle fixes for omap5 and dra7 Nishanth Menon
2016-10-26 21:31 ` Tony Lindgren
2016-10-27 7:43 ` H. Nikolaus Schaller
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=ecf2d8f9-c385-26db-7ffd-49026ecbc380@oracle.com \
--to=santosh.shilimkar@oracle.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).