linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: keita kobayashi <keita.kobayashi.ym@renesas.com>
Cc: Lina Iyer <lina.iyer@linaro.org>,
	horms@verge.net.au, rjw@rjwysocki.net, linux-sh@vger.kernel.org,
	linux-pm@vger.kernel.org, magnus.damm@gmail.com
Subject: Re: [RFC/PATCH 0/6] Add CPUIdle support for Renesas SoCs
Date: Mon, 09 Mar 2015 16:32:26 +0100	[thread overview]
Message-ID: <54FDBD0A.5060001@linaro.org> (raw)
In-Reply-To: <20150309152155.GC456@linaro.org>

On 03/09/2015 04:21 PM, Lina Iyer wrote:
> On Fri, Mar 06 2015 at 02:38 -0700, keita kobayashi wrote:
>> Hi Daniel

[ ... ]

>>>
>>> Hi Keita,
>>>
>>> the platform approach to pass private data from the arch specific to
>>> the cpuidle driver no longer accepted. Unfortunately, there is no
>>> alternate solution upstream.
>>>
>>> But hopefully, there is a patchset [1] submitted for upstreaming
>>> which unify arm32/64 into a single generic cpuidle driver and use the
>>> DT to define the idle functions to be used.
>>>
>>> I suggest you have a look at this patchset if it can fit your need.
>>>
>>>   -- Daniel
>>>
>>> [1] https://lkml.org/lkml/2015/3/3/271
>>
>> Thank you for information.
>> I will take a look at the patch series.
>
> Hi Kieta,
>
> Please also have a look at the v15 of the cpuidle support for QCOM SoC.
> Sent just now.  It is based on [1].

Lina's patchset is available at:

https://www.mail-archive.com/devicetree@vger.kernel.org/msg64700.html

Thanks
   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2015-03-09 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  4:55 [RFC/PATCH 0/6] Add CPUIdle support for Renesas SoCs Keita Kobayashi
2015-03-04  4:55 ` [RFC/PATCH 1/6] cpuidle: renesas: Add CPUIdle Driver " Keita Kobayashi
2015-03-05 18:05   ` Daniel Lezcano
2015-03-04  4:55 ` [RFC/PATCH 2/6] ARM: shmobile: Change CPUIdle InterFace Keita Kobayashi
2015-03-04  4:55 ` [RFC/PATCH 3/6] ARM: shmobile: APMU: Add Core-Standby function for CPUIdle Keita Kobayashi
2015-03-04  4:55 ` [RFC/PATCH 4/6] ARM: shmobile: r8a7791: Add Core-Standby CPUIdle support for r8a7791 Keita Kobayashi
     [not found]   ` <CAKDJKT6vx8xhHtxCerXen0NqRao5d5hzZdj8LtSJ4hiMjhZXdA@mail.gmail.com>
2015-03-05  0:29     ` Simon Horman
2015-03-05  1:19       ` keita kobayashi
2015-03-05 18:11   ` Daniel Lezcano
2015-03-04  4:55 ` [RFC/PATCH 5/6] ARM: shmobile: r8a7790: Add Core-Standby CPUIdle support for r8a7790 Keita Kobayashi
2015-03-05 18:13   ` Daniel Lezcano
2015-03-04  4:55 ` [RFC/PATCH 6/6] ARM: shmobile: Enable Renesas CPUIdle for shmobile_defconfig Keita Kobayashi
2015-03-05 18:02 ` [RFC/PATCH 0/6] Add CPUIdle support for Renesas SoCs Daniel Lezcano
2015-03-06  9:38   ` keita kobayashi
2015-03-09 15:21     ` Lina Iyer
2015-03-09 15:32       ` Daniel Lezcano [this message]
2015-03-13  5:01         ` keita kobayashi

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=54FDBD0A.5060001@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=horms@verge.net.au \
    --cc=keita.kobayashi.ym@renesas.com \
    --cc=lina.iyer@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=rjw@rjwysocki.net \
    /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).