Hi
On 07/12/2017 08:55 AM, Phil Edworthy wrote:
Hi,
I'm new to rt-linux, so please forgive me if I ask some dumb questions.
I have searched for a while, but not found what I am looking for.
I'm trying out the rt-linux patches (v4.9.35) on an out-of-tree BSP for
a new ARM Cortex A7 device. When I tried cyclictest, it complained that
I don't have High Resolution timers, so I checked and sure enough
/proc/timer_list showed the timer resolution is 10ms. I've checked my
kernel config and I have enabled hrtimers.
This device uses the ARM architected timer (CONFIG_ARM_ARCH_TIMER)
running at a lowly 6.25MHz.
So, how can I tell if a driver is supposed to support hrtimers?
If the ARM architected timer driver does support hrtimers, what could
stop them being used?
Most probably you do not have at least one tick_broadcast timer enabled.
See:
tick_check_oneshot_change()->tick_is_oneshot_available()
Alternative option for me was:
disable CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
--
regards,
-grygorii
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
