Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757502Ab1CAUln (ORCPT ); Tue, 1 Mar 2011 15:41:43 -0500 Received: from moutng.kundenserver.de ([212.227.126.171]:56566 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756459Ab1CAUll (ORCPT ); Tue, 1 Mar 2011 15:41:41 -0500 From: Arnd Bergmann To: "Russell King - ARM Linux" Subject: Re: [PATCH (sh-2.6) 1/4] clksource: Generic timer infrastructure Date: Tue, 1 Mar 2011 21:41:26 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.38-rc2+; KDE/4.5.1; x86_64; ; ) Cc: Stuart Menefy , Peppe CAVALLARO , "linux-sh@vger.kernel.org" , "netdev@vger.kernel.org" , John Stultz , Thomas Gleixner , "linux-kernel@vger.kernel.org" References: <1298369864-24429-1-git-send-email-peppe.cavallaro@st.com> <201103011743.19847.arnd@arndb.de> <20110301202611.GC27107@n2100.arm.linux.org.uk> In-Reply-To: <20110301202611.GC27107@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103012141.26679.arnd@arndb.de> X-Provags-ID: V02:K0:HtXwchXzi+xrPNmkczhJA8HqM3vjfwTsRTCztOF1Wot H2KqwF48+bG/D29gKIAD+hH1oSP9dLV6bMM7BxDfQYA3RYTRRT b/UeqN52HGzdt2kBeT5c7oUwND9DnQIPeH4JnNLJCSiCjN2uTK IAipN5OJSLkoeW2VxqasERGnlszUAXELaWPBAghC3yQj8GTEI+ B5tmYJRS42YvSBYGWRmZw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1484 Lines: 31 On Tuesday 01 March 2011 21:26:11 Russell King - ARM Linux wrote: > On Tue, Mar 01, 2011 at 05:43:19PM +0100, Arnd Bergmann wrote: > > On Tuesday 01 March 2011, Stuart Menefy wrote: > > > On 24/02/11 17:20, Arnd Bergmann wrote: > > > > Also, what is the difference between this and clkdev? > > > > > > clkdev can be used to find a struct clk, which is fine if you just want to > > > read the time. In this instance we want to get interrupts from the timer > > > hardware, which isn't supported by the clk infrastructure. > > > > (adding Russell to Cc) > > > > Is this something that could sensibly be added to clk/clkdev? > > I don't understand - why would anyone want to use clk/clkdev for timers. > clk/clkdev is all about those signals on the SoC which wiggle at regular > intervals between logic 0 and logic 1. It's not about things which count, > which seems to be an entirely separate problem, and hence why there's > nothing to deal with interrupts or setting timeouts etc. Ok, I see. I had mixed the two concepts. The clkdev infrastructure seemed like a nice way to connect a source and a consumer of a timer, but you're right that it's an entirely separate thing, and as Thomas said, it's probably not needed either. Arnd -- 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/