79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
59 lines
1,021 B
C
59 lines
1,021 B
C
/* Copyright (c) 2022 Intel Corporation
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
#include <zephyr/kernel.h>
|
|
|
|
void arch_timing_init(void)
|
|
{
|
|
}
|
|
|
|
void arch_timing_start(void)
|
|
{
|
|
}
|
|
|
|
void arch_timing_stop(void)
|
|
{
|
|
}
|
|
|
|
uint64_t arch_timing_freq_get(void)
|
|
{
|
|
return CONFIG_XTENSA_CCOUNT_HZ;
|
|
}
|
|
|
|
timing_t arch_timing_counter_get(void)
|
|
{
|
|
uint32_t ccount;
|
|
|
|
__asm__ volatile ("rsr %0, CCOUNT" : "=r"(ccount));
|
|
|
|
return ccount;
|
|
}
|
|
|
|
uint64_t arch_timing_cycles_get(volatile timing_t *const start,
|
|
volatile timing_t *const end)
|
|
{
|
|
int64_t dt = (int64_t) (*end - *start);
|
|
|
|
if (dt < 0) {
|
|
dt += 0x100000000ULL;
|
|
}
|
|
|
|
return (uint64_t) dt;
|
|
}
|
|
|
|
uint64_t arch_timing_cycles_to_ns(uint64_t cycles)
|
|
{
|
|
return cycles * 1000000000ULL / CONFIG_XTENSA_CCOUNT_HZ;
|
|
}
|
|
|
|
uint64_t arch_timing_cycles_to_ns_avg(uint64_t cycles, uint32_t count)
|
|
{
|
|
/* Why is this an arch API? This is just math! */
|
|
return arch_timing_cycles_to_ns(cycles) / (uint64_t) count;
|
|
}
|
|
|
|
uint32_t arch_timing_freq_get_mhz(void)
|
|
{
|
|
return arch_timing_freq_get() / 1000000ULL;
|
|
}
|