Thread (9 messages) flat view 9 messages, 2 authors, 2012-09-07
STALE5083d

[PATCH v2 2/2] ARM: delay: add registration mechanism for delay timer sources

From: Will Deacon <hidden>
Date: 2012-09-04 17:38:49

On Tue, Sep 04, 2012 at 06:11:51PM +0100, Stephen Boyd wrote:
On 09/04/12 03:44, Will Deacon wrote:
quoted
On Tue, Sep 04, 2012 at 11:07:50AM +0100, Will Deacon wrote:
quoted
On Fri, Aug 31, 2012 at 12:51:25AM +0100, Stephen Boyd wrote:
quoted
quoted
+void __init register_current_timer_delay(struct delay_timer *timer)
const?
Sure. I'll send an updated patch.
Gah, spoke too soon. This isn't going to work, as the frequency may not be
known until probe time (for example, it could be obtained by the device
tree) so const data isn't going to cut it.
That's fine. We can still do const can't we? I was suggesting you make
the argument const and not the data in arch_timer.c const. This way we
can be sure that delay.c isn't going to muck with the struct, but the
ones who register the struct can fill it in at runtime.
Aha, gotcha. I thought you wanted to enforce const-ness on the provider for
some reason.
Squash this in and test compile?
Works a treat.

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help