From: khilman@kernel•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa
Date: Mon, 01 Dec 2014 10:50:29 -0800 [thread overview]
Message-ID: <7hbnnn5hmy.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1417186209-5256-2-git-send-email-a.kesavan@samsung.com> (Abhilash Kesavan's message of "Fri, 28 Nov 2014 20:20:09 +0530")
Abhilash Kesavan <a.kesavan@samsung•com> writes:
> The arndale-octa board was giving "imprecise external aborts" during
> boot-up with MCPM enabled. CCI enablement of the boot cluster was found
> to be the cause of these aborts (possibly because the secure f/w was not
> allowing it). Hence, disable CCI for the arndale-octa board.
>
> Signed-off-by: Abhilash Kesavan <a.kesavan@samsung•com>
Tested-by: Kevin Hilman <khilman@linaro•org>
Tested on top of next-20141128 with exynos_defconfig on my Octa board
and I'm not seeing the imprecise aborts anymore.
Thanks,
Kevin
next prev parent reply other threads:[~2014-12-01 18:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 14:50 [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-11-28 14:50 ` [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa Abhilash Kesavan
2014-11-28 15:19 ` Krzysztof Kozlowski
2014-11-28 15:39 ` Abhilash Kesavan
2014-12-01 9:03 ` Krzysztof Kozlowski
2014-12-01 11:09 ` Russell King - ARM Linux
2014-12-01 11:19 ` Krzysztof Kozlowski
2014-12-01 18:50 ` Kevin Hilman [this message]
2014-12-01 19:52 ` Tyler Baker
2014-12-10 4:01 ` [PATCH RFT 1/2] drivers: bus: check cci device tree node status Abhilash Kesavan
2014-12-10 4:14 ` Sudeep Holla
2014-12-10 4:25 ` Abhilash Kesavan
2014-12-10 5:16 ` Sudeep Holla
2015-01-08 6:45 ` Sudeep Holla
2015-01-08 15:27 ` Abhilash Kesavan
2015-01-09 5:10 ` Sudeep Holla
2015-01-09 16:28 ` Abhilash Kesavan
2015-01-09 21:09 ` Kevin Hilman
2015-01-10 3:21 ` Abhilash Kesavan
2014-12-10 18:29 ` Nicolas Pitre
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=7hbnnn5hmy.fsf@deeprootsystems.com \
--to=khilman@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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