From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 1 Jul 2015 10:42:07 +0200 (CEST) From: Paul Osmialowski To: Thomas Gleixner cc: Paul Osmialowski , Greg Kroah-Hartman , Ian Campbell , Jiri Slaby , Kumar Gala , Linus Walleij , Mark Rutland , Michael Turquette , Pawel Moll , Rob Herring , Russell King , Stephen Boyd , Vinod Koul , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-serial@vger.kernel.org, devicetree@vger.kernel.org, dmaengine@vger.kernel.org, Arnd Bergmann , Geert Uytterhoeven , Nicolas Pitre , Paul Bolle , Uwe Kleine-Koenig , Anson Huang , Frank Li , Jingchang Lu , Rob Herring , Yuri Tikhonov , Sergei Poselenov , Alexander Potashev Subject: Re: [PATCH v2 4/9] arm: twr-k70f120m: timer driver for Kinetis SoC In-Reply-To: Message-ID: References: <1435667250-28299-1-git-send-email-pawelo@king.net.pl> <1435667250-28299-5-git-send-email-pawelo@king.net.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: Hi Thomas, On Wed, 1 Jul 2015, Thomas Gleixner wrote: >> + clockevents_register_device( >> + &kinetis_clockevent_tmrs[chan].evtdev); >> + >> + kinetis_pit_init(&kinetis_clockevent_tmrs[chan], >> + (rate / HZ) - 1); >> + kinetis_pit_enable(&kinetis_clockevent_tmrs[chan], 1); > > No point doing this. The core code has invoked the set_periodic call > back via clockevents_register_device() already. > As I removed this kinetis_pit_enable() line, the timer did not start, therefore the system became unusable. What could be possible reason for that?