Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Abhilash Kesavan <a.kesavan@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org, nicolas.pitre@linaro.org,
	lorenzo.pieralisi@arm.com, punit.agrawal@arm.com,
	will.deacon@arm.com, mark.rutland@arm.com, kgene@kernel.org,
	linux-samsung-soc@vger.kernel.org, dianders@chromium.org,
	olof@lixom.net, kgene.kim@samsung.com,
	javier.martinez@collabora.co.uk, k.kozlowski@samsung.com,
	b.zolnierkie@samsung.com, kesavan.abhilash@gmail.com,
	arnd@arndb.de
Subject: Re: [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

  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.org \
    --cc=a.kesavan@samsung.com \
    --cc=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=dianders@chromium.org \
    --cc=javier.martinez@collabora.co.uk \
    --cc=k.kozlowski@samsung.com \
    --cc=kesavan.abhilash@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=olof@lixom.net \
    --cc=punit.agrawal@arm.com \
    --cc=will.deacon@arm.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