From: tony@atomide.com
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: rfc - use clk api to handle timers?
Date: Fri, 7 Apr 2006 06:24:26 -0700 [thread overview]
Message-ID: <20060407132424.GE21950@atomide.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A5051197B4@dlee02.ent.ti.com>
* 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
prev parent reply other threads:[~2006-04-07 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 13:30 rfc - use clk api to handle timers? Woodruff, Richard
2006-04-07 13:24 ` tony [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060407132424.GE21950@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.