From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: add the cpuidle driver for WFI and ARM retention
Date: Mon, 23 Apr 2012 11:17:29 +0200 [thread overview]
Message-ID: <4F951E29.6060009@linaro.org> (raw)
In-Reply-To: <4F950B85.2010505@stericsson.com>
On 04/23/2012 09:57 AM, Rickard Andersson wrote:
> Should not the driver be located in the 'drivers/cpuidle/' directory?
We had a discussion about moving the cpuidle drivers to this directory
but there are too much dependencies between the arch specific code and
the drivers and Russell thinks there is no real benefit of moving these
drivers out arch/arm.
http://www.spinics.net/lists/arm-kernel/msg155454.html
The discussion is at91 specific but as this work was part of moving the
drivers to the 'drivers' directory in general. I assumed the same rule
applied to the ux500 cpuidle driver.
The current driver has the WFI and the ApIdle states and could be moved
to drivers directory without complicating the dependencies but that
won't be consistent with the rest of the drivers location (not only ARM)
and I am not sure that will be still the case with the next states
'ApSleep' and 'ApDeepSleep'.
IMO we should put this driver in arch/arm/mach-ux500, and, in the
future, if we are able to move all the SoC cpuidle drivers to the
'drivers' directory then this driver will be moved too.
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
prev parent reply other threads:[~2012-04-23 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 12:46 [PATCH] ARM: ux500: add the cpuidle driver for WFI and ARM retention Daniel Lezcano
2012-04-23 5:52 ` Daniel Lezcano
2012-04-24 9:09 ` Linus Walleij
2012-04-24 12:46 ` Daniel Lezcano
2012-04-23 7:55 ` Vincent Guittot
2012-04-23 7:57 ` Rickard Andersson
2012-04-23 9:17 ` Daniel Lezcano [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=4F951E29.6060009@linaro.org \
--to=daniel.lezcano@linaro.org \
--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).