From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH (sh-2.6) 1/4] clksource: Generic timer infrastructure Date: Tue, 1 Mar 2011 20:26:11 +0000 Message-ID: <20110301202611.GC27107@n2100.arm.linux.org.uk> References: <1298369864-24429-1-git-send-email-peppe.cavallaro@st.com> <201102241820.55873.arnd@arndb.de> <4D6D0EA3.9000504@st.com> <201103011743.19847.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stuart Menefy , Peppe CAVALLARO , "linux-sh@vger.kernel.org" , "netdev@vger.kernel.org" , John Stultz , Thomas Gleixner , "linux-kernel@vger.kernel.org" To: Arnd Bergmann Return-path: Content-Disposition: inline In-Reply-To: <201103011743.19847.arnd@arndb.de> Sender: linux-sh-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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.