public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* rfc - use clk api to handle timers?
@ 2006-04-04 13:30 Woodruff, Richard
  2006-04-07 13:24 ` tony
  0 siblings, 1 reply; 2+ messages in thread
From: Woodruff, Richard @ 2006-04-04 13:30 UTC (permalink / raw)
  To: linux-omap-open-source

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?

Regards,
Richard W.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: rfc - use clk api to handle timers?
  2006-04-04 13:30 rfc - use clk api to handle timers? Woodruff, Richard
@ 2006-04-07 13:24 ` tony
  0 siblings, 0 replies; 2+ messages in thread
From: tony @ 2006-04-07 13:24 UTC (permalink / raw)
  To: Woodruff, Richard; +Cc: linux-omap-open-source

* Woodruff, Richard <r-woodruff2@ti.com> [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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-04-07 13:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-04 13:30 rfc - use clk api to handle timers? Woodruff, Richard
2006-04-07 13:24 ` tony

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox