All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
Cc: linux-omap@vger.kernel.org, rnayak@ti.com, jouni.hogander@nokia.com
Subject: Re: [PATCH 0/3] Update CPU idle parameter passing
Date: Wed, 11 Nov 2009 16:28:10 -0800	[thread overview]
Message-ID: <87k4xwwpr9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1256805020-7402-1-git-send-email-kalle.jokiniemi@digia.com> (Kalle Jokiniemi's message of "Thu\, 29 Oct 2009 10\:30\:17 +0200")

Kalle Jokiniemi <kalle.jokiniemi@digia.com> writes:

> Hi Kevin,
>
> Made some patches to enable setting RX-51 cpu idle parameters
> as we use them. Added "valid" field passing to cpuidle_params
> in the process.
>
> Tested on RX-51. Applies on top of linux-omap/pm branch.
>
> Kalle Jokiniemi (3):
>       OMAP:PM: Fix non-cpu idle builds using omap3_pm_init_cpuidle
>       OMAP3: Add valid field into C-state parameter passing
>       OMAP: RX-51: Pass cpu idle parameters

Thanks, applying this series to PM branch.

Kevin

> kajokini@ubuntu:~/work/linux-open/linux-omap$ git diff --stat HEAD~3..HEAD
>  arch/arm/mach-omap2/board-3430sdp.c |   14 ++++++------
>  arch/arm/mach-omap2/board-rx51.c    |   18 +++++++++++++++++
>  arch/arm/mach-omap2/cpuidle34xx.c   |   37 +++++++++++++++++++++-------------
>  arch/arm/mach-omap2/pm.h            |    8 +++++++
>  4 files changed, 56 insertions(+), 21 deletions(-)

      parent reply	other threads:[~2009-11-12  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  8:30 [PATCH 0/3] Update CPU idle parameter passing Kalle Jokiniemi
2009-10-29  8:30 ` [PATCH 1/3] OMAP:PM: Fix non-cpu idle builds using omap3_pm_init_cpuidle Kalle Jokiniemi
2009-10-29  8:30   ` [PATCH 2/3] OMAP3: Add valid field into C-state parameter passing Kalle Jokiniemi
2009-10-29  8:30     ` [PATCH 3/3] OMAP: RX-51: Pass cpu idle parameters Kalle Jokiniemi
2009-11-12  0:28 ` Kevin Hilman [this message]

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=87k4xwwpr9.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=jouni.hogander@nokia.com \
    --cc=kalle.jokiniemi@digia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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.