linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable
Date: Fri, 31 Oct 2014 15:59:41 -0700	[thread overview]
Message-ID: <1414796382-5447-1-git-send-email-khilman@kernel.org> (raw)

From: Kevin Hilman <khilman@linaro.org>

The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
during boot testing, causing various userspace startup failures.

Disable until it has gotten more testing.

Cc: Kukjin Kim <kgene.kim@samsung.com>,
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Cc: Sachin Kamat <sachin.kamat@samsung.com>,
Cc: Doug Anderson <dianders@chromium.org>,
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Cc: Tushar Behera <tushar.behera@linaro.org>,
Cc: stable at vger.kernel.org # v3.17+
Signed-off-by: Kevin Hilman <khilman@linaro.org>
---
This has been reported by a few people[1], but not investigated or fixed, so it's
time to disable this feature until it can be fixed.

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/288344.html

 arch/arm/configs/exynos_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
index 72058b8a6f4d..a250dcbf34cd 100644
--- a/arch/arm/configs/exynos_defconfig
+++ b/arch/arm/configs/exynos_defconfig
@@ -10,7 +10,7 @@ CONFIG_MODULE_UNLOAD=y
 CONFIG_PARTITION_ADVANCED=y
 CONFIG_ARCH_EXYNOS=y
 CONFIG_ARCH_EXYNOS3=y
-CONFIG_EXYNOS5420_MCPM=y
+CONFIG_EXYNOS5420_MCPM=n
 CONFIG_SMP=y
 CONFIG_BIG_LITTLE=y
 CONFIG_BL_SWITCHER=y
-- 
2.1.0

             reply	other threads:[~2014-10-31 22:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 22:59 Kevin Hilman [this message]
2014-11-08  9:50 ` [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable Kukjin Kim
2014-11-10 19:35   ` Kevin Hilman
2014-11-24 19:51     ` Kevin Hilman
2014-11-25  0:25       ` Olof Johansson
2014-11-25  1:35         ` Kevin Hilman
2014-11-25  1:37           ` Olof Johansson
2014-11-25  1:38             ` Olof Johansson
2014-11-25  1:50               ` Kukjin Kim
2014-11-25  3:20                 ` Kevin Hilman
2014-11-25  6:01                   ` Abhilash Kesavan
2014-11-26  1:00                     ` Kevin Hilman
2014-11-26 16:58                       ` Abhilash Kesavan
2014-11-26 17:56                         ` Kevin Hilman
2014-11-26 18:11                           ` Kukjin Kim
2014-11-26 18:41                           ` Nicolas Pitre
2014-11-27 16:51                             ` Abhilash Kesavan
2014-11-27 17:06                               ` Nicolas Pitre
2014-11-28 14:41                                 ` Abhilash Kesavan
2014-11-27 18:57                             ` Sudeep Holla
2014-11-25  8:47                   ` Krzysztof Kozlowski
2014-11-25  9:07                     ` Krzysztof Kozlowski
2014-11-25  2:13             ` 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=1414796382-5447-1-git-send-email-khilman@kernel.org \
    --to=khilman@kernel.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).