Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753482AbbGQV4l (ORCPT ); Fri, 17 Jul 2015 17:56:41 -0400 Received: from mail-wg0-f43.google.com ([74.125.82.43]:32943 "EHLO mail-wg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752002AbbGQV4j (ORCPT ); Fri, 17 Jul 2015 17:56:39 -0400 From: Matthias Brugger To: Yingjoe Chen Cc: Thomas Gleixner , Stephen Boyd , Michael Turquette , James Liao , Russell King , devicetree@vger.kernel.org, Arnd Bergmann , Catalin Marinas , Daniel Lezcano , linux-kernel@vger.kernel.org, Rob Herring , linux-mediatek@lists.infradead.org, Sascha Hauer , Olof Johansson , srv_heupstream@mediatek.com, linux-arm-kernel@lists.infradead.org, Daniel Kurtz , linux-clk@vger.kernel.org Subject: Re: [PATCH 1/5] clocksource: mediatek: do not enable GPT_CLK_EVT when setup Date: Fri, 17 Jul 2015 23:56:35 +0200 Message-ID: <287437450.ZlyYtovZRG@ubix> User-Agent: KMail/4.13.3 (Linux/3.13.0-57-generic; KDE/4.13.3; x86_64; ; ) In-Reply-To: <1436779969-18610-2-git-send-email-yingjoe.chen@mediatek.com> References: <1436779969-18610-1-git-send-email-yingjoe.chen@mediatek.com> <1436779969-18610-2-git-send-email-yingjoe.chen@mediatek.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 709 Lines: 16 On Monday, July 13, 2015 05:32:45 PM Yingjoe Chen wrote: > Spurious mtk timer interrupt is noticed at boot and cause kernel > crash. It seems if GPT is enabled, it will latch irq status even > when its IRQ is disabled. When irq is enabled afterward, we see > spurious interrupt. > Change init flow to only enable GPT_CLK_SRC at mtk_timer_init. > > Signed-off-by: Yingjoe Chen > --- Acked-by: Matthias Brugger -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/