From ff00dbecce32aba0433a3c182f5e18727395f85a Mon Sep 17 00:00:00 2001 From: Dan Kalowsky Date: Thu, 16 Apr 2015 12:25:10 -0700 Subject: [PATCH] Renaming intLatencyInit with int_latency_init 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 --- kernel/nanokernel/core/int_latency_bench.c | 6 +++--- make/target/kconfig/modules/monitor.kconf | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/kernel/nanokernel/core/int_latency_bench.c b/kernel/nanokernel/core/int_latency_bench.c index a4347331d75..74e72025755 100644 --- a/kernel/nanokernel/core/int_latency_bench.c +++ b/kernel/nanokernel/core/int_latency_bench.c @@ -151,13 +151,13 @@ void _int_latency_stop(void) /******************************************************************************* * -* intLatencyInit - initialize interrupt latency benchmark +* int_latency_init - initialize interrupt latency benchmark * * RETURNS: N/A * */ -void intLatencyInit(void) +void int_latency_init(void) { uint32_t timeToReadTime; uint32_t cacheWarming = NB_CACHE_WARMING_DRY_RUN; @@ -215,7 +215,7 @@ void intLatencyShow(void) uint32_t intHandlerLatency = 0; if (!intLatencyBenchRdy) { - printk("error: intLatencyInit() has not been invoked\n"); + printk("error: int_latency_init() has not been invoked\n"); return; } diff --git a/make/target/kconfig/modules/monitor.kconf b/make/target/kconfig/modules/monitor.kconf index 720fdbd5ed4..c81746c4398 100644 --- a/make/target/kconfig/modules/monitor.kconf +++ b/make/target/kconfig/modules/monitor.kconf @@ -112,7 +112,7 @@ config INT_LATENCY_BENCHMARK This option enables the tracking of interrupt latency metrics; 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) each time intLatencyShow() is called thereafter.