-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"sys_clock_hw_cycles_per_tick" for hpet timer? #2574
Labels
area: Kernel
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
by Benjamin Walsh: The value in the kconfig option is overridden at runtime by the HPET, since it queries its hardware to get the real value. |
by Sharron LIU: It's clear. Agree to close. |
by Mark Linkmeyer: Fixing incorrect priority |
zephyrbot
added
priority: low
Low impact/importance bug
area: Kernel
bug
The issue is a bug, or the PR is fixing a bug
labels
Sep 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Kernel
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Reported by Sharron LIU:
I'm doing some testing on unified kernel, where "sys_clock_hw_cycles_per_tick" is not defined in the "include/kernel.h". Thus I tried to compute this value by doing:
#define CYCLES_PER_TICK (CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC/
CONFIG_SYS_CLOCK_TICKS_PER_SEC)
This comes out "250000", but the "sys_clock_hw_cycles_per_tick" used in qemu_x86 is actually "1000000". Is this as expected?
I noticed in the default configure of qemu_x86
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=25000000
CONFIG_SYS_CLOCK_TICKS_PER_SEC=100
and I would expect "sys_clock_hw_cycles_per_tick = 250000".
(Imported from Jira ZEP-1071)
The text was updated successfully, but these errors were encountered: