From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Abhilash Kesavan <kesavan.abhilash@gmail.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@kernel.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
punit.agrawal@arm.com, Will Deacon <will.deacon@arm.com>,
"mark.rutland" <mark.rutland@arm.com>,
Kukjin Kim <kgene@kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Olof Johansson <olof@lixom.net>,
Kukjin Kim <kgene.kim@samsung.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH RFT 2/2] arm: dts: disable CCI on exynos420 based arndale-octa
Date: Mon, 01 Dec 2014 10:03:28 +0100 [thread overview]
Message-ID: <1417424608.4055.24.camel@AMDC1943> (raw)
In-Reply-To: <CAM4voa=aN53CWjTzw-A736xZo3xWr2N4kBpM0vJX5KqfV-ikjQ@mail.gmail.com>
On pią, 2014-11-28 at 21:09 +0530, Abhilash Kesavan wrote:
> Hello Krzysztof,
>
> On Fri, Nov 28, 2014 at 8:49 PM, Krzysztof Kozlowski
> <k.kozlowski@samsung.com> wrote:
> > On pią, 2014-11-28 at 20:20 +0530, Abhilash Kesavan wrote:
> >> 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>
> >> ---
> >> arch/arm/boot/dts/exynos5420-arndale-octa.dts | 4 ++++
> >> arch/arm/boot/dts/exynos5420.dtsi | 2 +-
> >> 2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > I tested these 2 patches on Arndale Octa but there are no improvements.
> > I still got imprecise aborts (some not fatal and sometimes killing init
> > with full backtrace).
>
> Thanks for testing. Are you testing this with exynos_defconfig with no
> other changes ? Can you please confirm from the bootlog that MCPM and
> CCI are not being initialized.
>
That was exynos_defconfig with disabled DRM and enabled some debug,
next-20141128.
When I tried only exynos_defconfig (with disabled DRM) it worked fine...
So the imprecise aborts were caused by one of following debug options:
DEBUG_SECTION_MISMATCH
DYNAMIC_DEBUG
DEBUG_ATOMIC_SLEEP
DEBUG_PREEMPT
PROVE_LOCKING
LOCKUP_DETECTOR
DEBUG_LOCK_ALLOC
PROVE_RCU
DEBUG_RT_MUTEXES
DEBUG_MUTEXES
DEBUG_SPINLOCK
DEBUG_LIST
DEBUG_PAGEALLOC
SPARSE_RCU_POINTER
DEBUG_FS
PM_DEBUG
PM_ADVANCED_DEBUG
GPIO_SYSFS
> Can you remove these 2 patches and on linux-next check if you are
> getting aborts even with 5420_MCPM disabled.
I tried this already and imprecise aborts shown, however with my
debugging options above.
Overall the patches seems to work properly (although the debugging issue
needs to be resolved still), so:
On Arndale Octa (Exynos 5420):
Tested-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
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:03:28 +0100 [thread overview]
Message-ID: <1417424608.4055.24.camel@AMDC1943> (raw)
In-Reply-To: <CAM4voa=aN53CWjTzw-A736xZo3xWr2N4kBpM0vJX5KqfV-ikjQ@mail.gmail.com>
On pi?, 2014-11-28 at 21:09 +0530, Abhilash Kesavan wrote:
> Hello Krzysztof,
>
> On Fri, Nov 28, 2014 at 8:49 PM, Krzysztof Kozlowski
> <k.kozlowski@samsung.com> wrote:
> > On pi?, 2014-11-28 at 20:20 +0530, Abhilash Kesavan wrote:
> >> 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>
> >> ---
> >> arch/arm/boot/dts/exynos5420-arndale-octa.dts | 4 ++++
> >> arch/arm/boot/dts/exynos5420.dtsi | 2 +-
> >> 2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > I tested these 2 patches on Arndale Octa but there are no improvements.
> > I still got imprecise aborts (some not fatal and sometimes killing init
> > with full backtrace).
>
> Thanks for testing. Are you testing this with exynos_defconfig with no
> other changes ? Can you please confirm from the bootlog that MCPM and
> CCI are not being initialized.
>
That was exynos_defconfig with disabled DRM and enabled some debug,
next-20141128.
When I tried only exynos_defconfig (with disabled DRM) it worked fine...
So the imprecise aborts were caused by one of following debug options:
DEBUG_SECTION_MISMATCH
DYNAMIC_DEBUG
DEBUG_ATOMIC_SLEEP
DEBUG_PREEMPT
PROVE_LOCKING
LOCKUP_DETECTOR
DEBUG_LOCK_ALLOC
PROVE_RCU
DEBUG_RT_MUTEXES
DEBUG_MUTEXES
DEBUG_SPINLOCK
DEBUG_LIST
DEBUG_PAGEALLOC
SPARSE_RCU_POINTER
DEBUG_FS
PM_DEBUG
PM_ADVANCED_DEBUG
GPIO_SYSFS
> Can you remove these 2 patches and on linux-next check if you are
> getting aborts even with 5420_MCPM disabled.
I tried this already and imprecise aborts shown, however with my
debugging options above.
Overall the patches seems to work properly (although the debugging issue
needs to be resolved still), so:
On Arndale Octa (Exynos 5420):
Tested-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2014-12-01 9:03 UTC|newest]
Thread overview: 40+ 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 ` 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 14:50 ` Abhilash Kesavan
2014-11-28 15:19 ` Krzysztof Kozlowski
2014-11-28 15:19 ` Krzysztof Kozlowski
2014-11-28 15:39 ` Abhilash Kesavan
2014-11-28 15:39 ` Abhilash Kesavan
2014-12-01 9:03 ` Krzysztof Kozlowski [this message]
2014-12-01 9:03 ` Krzysztof Kozlowski
2014-12-01 11:09 ` Russell King - ARM Linux
2014-12-01 11:09 ` Russell King - ARM Linux
2014-12-01 11:19 ` Krzysztof Kozlowski
2014-12-01 11:19 ` Krzysztof Kozlowski
2014-12-01 18:50 ` Kevin Hilman
2014-12-01 18:50 ` Kevin Hilman
2014-12-01 19:52 ` Tyler Baker
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:01 ` Abhilash Kesavan
2014-12-10 4:14 ` Sudeep Holla
2014-12-10 4:14 ` Sudeep Holla
2014-12-10 4:25 ` Abhilash Kesavan
2014-12-10 4:25 ` Abhilash Kesavan
2014-12-10 5:16 ` Sudeep Holla
2014-12-10 5:16 ` Sudeep Holla
2015-01-08 6:45 ` Sudeep Holla
2015-01-08 6:45 ` Sudeep Holla
2015-01-08 15:27 ` Abhilash Kesavan
2015-01-08 15:27 ` Abhilash Kesavan
2015-01-09 5:10 ` Sudeep Holla
2015-01-09 5:10 ` Sudeep Holla
2015-01-09 16:28 ` Abhilash Kesavan
2015-01-09 16:28 ` Abhilash Kesavan
2015-01-09 21:09 ` Kevin Hilman
2015-01-09 21:09 ` Kevin Hilman
2015-01-10 3:21 ` Abhilash Kesavan
2015-01-10 3:21 ` Abhilash Kesavan
2014-12-10 18:29 ` Nicolas Pitre
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=1417424608.4055.24.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=javier.martinez@collabora.co.uk \
--cc=kesavan.abhilash@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.