From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: Problems booting exynos5420 with >1 CPU
Date: Fri, 6 Jun 2014 17:48:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406061740280.25775@knanqh.ubzr> (raw)
In-Reply-To: <CAM4voaknx3+X4O8MUwaruUFPyquY8Opq61ucKX08xTrv8PqfLg@mail.gmail.com>
On Fri, 6 Jun 2014, Abhilash Kesavan wrote:
> Hi Doug,
>
> The first change in the kernel (clearing an iRAM location) is needed
> because of an unnecessary change that we are carrying in the Chrome
> U-boot. There is no reason for us to have the workaround in the
> mainline kernel. Rather, we should remove the check from our u-boot.
> However AFAIR a clean-up patch that I had posted internally was not
> accepted as we had frozen the SPL at the time.
>
> The second change is to enable snoops for boot cluster. Internally, we
> were disabling the snoops for both the clusters at power off and
> enabling it in power_up_setup and power_up. However, I dropped the
> approach due to problems pointed out by Nicolas here
> http://www.spinics.net/lists/arm-kernel/msg324091.html related to
> cpuidle. Hence, we turn it on at the u-boot.
You should never *ever* play with the CCI from U-Boot. That's for the
MCPM layer to decide when it is safe to do so. That's mainly the
_whole_ reason why MCPM exists in the first place.
Nicolas
next prev parent reply other threads:[~2014-06-06 21:48 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:08 Problems booting exynos5420 with >1 CPU Doug Anderson
2014-06-06 4:38 ` Tushar Behera
2014-06-06 17:17 ` Doug Anderson
2014-06-06 17:36 ` Abhilash Kesavan
2014-06-06 18:02 ` Doug Anderson
2014-06-06 18:12 ` Abhilash Kesavan
2014-06-06 18:20 ` Doug Anderson
2014-06-06 18:31 ` Abhilash Kesavan
2014-06-06 18:56 ` Doug Anderson
2014-06-06 19:09 ` Abhilash Kesavan
2014-06-06 19:12 ` Abhilash Kesavan
2014-06-06 20:49 ` Doug Anderson
2014-06-06 21:01 ` Russell King - ARM Linux
2014-06-06 21:12 ` Doug Anderson
2014-06-06 21:44 ` Doug Anderson
2014-06-06 20:37 ` Olof Johansson
2014-06-06 20:46 ` Abhilash Kesavan
2014-06-06 21:01 ` Olof Johansson
2014-06-06 21:06 ` Abhilash Kesavan
2014-06-06 21:34 ` Nicolas Pitre
2014-06-06 21:49 ` Olof Johansson
2014-06-06 21:59 ` Doug Anderson
2014-06-06 22:38 ` Nicolas Pitre
2014-06-06 23:03 ` Doug Anderson
2014-06-06 22:17 ` Nicolas Pitre
2014-06-06 21:48 ` Nicolas Pitre [this message]
2014-06-07 3:25 ` Abhilash Kesavan
2014-06-07 16:10 ` Nicolas Pitre
2014-06-07 17:56 ` Lorenzo Pieralisi
2014-06-07 20:06 ` Nicolas Pitre
2014-06-07 22:36 ` Lorenzo Pieralisi
2014-06-07 23:53 ` Olof Johansson
2014-06-08 0:19 ` Russell King - ARM Linux
2014-06-08 2:52 ` Olof Johansson
2014-06-08 18:26 ` Nicolas Pitre
2014-06-08 18:29 ` Russell King - ARM Linux
2014-06-08 18:55 ` Nicolas Pitre
2014-06-08 19:02 ` Russell King - ARM Linux
2014-06-08 12:45 ` Lorenzo Pieralisi
2014-06-08 14:34 ` Russell King - ARM Linux
2014-06-08 17:53 ` Nicolas Pitre
2014-06-09 20:47 ` Kevin Hilman
2014-06-09 22:26 ` Lorenzo Pieralisi
2014-06-10 4:25 ` Nicolas Pitre
2014-06-10 9:19 ` Lorenzo Pieralisi
2014-06-10 14:14 ` Catalin Marinas
2014-06-10 16:49 ` Nicolas Pitre
2014-06-10 17:42 ` Catalin Marinas
2014-06-10 19:15 ` Nicolas Pitre
2014-06-09 20:27 ` Kevin Hilman
2014-06-09 20:35 ` Doug Anderson
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=alpine.LFD.2.11.1406061740280.25775@knanqh.ubzr \
--to=nicolas.pitre@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).