From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932950AbcL0RgC (ORCPT ); Tue, 27 Dec 2016 12:36:02 -0500 Received: from muru.com ([72.249.23.125]:53642 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932837AbcL0Rfx (ORCPT ); Tue, 27 Dec 2016 12:35:53 -0500 Date: Tue, 27 Dec 2016 09:35:49 -0800 From: Tony Lindgren To: Keerthy Cc: t-kristo@ti.com, linux@armlinux.org.uk, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Grygorii Strashko , Lokesh Vutla Subject: Re: [PATCH v2] ARM: omap2: am437x: rollback to use omap3_gptimer_timer_init() Message-ID: <20161227173549.GS4920@atomide.com> References: <1480910264-5126-1-git-send-email-j-keerthy@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1480910264-5126-1-git-send-email-j-keerthy@ti.com> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Keerthy [161204 19:58]: > From: Grygorii Strashko > > The commit 55ee7017ee31 ("arm: omap2: board-generic: use > omap4_local_timer_init for AM437x") unintentionally changes the > clocksource devices for AM437x from OMAP GP Timer to SyncTimer32K. > > Unfortunately, the SyncTimer32K is starving from frequency deviation > as mentioned in commit 5b5c01359152 ("ARM: OMAP2+: AM43x: Use gptimer > as clocksource") and, as reported by Franklin [1], even its monotonic > nature is under question (most probably there is a HW issue, but it's > still under investigation). > > Taking into account above facts It's reasonable to rollback to the use > of omap3_gptimer_timer_init(). > > [1] http://www.spinics.net/lists/linux-omap/msg127425.html Applying into omap-for-v4.10/fixes thanks. Tony