zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Gerard Marull-Paretas	12b2ee54e3	drivers: timer: s/device.h/init.h Timer "drivers" do not use the device model infrastructure, they are singletons with a SYS_INIT call. This means they do not have to include device.h but init.h. Things worked because device.h includes init.h. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>	2 years ago
Gerard Marull-Paretas	a5fd0d184a	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>	2 years ago
Gerard Marull-Paretas	acc8cb4bc8	include: add missing irq.h include Some modules use the IRQ API without including the necessary headers. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>	3 years ago
Gerard Marull-Paretas	fb60aab245	drivers: migrate includes to <zephyr/...> In order to bring consistency in-tree, migrate all drivers to the new prefix <zephyr/...>. Note that the conversion has been scripted, refer to #45388 for more details. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>	3 years ago
Gerard Marull-Paretas	b1ced75386	drivers: timer: move initialization setup to drivers The weak symbol sys_clock_driver_init has been removed, therefore moving the init responsability to the drivers themselves. As a result, the init function has now been made static on all drivers and moved to the bottom, following the convention used in other areas. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>	4 years ago
Anas Nashif	5d6c219210	drivers: device: do not reuse tag name 'device' Do not reuse tag name (misra rule 5.7). Signed-off-by: Anas Nashif <anas.nashif@intel.com>	4 years ago
Anas Nashif	12b53d121e	clock: rename z_timer_cycle_get_32 -> sys_clock_cycle_get_32 This is another API that is being used in all timer drivers and is not internal to the clock subsystem. Remove the leading z_ and make promote it to a cross-subsystem API. Signed-off-by: Anas Nashif <anas.nashif@intel.com>	4 years ago
Anas Nashif	9c1efe6b4b	clock: remove z_ from semi-public APIs The clock/timer APIs are not application facing APIs, however, similar to arch_ and a few other APIs they are available to implement drivers and add support for new hardware and are documented and available to be used outside of the clock/kernel subsystems. Remove the leading z_ and provide them as clock_* APIs for someone writing a new timer driver to use. Signed-off-by: Anas Nashif <anas.nashif@intel.com>	4 years ago
Martin Åberg	bb5a565aaa	timer: Add support for GRLIB GPTIMER This adds support for GRLIB GPTIMER general purpose timer used in LEON3/4/5 systems. One of the GPTIMER subtimers is used to generate periodic interrutps for announcing ticks. Another subtimer is used as upcounter for the cycle_get_32() service. Signed-off-by: Martin Åberg <martin.aberg@gaisler.com>	5 years ago