timestamp: add tick frequency to exported table
Add the timestamp tick frequency within the timestamp table so the cbmem utility doesn't try to figure it out on its own. Those paths still exist for x86 systems which don't provide tsc_freq_mhz(). All other non-x86 systems use the monotonic timer which has a 1us granularity or 1MHz. One of the main reasons is that Linux is reporting /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq as the true turbo frequency on turbo enables machines. This change also fixes the p-state values honored in cpufreq for turbo machines in that turbo p-pstates were reported as 100MHz greater than nominal. BUG=chrome-os-partner:44669 BRANCH=firmware-strago-7287.B TEST=Built and booted on glados. Confirmed table frequency honored. Change-Id: I763fe2d9a7b01d0ef5556e5abff36032062f5801 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11470 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
@ -278,6 +278,10 @@ static void timestamp_sync_cache_to_cbmem(int is_recovery)
|
||||
if (ts_cbmem_table->base_time == 0)
|
||||
ts_cbmem_table->base_time = ts_cache_table->base_time;
|
||||
|
||||
/* Seed the timestamp tick frequency in ramstage. */
|
||||
if (ENV_RAMSTAGE)
|
||||
ts_cbmem_table->tick_freq_mhz = timestamp_tick_freq_mhz();
|
||||
|
||||
/* Cache no longer required. */
|
||||
ts_cache_table->num_entries = 0;
|
||||
ts_cache->cache_state = TIMESTAMP_CACHE_NOT_NEEDED;
|
||||
@ -299,3 +303,9 @@ uint64_t __attribute__((weak)) timestamp_get(void)
|
||||
|
||||
return mono_time_diff_microseconds(&t1, &t2);
|
||||
}
|
||||
|
||||
/* Like timestamp_get() above this matches up with microsecond granularity. */
|
||||
int __attribute__((weak)) timestamp_tick_freq_mhz(void)
|
||||
{
|
||||
return 1;
|
||||
}
|
||||
|
Reference in New Issue
Block a user