michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Renaming intLatencyInit with int_latency_init

Browse source 
Updating nano kernel functions to follow a consistent naming convention.
Part of that process is the removal of camelCase naming conventions for the
preferred_underscore_method.

Change accomplished with the following script:

#!/bin/bash
echo "Searching for ${1} to replace with ${2}"
find . -type f \( -iname \*.c -o -iname \*.h -o -iname \*.s \) \
       -not \( -path host/src/genIdt -prune \) \   \
       -not \( -path host/src/gen_tables -prune \) \
       -print | xargs sed -i "s/"${1}"/"${2}"/g"

Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com>
This commit is contained in:
Dan Kalowsky 2015-04-16 12:25:10 -07:00 • committed by Anas Nashif
commit ff00dbecce
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
kernel/nanokernel/core/int_latency_bench.c
View file

@ -151,13 +151,13 @@ void _int_latency_stop(void)
/******************************************************************************* /*******************************************************************************
* *
* intLatencyInit - initialize interrupt latency benchmark * int_latency_init - initialize interrupt latency benchmark
* *
* RETURNS: N/A * RETURNS: N/A
* *
*/ */
void intLatencyInit(void) void int_latency_init(void)
{ {
uint32_t timeToReadTime; uint32_t timeToReadTime;
uint32_t cacheWarming = NB_CACHE_WARMING_DRY_RUN; uint32_t cacheWarming = NB_CACHE_WARMING_DRY_RUN;
@ -215,7 +215,7 @@ void intLatencyShow(void)
uint32_t intHandlerLatency = 0; uint32_t intHandlerLatency = 0;
if (!intLatencyBenchRdy) { if (!intLatencyBenchRdy) {
printk("error: intLatencyInit() has not been invoked\n"); printk("error: int_latency_init() has not been invoked\n");
return; return;
} }

2
make/target/kconfig/modules/monitor.kconf
View file

@ -112,7 +112,7 @@ config INT_LATENCY_BENCHMARK
This option enables the tracking of interrupt latency metrics; This option enables the tracking of interrupt latency metrics;
the exact set of metrics being tracked is BSP-dependent. the exact set of metrics being tracked is BSP-dependent.
Tracking begins when intLatencyInit() is invoked by an application. Tracking begins when int_latency_init() is invoked by an application.
The metrics are displayed (and a new sampling interval is started) The metrics are displayed (and a new sampling interval is started)
each time intLatencyShow() is called thereafter. each time intLatencyShow() is called thereafter.