Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: a.kesavan@samsung.com
Cc: CHANDER KASHYAP <k.chander@samsung.com>,
	Mauro Ribeiro <mdrjr0@gmail.com>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>
Subject: Re: exynos5422-odroid-xu3: MCPM: only 6 of 8 CPUs coming online
Date: Thu, 09 Oct 2014 14:58:18 -0700	[thread overview]
Message-ID: <7hzjd4lxc5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <7133556.456161412823997169.JavaMail.weblogic@epml02> (Abhilash Kesavan's message of "Thu, 09 Oct 2014 03:06:38 +0000 (GMT)")

Hi Abhilash,

Abhilash Kesavan <a.kesavan@samsung.com> writes:

> I had noticed a similar issue where only 6 cores would come up during
> development on 5420. This was because there was a check in our u-boot
> secondary boot-up path which would put a core into WFI if a flag was
> not present and hence fail to boot. I wonder if it is the same
> situation in your case too.
> Is the u-boot for odroid-xu3 publically available or can you check if there is any such code present in your secondary bring-up path.

I'm using the hardkernel u-boot[1], branch: odroidxu3-v2012.07.  I'm
currently using the pre-built binaries that are in the
sd_fuse/hardkernel directory of that branch, but I can rebuild u-boot if
needed.

I'm not very familiar with u-boot, but if f you have some pointers where
to start looking in that code, that would be helpful.

Kevin

[1] https://github.com/hardkernel/u-boot.git

  reply	other threads:[~2014-10-09 21:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09  3:06 exynos5422-odroid-xu3: MCPM: only 6 of 8 CPUs coming online Abhilash Kesavan
2014-10-09 21:58 ` Kevin Hilman [this message]
2014-10-15 11:35   ` Joonyoung Shim
2014-10-17 12:06     ` Kevin Hilman
2014-10-23  1:04       ` Joonyoung Shim
2014-10-23  1:17         ` Joonyoung Shim
2014-10-23  1:25           ` Mauro Ribeiro
2014-10-23  1:36             ` Joonyoung Shim
2014-10-23  1:42               ` Mauro Ribeiro
2014-10-23  1:49                 ` Joonyoung Shim
2014-10-23  1:54                   ` Joonyoung Shim
2014-10-23  8:36                     ` Abhijeet Dev
     [not found]                     ` <CAG30XQJ29cM6=OFh=TTbR2rfWGt3AK1o2=PMqdoq6ejUJtUwGA@mail.gmail.com>
     [not found]                       ` <A804D1798D614199AFA7AEDC00248EA9@sisodomain.com>
2014-10-23 15:56                         ` Kevin Hilman
2014-10-24 14:33                           ` Abhilash Kesavan
2014-10-24 16:00                             ` Kevin Hilman
2014-10-25 12:47                               ` Mauro Ribeiro
2014-10-27 19:00                                 ` Kevin Hilman
2014-10-23 18:01           ` Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2014-10-08 18:58 Kevin Hilman

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=7hzjd4lxc5.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=a.kesavan@samsung.com \
    --cc=k.chander@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mdrjr0@gmail.com \
    /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