linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: cpuidle: don't initialize big.LITTLE driver if MCPM is unavailable
Date: Thu, 08 Jan 2015 11:02:54 +0100	[thread overview]
Message-ID: <54AE55CE.6040201@linaro.org> (raw)
In-Reply-To: <54AE4ADF.3030307@arm.com>

On 01/08/2015 10:16 AM, Sudeep Holla wrote:
> Hi Daniel,
>
> On Thursday 08 January 2015 02:23 PM, Daniel Lezcano wrote:
>> On 01/08/2015 07:29 AM, Sudeep Holla wrote:
>>> If big.LITTLE driver is initialized even when MCPM is unavailable,
>>> we get the below warning the first time cpu tries to enter deeper
>>> C-states.
>>
>> Can you elaborate why MCPM could be unavailable when the tc2 pm code
>> registers the mcpm platform ops before the cpuidle driver ?
>>
>>
> I can think of 3 possible scenarios. Let me know if these make sense.
>
> 1. If the firmware settings in Vexpress configuration files are set to
>     boot in legacy mode, but MCPM is enabled in the kernel.

If I am not wrong, we have a BUG_ON in this path, right ?

> 2. If some failure occurs during MCPM initialization
> 3. For example, if CCI is not accessible as in some Exynos boards [1],
>     we don't want to wait till mpcm_cpu_suspend ?

Well, I think if the firmware is preventing us to play with the CCI but 
MCPM is enabled. We should add BUG_ON also in the same initialization 
path. IIRC, Kevin spent some time to figure out what was happening to 
its odroid-xu3 board before understanding mcpm wasn't able to deal with 
the CCI due to the broken firmware.

The patch you are proposing is valid. Nevertheless, I would really like 
to have the firmwares to be fixed and your patch is hiding an 
incompatible firmware with the kernel configuration and letting the 
kernel continue to work in degraded mode.

IMO, it would be better to be more strict with the mcpm initialization 
and not let the system boot if something is wrong with it which I 
believe is coming from the firmware and let the user to figure out what 
is really happening by letting him to disable mcpm in the kernel 
configuration (which in turn will disable cpuidle).

Nico, Kevin, what is your opinion ?



> [1]
> https://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg39624.html



-- 
  <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-01-08 10:02 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 [this message]
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
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=54AE55CE.6040201@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).