All of lore.kernel.org
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm: psci: implement cpuidle_ops
Date: Thu, 2 Jul 2015 16:18:20 +0800	[thread overview]
Message-ID: <20150702161820.15dc9770@xhacker> (raw)
In-Reply-To: <5594F12F.6050401@linaro.org>

Dear Daniel,

On Thu, 2 Jul 2015 10:07:11 +0200
Daniel Lezcano <daniel.lezcano@linaro.org> wrote:

> On 07/02/2015 05:10 AM, Jisheng Zhang wrote:
> > Hi all,
> >
> > we'd like to use cpuidle-arm.c for both arm and arm64 with psci as backend. For
> > arm64, it works. But for arm, we miss cpuidle_ops. I want to add cpuidle_ops for
> > arm psci, I dunno whether this is the correct direction, could you please give
> > suggestions?
> 
> You should look at the macro
> 
> arch/arm/include/asm/cpuidle.h:
> 
> #define CPUIDLE_METHOD_OF_DECLARE(name, _method, _ops)

Yep, this is what I want to use. I want to use this MACRO to implement cpuidle_ops
for arm, but I dunno whether this is the correct direction. And I'd like to
reuse cpu_psci_cpu_init_idle() function in arch/arm64/kernel/psci.c to parse
the DT, but I'm not sure where to put cpu_psci_cpu_init_idle() so that can
be shared between arm and arm64. Also I noticed that there's a psci unification
work from Mark Rutland, does it make sense to put it in drivers/firmware/psci.c?

Thanks a lot,
Jisheng

  parent reply	other threads:[~2015-07-02  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  3:10 [RFC] arm: psci: implement cpuidle_ops Jisheng Zhang
2015-07-02  8:07 ` Daniel Lezcano
2015-07-02  8:16   ` Daniel Lezcano
2015-07-02  8:21     ` Jisheng Zhang
2015-07-02  8:18   ` Jisheng Zhang [this message]
2015-07-02 15:32     ` Mark Rutland
2015-07-07 11:03       ` Lorenzo Pieralisi

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=20150702161820.15dc9770@xhacker \
    --to=jszhang@marvell.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 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.