From: Kevin Hilman <khilman@kernel.org>
To: Przemyslaw Marczak <p.marczak@samsung.com>
Cc: "Amit Kucheria" <amit.kucheria@linaro.org>,
"Krzysztof Kozłowski" <k.kozlowski.k@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"Bartłomiej Żołnierkiewicz" <b.zolnierkie@samsung.com>,
"Andrew Bresticker" <abrestic@chromium.org>,
"Mauro Ribeiro" <mauro.ribeiro@hardkernel.com>,
"Doug Anderson" <dianders@chromium.org>,
"Abhilash Kesavan" <a.kesavan@samsung.com>,
"Lists linaro-kernel" <linaro-kernel@lists.linaro.org>,
"Kukjin Kim" <kgene@kernel.org>,
"Olof Johansson" <olof@lixom.net>,
"Lists LAKML" <linux-arm-kernel@lists.infradead.org>,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422?
Date: Mon, 15 Jun 2015 11:58:26 -0700 [thread overview]
Message-ID: <7hoakg4x4d.fsf@deeprootsystems.com> (raw)
In-Reply-To: <557ECBAE.20302@samsung.com> (Przemyslaw Marczak's message of "Mon, 15 Jun 2015 14:57:18 +0200")
Przemyslaw Marczak <p.marczak@samsung.com> writes:
> On 06/15/2015 01:19 PM, Amit Kucheria wrote:
>> On Mon, Jun 15, 2015 at 3:49 PM, Przemyslaw Marczak
>> <p.marczak@samsung.com> wrote:
>>> Hello Krzysztof,
>>>
>>>
>>> On 06/14/2015 10:56 AM, Krzysztof Kozłowski wrote:
>>
>> <snip>
>>
>>> I'm trying port the hardkernel's SPL to the mainline U-Boot at present. The
>>> mainline SPL is implemented for E5420 and E5800. But there are few
>>> differences:
>>> - different DRAM
>>> - different clocks
>>> - different boot core (peach-pi boots from A15)
>>> - bl2 signature
>>> - hdk's SPL uses smc calls
>>> ... and some more.
>>
>> This is really good news! Would this work leave CCI control to Linux
>> so that we may use MCPM to manage cpu and cluster OFF?
>>
>
> Yes, I would like to get this stuff working.
>
Do you have access to BL1 sources to change this?
IIUC, what is happening is BL1 is leaving CCI in secure mode, which
means the kernel MCPM cannot manage it. That means the kernel cannot
manage any low-power CPU or cluster states.
Does anyone know at which stage of the boot secure world is left for
normal world? in BL1? in BL2?
If it's in BL2, maybe the CCI issue can also be fixed by ensuring that
CCI is not left in secure mode so the kernel can properly manage CCI.
Kevin
next prev parent reply other threads:[~2015-06-15 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 6:21 [RFC] ARM: exynos: MCPM: [is this a] fix for secondary boot on 5422? Kevin Hilman
2014-11-26 9:35 ` Heesub Shin
2014-11-26 16:00 ` Kevin Hilman
2015-06-14 8:56 ` Krzysztof Kozłowski
2015-06-15 10:07 ` Bartlomiej Zolnierkiewicz
2015-06-15 10:19 ` Przemyslaw Marczak
2015-06-15 11:19 ` Amit Kucheria
2015-06-15 12:57 ` Przemyslaw Marczak
2015-06-15 18:58 ` Kevin Hilman [this message]
2015-06-15 12:17 ` Krzysztof Kozłowski
2015-06-15 14:00 ` Przemyslaw Marczak
2015-06-15 18:53 ` 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=7hoakg4x4d.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=a.kesavan@samsung.com \
--cc=abrestic@chromium.org \
--cc=amit.kucheria@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mauro.ribeiro@hardkernel.com \
--cc=olof@lixom.net \
--cc=p.marczak@samsung.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