2017-12-21 14:14:19 +01:00
|
|
|
/*
|
2019-07-12 16:09:03 +02:00
|
|
|
* Copyright (c) 2017-2019 Oticon A/S
|
2017-12-21 14:14:19 +01:00
|
|
|
*
|
|
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
|
|
*/
|
|
|
|
|
|
|
|
/**
|
2023-12-05 17:14:05 +01:00
|
|
|
* Driver for the timer model of the POSIX native_sim/posix board
|
2017-12-21 14:14:19 +01:00
|
|
|
* It provides the interfaces required by the kernel and the sanity testcases
|
|
|
|
* It also provides a custom k_busy_wait() which can be used with the
|
|
|
|
* POSIX arch and InfClock SOC
|
|
|
|
*/
|
2023-09-14 11:07:22 +02:00
|
|
|
#include <zephyr/types.h>
|
2022-05-25 17:31:28 +02:00
|
|
|
#include <zephyr/irq.h>
|
2023-08-28 13:15:43 +02:00
|
|
|
#include <zephyr/init.h>
|
2022-05-06 10:25:46 +02:00
|
|
|
#include <zephyr/drivers/timer/system_timer.h>
|
2022-05-25 17:31:28 +02:00
|
|
|
#include <zephyr/sys_clock.h>
|
2017-12-21 14:14:19 +01:00
|
|
|
#include "timer_model.h"
|
|
|
|
#include "soc.h"
|
2022-05-06 10:25:46 +02:00
|
|
|
#include <zephyr/arch/posix/posix_trace.h>
|
2017-12-21 14:14:19 +01:00
|
|
|
|
2020-05-27 18:26:57 +02:00
|
|
|
static uint64_t tick_period; /* System tick period in microseconds */
|
2019-07-12 16:09:03 +02:00
|
|
|
/* Time (microseconds since boot) of the last timer tick interrupt */
|
2020-05-27 18:26:57 +02:00
|
|
|
static uint64_t last_tick_time;
|
2018-02-06 14:24:27 +01:00
|
|
|
|
2017-12-21 14:14:19 +01:00
|
|
|
/**
|
|
|
|
* Return the current HW cycle counter
|
|
|
|
* (number of microseconds since boot in 32bits)
|
|
|
|
*/
|
2021-03-12 18:46:52 +01:00
|
|
|
uint32_t sys_clock_cycle_get_32(void)
|
2017-12-21 14:14:19 +01:00
|
|
|
{
|
|
|
|
return hwm_get_time();
|
|
|
|
}
|
|
|
|
|
2021-10-30 02:10:35 +02:00
|
|
|
uint64_t sys_clock_cycle_get_64(void)
|
|
|
|
{
|
|
|
|
return hwm_get_time();
|
|
|
|
}
|
|
|
|
|
2018-02-08 12:46:13 +01:00
|
|
|
/**
|
|
|
|
* Interrupt handler for the timer interrupt
|
2019-07-12 16:09:03 +02:00
|
|
|
* Announce to the kernel that a number of ticks have passed
|
2018-02-08 12:46:13 +01:00
|
|
|
*/
|
isr: Normalize usage of device instance through ISR
The goal of this patch is to replace the 'void *' parameter by 'struct
device *' if they use such variable or just 'const void *' on all
relevant ISRs
This will avoid not-so-nice const qualifier tweaks when device instances
will be constant.
Note that only the ISR passed to IRQ_CONNECT are of interest here.
In order to do so, the script fix_isr.py below is necessary:
from pathlib import Path
import subprocess
import pickle
import mmap
import sys
import re
import os
cocci_template = """
@r_fix_isr_0
@
type ret_type;
identifier P;
identifier D;
@@
-ret_type <!fn!>(void *P)
+ret_type <!fn!>(const struct device *P)
{
...
(
const struct device *D = (const struct device *)P;
|
const struct device *D = P;
)
...
}
@r_fix_isr_1
@
type ret_type;
identifier P;
identifier D;
@@
-ret_type <!fn!>(void *P)
+ret_type <!fn!>(const struct device *P)
{
...
const struct device *D;
...
(
D = (const struct device *)P;
|
D = P;
)
...
}
@r_fix_isr_2
@
type ret_type;
identifier A;
@@
-ret_type <!fn!>(void *A)
+ret_type <!fn!>(const void *A)
{
...
}
@r_fix_isr_3
@
const struct device *D;
@@
-<!fn!>((void *)D);
+<!fn!>(D);
@r_fix_isr_4
@
type ret_type;
identifier D;
identifier P;
@@
-ret_type <!fn!>(const struct device *P)
+ret_type <!fn!>(const struct device *D)
{
...
(
-const struct device *D = (const struct device *)P;
|
-const struct device *D = P;
)
...
}
@r_fix_isr_5
@
type ret_type;
identifier D;
identifier P;
@@
-ret_type <!fn!>(const struct device *P)
+ret_type <!fn!>(const struct device *D)
{
...
-const struct device *D;
...
(
-D = (const struct device *)P;
|
-D = P;
)
...
}
"""
def find_isr(fn):
db = []
data = None
start = 0
try:
with open(fn, 'r+') as f:
data = str(mmap.mmap(f.fileno(), 0).read())
except Exception as e:
return db
while True:
isr = ""
irq = data.find('IRQ_CONNECT', start)
while irq > -1:
p = 1
arg = 1
p_o = data.find('(', irq)
if p_o < 0:
irq = -1
break;
pos = p_o + 1
while p > 0:
if data[pos] == ')':
p -= 1
elif data[pos] == '(':
p += 1
elif data[pos] == ',' and p == 1:
arg += 1
if arg == 3:
isr += data[pos]
pos += 1
isr = isr.strip(',\\n\\t ')
if isr not in db and len(isr) > 0:
db.append(isr)
start = pos
break
if irq < 0:
break
return db
def patch_isr(fn, isr_list):
if len(isr_list) <= 0:
return
for isr in isr_list:
tmplt = cocci_template.replace('<!fn!>', isr)
with open('/tmp/isr_fix.cocci', 'w') as f:
f.write(tmplt)
cmd = ['spatch', '--sp-file', '/tmp/isr_fix.cocci', '--in-place', fn]
subprocess.run(cmd)
def process_files(path):
if path.is_file() and path.suffix in ['.h', '.c']:
p = str(path.parent) + '/' + path.name
isr_list = find_isr(p)
patch_isr(p, isr_list)
elif path.is_dir():
for p in path.iterdir():
process_files(p)
if len(sys.argv) < 2:
print("You need to provide a dir/file path")
sys.exit(1)
process_files(Path(sys.argv[1]))
And is run: ./fix_isr.py <zephyr root directory>
Finally, some files needed manual fixes such.
Fixes #27399
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2020-06-17 14:58:56 +02:00
|
|
|
static void np_timer_isr(const void *arg)
|
2017-12-21 14:14:19 +01:00
|
|
|
{
|
|
|
|
ARG_UNUSED(arg);
|
2019-07-12 16:09:03 +02:00
|
|
|
|
2020-05-27 18:26:57 +02:00
|
|
|
uint64_t now = hwm_get_time();
|
|
|
|
int32_t elapsed_ticks = (now - last_tick_time)/tick_period;
|
2019-07-12 16:09:03 +02:00
|
|
|
|
|
|
|
last_tick_time += elapsed_ticks*tick_period;
|
2021-02-25 21:33:15 +01:00
|
|
|
sys_clock_announce(elapsed_ticks);
|
2017-12-21 14:14:19 +01:00
|
|
|
}
|
|
|
|
|
2020-12-10 13:23:29 +01:00
|
|
|
/**
|
|
|
|
* This function exists only to enable tests to call into the timer ISR
|
|
|
|
*/
|
|
|
|
void np_timer_isr_test_hook(const void *arg)
|
|
|
|
{
|
|
|
|
np_timer_isr(NULL);
|
|
|
|
}
|
|
|
|
|
2019-07-12 16:09:03 +02:00
|
|
|
/**
|
|
|
|
* @brief Set system clock timeout
|
|
|
|
*
|
|
|
|
* Informs the system clock driver that the next needed call to
|
2021-02-25 21:33:15 +01:00
|
|
|
* sys_clock_announce() will not be until the specified number of ticks
|
2019-07-12 16:09:03 +02:00
|
|
|
* from the the current time have elapsed.
|
|
|
|
*
|
|
|
|
* See system_timer.h for more information
|
|
|
|
*
|
|
|
|
* @param ticks Timeout in tick units
|
|
|
|
* @param idle Hint to the driver that the system is about to enter
|
|
|
|
* the idle state immediately after setting the timeout
|
|
|
|
*/
|
2021-02-25 21:33:15 +01:00
|
|
|
void sys_clock_set_timeout(int32_t ticks, bool idle)
|
2019-07-12 16:09:03 +02:00
|
|
|
{
|
|
|
|
ARG_UNUSED(idle);
|
|
|
|
|
|
|
|
#if defined(CONFIG_TICKLESS_KERNEL)
|
2020-05-27 18:26:57 +02:00
|
|
|
uint64_t silent_ticks;
|
2019-07-12 16:09:03 +02:00
|
|
|
|
|
|
|
/* Note that we treat INT_MAX literally as anyhow the maximum amount of
|
2021-02-25 21:33:15 +01:00
|
|
|
* ticks we can report with sys_clock_announce() is INT_MAX
|
2019-07-12 16:09:03 +02:00
|
|
|
*/
|
kernel/timeout: Make timeout arguments an opaque type
Add a k_timeout_t type, and use it everywhere that kernel API
functions were accepting a millisecond timeout argument. Instead of
forcing milliseconds everywhere (which are often not integrally
representable as system ticks), do the conversion to ticks at the
point where the timeout is created. This avoids an extra unit
conversion in some application code, and allows us to express the
timeout in units other than milliseconds to achieve greater precision.
The existing K_MSEC() et. al. macros now return initializers for a
k_timeout_t.
The K_NO_WAIT and K_FOREVER constants have now become k_timeout_t
values, which means they cannot be operated on as integers.
Applications which have their own APIs that need to inspect these
vs. user-provided timeouts can now use a K_TIMEOUT_EQ() predicate to
test for equality.
Timer drivers, which receive an integer tick count in ther
z_clock_set_timeout() functions, now use the integer-valued
K_TICKS_FOREVER constant instead of K_FOREVER.
For the initial release, to preserve source compatibility, a
CONFIG_LEGACY_TIMEOUT_API kconfig is provided. When true, the
k_timeout_t will remain a compatible 32 bit value that will work with
any legacy Zephyr application.
Some subsystems present timeout (or timeout-like) values to their own
users as APIs that would re-use the kernel's own constants and
conventions. These will require some minor design work to adapt to
the new scheme (in most cases just using k_timeout_t directly in their
own API), and they have not been changed in this patch, instead
selecting CONFIG_LEGACY_TIMEOUT_API via kconfig. These subsystems
include: CAN Bus, the Microbit display driver, I2S, LoRa modem
drivers, the UART Async API, Video hardware drivers, the console
subsystem, and the network buffer abstraction.
k_sleep() now takes a k_timeout_t argument, with a k_msleep() variant
provided that works identically to the original API.
Most of the changes here are just type/configuration management and
documentation, but there are logic changes in mempool, where a loop
that used a timeout numerically has been reworked using a new
z_timeout_end_calc() predicate. Also in queue.c, a (when POLL was
enabled) a similar loop was needlessly used to try to retry the
k_poll() call after a spurious failure. But k_poll() does not fail
spuriously, so the loop was removed.
Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2020-03-06 00:18:14 +01:00
|
|
|
if (ticks == K_TICKS_FOREVER) {
|
2019-07-12 16:09:03 +02:00
|
|
|
silent_ticks = INT64_MAX;
|
|
|
|
} else if (ticks > 0) {
|
|
|
|
silent_ticks = ticks - 1;
|
|
|
|
} else {
|
|
|
|
silent_ticks = 0;
|
|
|
|
}
|
|
|
|
hwtimer_set_silent_ticks(silent_ticks);
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2021-02-25 21:33:15 +01:00
|
|
|
* @brief Ticks elapsed since last sys_clock_announce() call
|
2019-07-12 16:09:03 +02:00
|
|
|
*
|
|
|
|
* Queries the clock driver for the current time elapsed since the
|
2021-02-25 21:33:15 +01:00
|
|
|
* last call to sys_clock_announce() was made. The kernel will call
|
2019-07-12 16:09:03 +02:00
|
|
|
* this with appropriate locking, the driver needs only provide an
|
|
|
|
* instantaneous answer.
|
|
|
|
*/
|
2021-02-25 21:33:15 +01:00
|
|
|
uint32_t sys_clock_elapsed(void)
|
2019-07-12 16:09:03 +02:00
|
|
|
{
|
|
|
|
return (hwm_get_time() - last_tick_time)/tick_period;
|
|
|
|
}
|
|
|
|
|
2018-09-30 14:02:16 +02:00
|
|
|
/**
|
|
|
|
* @brief Stop announcing sys ticks into the kernel
|
|
|
|
*
|
|
|
|
* Disable the system ticks generation
|
|
|
|
*/
|
|
|
|
void sys_clock_disable(void)
|
|
|
|
{
|
|
|
|
irq_disable(TIMER_TICK_IRQ);
|
|
|
|
hwtimer_set_silent_ticks(INT64_MAX);
|
|
|
|
}
|
2021-11-04 12:51:39 +01:00
|
|
|
|
2022-01-07 01:38:03 +01:00
|
|
|
/**
|
2021-11-04 12:51:39 +01:00
|
|
|
* @brief Initialize system timer driver
|
|
|
|
*
|
|
|
|
* Enable the hw timer, setting its tick period, and setup its interrupt
|
|
|
|
*/
|
init: remove the need for a dummy device pointer in SYS_INIT functions
The init infrastructure, found in `init.h`, is currently used by:
- `SYS_INIT`: to call functions before `main`
- `DEVICE_*`: to initialize devices
They are all sorted according to an initialization level + a priority.
`SYS_INIT` calls are really orthogonal to devices, however, the required
function signature requires a `const struct device *dev` as a first
argument. The only reason for that is because the same init machinery is
used by devices, so we have something like:
```c
struct init_entry {
int (*init)(const struct device *dev);
/* only set by DEVICE_*, otherwise NULL */
const struct device *dev;
}
```
As a result, we end up with such weird/ugly pattern:
```c
static int my_init(const struct device *dev)
{
/* always NULL! add ARG_UNUSED to avoid compiler warning */
ARG_UNUSED(dev);
...
}
```
This is really a result of poor internals isolation. This patch proposes
a to make init entries more flexible so that they can accept sytem
initialization calls like this:
```c
static int my_init(void)
{
...
}
```
This is achieved using a union:
```c
union init_function {
/* for SYS_INIT, used when init_entry.dev == NULL */
int (*sys)(void);
/* for DEVICE*, used when init_entry.dev != NULL */
int (*dev)(const struct device *dev);
};
struct init_entry {
/* stores init function (either for SYS_INIT or DEVICE*)
union init_function init_fn;
/* stores device pointer for DEVICE*, NULL for SYS_INIT. Allows
* to know which union entry to call.
*/
const struct device *dev;
}
```
This solution **does not increase ROM usage**, and allows to offer clean
public APIs for both SYS_INIT and DEVICE*. Note that however, init
machinery keeps a coupling with devices.
**NOTE**: This is a breaking change! All `SYS_INIT` functions will need
to be converted to the new signature. See the script offered in the
following commit.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
init: convert SYS_INIT functions to the new signature
Conversion scripted using scripts/utils/migrate_sys_init.py.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
manifest: update projects for SYS_INIT changes
Update modules with updated SYS_INIT calls:
- hal_ti
- lvgl
- sof
- TraceRecorderSource
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: devicetree: devices: adjust test
Adjust test according to the recently introduced SYS_INIT
infrastructure.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: kernel: threads: adjust SYS_INIT call
Adjust to the new signature: int (*init_fn)(void);
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-10-19 09:33:44 +02:00
|
|
|
static int sys_clock_driver_init(void)
|
2021-11-04 12:51:39 +01:00
|
|
|
{
|
|
|
|
|
|
|
|
tick_period = 1000000ul / CONFIG_SYS_CLOCK_TICKS_PER_SEC;
|
|
|
|
|
|
|
|
last_tick_time = hwm_get_time();
|
|
|
|
hwtimer_enable(tick_period);
|
|
|
|
|
|
|
|
IRQ_CONNECT(TIMER_TICK_IRQ, 1, np_timer_isr, 0, 0);
|
|
|
|
irq_enable(TIMER_TICK_IRQ);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
SYS_INIT(sys_clock_driver_init, PRE_KERNEL_2,
|
|
|
|
CONFIG_SYSTEM_CLOCK_INIT_PRIORITY);
|