Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Mauro Ribeiro <mdrjr0@gmail.com>
Cc: Abhilash Kesavan <kesavan.abhilash@gmail.com>,
	Abhijeet Dev <abhijeet@abhijeet-dev.net>,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	Chander Kashyap <k.chander@samsung.com>,
	Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: exynos5422-odroid-xu3: MCPM: only 6 of 8 CPUs coming online
Date: Mon, 27 Oct 2014 12:00:28 -0700	[thread overview]
Message-ID: <7hwq7ll4mr.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAGc3s_dEk6S82JgSbueML8_68-hdEKhLrY1G0k+kcg+YJ77JmQ@mail.gmail.com> (Mauro Ribeiro's message of "Sat, 25 Oct 2014 10:47:05 -0200")

Mauro Ribeiro <mdrjr0@gmail.com> writes:

> As I wrote you previously outside the list this is the commit "ARM:
> EXYNOS: SWRESET is needed to boot secondary CPU on exynos3250" that I
> was expecting it to fix XU3 as well and apparently it is..

I'm not sure about that, since I haven't been able to get that to work.

> Next week if everything goes as I plan I'll check if I can use the
> same code to enable the A7's on XU3 as well.
> If its possible to use the same code I'll try to upstream this next week.

Excellent.  I'd love to see a patch against mainline that using that
function that works on the XU3.  Note that mainline is using MCPM and
that patch solves the problem for the older platsmp method.

> It would be nice if Samsung could tell what in our u-boot (provided by
> LSI) is needed to be changed as I can just push any changes to our
> u-boot.

Yes, I completely agree.  This seems to me like a bootloader bug and the
best solution here would be to have a bootloader fix.

Kevin

  reply	other threads:[~2014-10-27 19:00 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
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 [this message]
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=7hwq7ll4mr.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=abhijeet@abhijeet-dev.net \
    --cc=jy0922.shim@samsung.com \
    --cc=k.chander@samsung.com \
    --cc=kesavan.abhilash@gmail.com \
    --cc=kgene.kim@samsung.com \
    --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