Lines Matching refs:may

6 drivers/clocksource in the kernel tree, but the code may be spread out
32 may stop during system suspend.
55 Since this operation may be invoked very often, doing this in a strict
92 and register range may be used for the clock event, but it is essentially
112 number of nanoseconds since the system was started. An architecture may or
113 may not provide an implementation of sched_clock() on its own. If a local
124 between accuracy compared to the clock source, you may sacrifice accuracy
128 The sched_clock() function may wrap only on unsigned long long boundaries,
137 The clock driving sched_clock() may stop or reset to zero during system
139 events on the system. However it may result in interesting timestamps in
145 Some architectures may have a limited set of time sources and lack a nice
173 Enter timer-based delays. Using these, a timer read may be used instead of