From: trblinux@gmail.com (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: Problems booting exynos5420 with >1 CPU
Date: Fri, 06 Jun 2014 10:08:12 +0530 [thread overview]
Message-ID: <539145B4.5000200@gmail.com> (raw)
In-Reply-To: <CAD=FV=UX90hgyojW3k_kpT=mt8eX9=AyHr+AGjhK=MrE1hHbUA@mail.gmail.com>
On 06/06/2014 06:38 AM, Doug Anderson wrote:
> Hi,
>
> When I try to boot linuxnext on my exynos5420-peach-pit chromebook I
> have problems bringing up extra CPUs:
>
> 1. They don't come up
>
[ ... ]
> [ 1.125030] CPU1: failed to boot: -38
> [ 2.130043] CPU2: failed to boot: -38
> [ 3.135059] CPU3: failed to boot: -38
>
With following config modifications over exynos_defconfig, I can see 4
big cores coming up.
CONFIG_MCPM=y
CONFIG_EXYNOS5420_MCPM=y
[ 0.030919] Exynos MCPM support installed
[ 0.060233] CPU1: Booted secondary processor
[ 0.090006] CPU1: update cpu_power 1535
[ 0.090010] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.100234] CPU2: Booted secondary processor
[ 0.130007] CPU2: update cpu_power 1535
[ 0.130011] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.140233] CPU3: Booted secondary processor
[ 0.170008] CPU3: update cpu_power 1535
[ 0.170012] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
--
Tushar Behera
next prev parent reply other threads:[~2014-06-06 4:38 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 [this message]
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
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=539145B4.5000200@gmail.com \
--to=trblinux@gmail.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).