From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: cpuidle: don't initialize big.LITTLE driver if MCPM is unavailable
Date: Fri, 09 Jan 2015 10:28:31 +0530 [thread overview]
Message-ID: <54AF5FF7.5080308@arm.com> (raw)
In-Reply-To: <7hh9w1vwzr.fsf@deeprootsystems.com>
Hi Kevin,
On Friday 09 January 2015 01:57 AM, Kevin Hilman wrote:
> Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> writes:
>
>> On Thu, Jan 08, 2015 at 11:11:40AM +0000, Daniel Lezcano wrote:
>>
[...]
>> 3) Sudeep's patch is not hiding anything. If CCI is in DT, CCI is
>> probed so mcpm_is_available() == true. If the firmware is borked
>> the idle states will be entered and we will notice there is
>> something wrong
>>
>> So overall I think Sudeep's patch is sound. I also think we should
>> improve the way we detect if MCPM is available, and again, I think
>> the CPU operations on arm64 are a good example that we can and we
>> should replicate.
>
> This patch disables CPUidle all together, but shouldn't it just
> disable the states that rely on MCPM? IOW, C1 should still work just
> fine since it doesn't use MCPM, right? So, rather than fail the
> init, it should just drop any MCPM states (e.g. set ->state_count =
> 1)
>
As Daniel pointed out, if there's no cpuidle driver or if cpuidle fails
to choose a convenient idle state, we fall back to the default arch idle
method(arch_cpu_idle)
Regards,
Sudeep
next prev parent reply other threads:[~2015-01-09 4:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 6:29 [PATCH] drivers: cpuidle: don't initialize big.LITTLE driver if MCPM is unavailable Sudeep Holla
2015-01-08 8:53 ` Daniel Lezcano
2015-01-08 9:16 ` Sudeep Holla
2015-01-08 10:02 ` Daniel Lezcano
2015-01-08 10:31 ` Sudeep Holla
2015-01-08 11:11 ` Daniel Lezcano
2015-01-08 12:29 ` Lorenzo Pieralisi
2015-01-08 14:01 ` Daniel Lezcano
2015-01-08 14:46 ` Lorenzo Pieralisi
2015-01-08 20:27 ` Kevin Hilman
2015-01-08 20:51 ` Daniel Lezcano
2015-01-09 17:34 ` Kevin Hilman
2015-01-09 4:58 ` Sudeep Holla [this message]
2015-01-09 5:01 ` Sudeep Holla
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=54AF5FF7.5080308@arm.com \
--to=sudeep.holla@arm.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).