From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com Subject: Re: rfc - use clk api to handle timers? Date: Fri, 7 Apr 2006 06:24:26 -0700 Message-ID: <20060407132424.GE21950@atomide.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com Errors-To: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com To: "Woodruff, Richard" Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Woodruff, Richard [060404 06:32]: > I was just wondering if it might be useful to use the clk api to control > gp-timers? > > enable/disable map well. > set_parent maps to sys_clk, dpll clk, alt_clk. > get_rate/set_rate/round_rate work well. There is a well known > divider set to use round_rate against. > > One thing which might be nice is some kind of get_exclusive > which causes further gets from others to fail if a resource is already > owned. Normal usecount's would handle a shared resource. > > This doesn't cover interrupt generation and others those could be added > or handled separately. > > Thoughts? We should use gptimers via hrtimers. Using the clk api for internal rate control may work as long as we use rates. Tony