From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start
Date: Mon, 16 Jun 2014 11:37:28 -0700 [thread overview]
Message-ID: <CAD=FV=XYBSkx_3jzZ2G=WuEYweiejna7KionneqUkEVPx3_E-w@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1406091649290.25775@knanqh.ubzr>
Nicolas,
On Mon, Jun 9, 2014 at 1:55 PM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> On Mon, 9 Jun 2014, Kevin Hilman wrote:
>
>> On Mon, Jun 9, 2014 at 1:22 PM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
>> > On Mon, 9 Jun 2014, Andrew Bresticker wrote:
>> >
>> >> > [1] While waiting for the forth-coming patch from Andrew to enable the
>> >> > CCI port for the boot cluster), I do this from u-boot before starting
>> >> > the kernel (based on earlier email from Doug):
>> >> >
>> >> > mw.l 10d25000 3 # Enable CCI from U-Boot
>> >>
>> >> From the other thread, it sounds like Nicolas wants enabling of the
>> >> boot cluster's CCI port to be done unconditionally for all MCPM
>> >> platforms. Nicolas, are you preparing a patch for this or should I?
>> >
>> > I would like confirmation this indeed solves your problem first before I
>> > go ahead with it.
>>
>> FYI... I confirmed on the other thread. It works on the Chromebook2.
>
> OK I'll clean it up for mainline.
I just wanted to double-check that this is still on your list of
things to do. If not then please let us know! :)
-Doug
next prev parent reply other threads:[~2014-06-16 18:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 21:43 [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start Doug Anderson
2014-06-06 22:35 ` Nicolas Pitre
2014-06-06 22:43 ` Doug Anderson
2014-06-06 22:46 ` Andrew Bresticker
2014-06-06 23:14 ` [PATCH v2] " Doug Anderson
2014-06-07 1:34 ` Nicolas Pitre
2014-06-09 18:09 ` Kevin Hilman
2014-06-09 20:05 ` Andrew Bresticker
2014-06-09 20:22 ` Nicolas Pitre
2014-06-09 20:35 ` Kevin Hilman
2014-06-09 20:55 ` Nicolas Pitre
2014-06-16 18:37 ` Doug Anderson [this message]
2014-06-16 18:47 ` Nicolas Pitre
2014-06-07 18:12 ` [PATCH] " Lorenzo Pieralisi
2014-06-09 17:03 ` Doug Anderson
2014-06-09 22:38 ` Lorenzo Pieralisi
2014-06-10 8:12 ` Chander Kashyap
2014-06-10 15:21 ` Doug Anderson
2014-06-10 15:49 ` Nicolas Pitre
2014-06-11 4:52 ` Chander Kashyap
2014-06-11 10:13 ` Lorenzo Pieralisi
2014-06-11 12:14 ` Chander Kashyap
2014-06-11 13:15 ` Lorenzo Pieralisi
2014-06-11 13:29 ` Chander Kashyap
2014-06-11 13:34 ` Abhilash Kesavan
2014-06-11 15:19 ` Doug Anderson
2014-06-11 15:28 ` Kukjin Kim
2014-06-13 11:54 ` Chander Kashyap
2014-06-13 13:29 ` Nicolas Pitre
2014-06-13 15:10 ` Doug Anderson
2014-06-16 7:40 ` Chander Kashyap
2014-06-16 18: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='CAD=FV=XYBSkx_3jzZ2G=WuEYweiejna7KionneqUkEVPx3_E-w@mail.gmail.com' \
--to=dianders@chromium.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).