Home
last modified time | relevance | path

Searched +full:api +full:- +full:coverage (Results 1 – 25 of 49) sorted by relevance

12

/Zephyr-latest/.github/workflows/
Ddoc-publish.yml3 # SPDX-License-Identifier: Apache-2.0
11 - main
12 - v*
14 - completed
17 doc-publish:
19 runs-on: ubuntu-22.04
23 github.repository == 'zephyrproject-rtos/zephyr'
26 - name: Download artifacts
27 uses: dawidd6/action-download-artifact@v6
29 workflow: doc-build.yml
[all …]
Ddoc-publish-pr.yml3 # SPDX-License-Identifier: Apache-2.0
11 - completed
14 doc-publish:
16 runs-on: ubuntu-22.04
20 github.repository == 'zephyrproject-rtos/zephyr'
23 - name: Download artifacts
24 id: download-artifacts
25 uses: dawidd6/action-download-artifact@v6
27 workflow: doc-build.yml
31 - name: Load PR number
[all …]
Ddoc-build.yml2 # SPDX-License-Identifier: Apache-2.0
8 - cron: '0 */3 * * *'
11 - v*
22 # and each sphinx-build process may use more than 2GiB of RAM.
26 doc-file-check:
28 runs-on: ubuntu-22.04
30 github.repository_owner == 'zephyrproject-rtos'
32 file_check: ${{ steps.check-doc-files.outputs.any_modified }}
34 - name: checkout
38 fetch-depth: 0
[all …]
/Zephyr-latest/tests/benchmarks/sys_kernel/
DREADME.txt8 --------------------------------------------------------------------------------
12 MODULE: kernel API test
19 TEST COVERAGE:
29 TEST COVERAGE:
40 TEST COVERAGE:
52 TEST COVERAGE:
62 TEST COVERAGE:
74 TEST COVERAGE:
86 TEST COVERAGE:
96 TEST COVERAGE:
[all …]
/Zephyr-latest/tests/kernel/events/event_api/src/
Dmain.c4 * SPDX-License-Identifier: Apache-2.0
12 * - API coverage
13 * -# k_event_init K_EVENT_DEFINE
14 * -# k_event_post
15 * -# k_event_set
16 * -# k_event_wait
17 * -# k_event_wait_all
18 * -# k_event_test
/Zephyr-latest/tests/kernel/fifo/fifo_api/src/
Dmain.c4 * SPDX-License-Identifier: Apache-2.0
12 * - API coverage
13 * -# k_fifo_init K_FIFO_DEFINE
14 * -# k_fifo_put k_fifo_put_list k_fifo_put_slist
15 * -# k_fifo_get *
/Zephyr-latest/tests/subsys/edac/ibecc/src/
Ddummy.c4 * SPDX-License-Identifier: Apache-2.0
14 * EDAC dummy is used for coverage tests for -ENOSYS returns
32 /* Error log API */ in ZTEST()
35 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
38 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
41 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
44 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
46 /* Error stat API */ in ZTEST()
49 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
52 zassert_equal(ret, -ENOSYS, "dummy api failed"); in ZTEST()
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-2.0.rst12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
43 ARC, ARM Cortex-M, and x86 architectures.
45 * Additional support for compatibility with 64-bit architectures.
[all …]
Drelease-notes-1.11.rst12 * Thread-level memory protection on x86, ARC and Arm, userspace and memory
15 * Initial Armv8-M architecture support.
20 * Firmware over-the-air (FOTA) updates over BLE using MCUmgr.
32 * SMP-aware scheduler
47 * Armv8-M initial architecture support, including the following cores:
49 * Arm Cortex-M23
50 * Arm Cortex-M33
74 * Refactored dts.fixup so common SoC-related fixes are in arch/<*>/soc
75 and board dts.fixup is only used for board-specific items.
82 * Added I2C master, QSPI flash, and GPIO drivers for nios-II
[all …]
Drelease-notes-1.14.rst17 * CVE-2020-10066
18 * CVE-2020-10069
19 * CVE-2020-13601
20 * CVE-2020-13602
32 * :github:`issuenumber` - issue title
34 * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre
35 * :github:`19917` - Bluetooth: Controller: Missing LL_ENC_RSP after HCI LTK Negative Reply
36 * :github:`21107` - LL_ASSERT and 'Imprecise data bus error' in LL Controller
37 * :github:`21257` - tests/net/net_pkt failed on mimxrt1050_evk board.
38 * :github:`21299` - bluetooth: Controller does not release buffer on central side after peripheral …
[all …]
Drelease-notes-3.4.rst14 * Barrier API: added architecture agnostic API for data memory barriers.
17 * USB device controller API (UDC API) and nRF USBD controller driver.
18 * USB device stack implementation using new UDC API.
20 * Added Power Delivery Source Support to the USB-C Stack.
22 * Cache API functions are now fully in-lined by compilers.
23 * Added an API for real-time clocks (RTC).
26 * SMBus (System Management Bus) API.
29 - Introduction of 3 new test harnesses into twister supporting pyTest,
31 - Transitioning to new Ztest API was completed and legacy Ztest was deprecated.
46 * CVE-2023-1901: Under embargo until 2023-07-04
[all …]
Drelease-notes-2.2.rst18 * Fix CVE-2020-10028
19 * Fix CVE-2020-10060
20 * Fix CVE-2020-10063
21 * Fix CVE-2020-10066
32 * :github:`23494` - Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disa…
33 * :github:`23485` - BT: host: Service Change indication sent regardless of whether it is needed or …
34 * :github:`23482` - 2M PHY + DLE and timing calculations on an encrypted link are wrong
35 * :github:`23070` - Bluetooth: controller: Fix ticker implementation to avoid catch up
36 * :github:`22967` - Bluetooth: controller: ASSERTION FAIL on invalid packet sequence
37 * :github:`24183` - [v2.2] Bluetooth: controller: split: Regression slave latency during connection…
[all …]
Drelease-notes-1.9.rst49 * Bluetooth Qualification-ready BLE Controller
52 * Pthreads compatible API
53 * BSD Sockets compatible API
56 * Revamp Testsuite, Increase Coverage
82 * ARC: Nested interrupt support for normal, non-FIRQ interrupts
90 * arm: Added Olimex STM32-E407 and STM32-P405 boards
91 * arm: Added STM32F412 Nucleo and STM32F429I-DISC1 boards
116 * net-app API support added. This is higher level API that can be used
125 * BSD Socket compatible API layer, allowing to write and/or port simple
126 networking applications using a well-known, cross-platform API
[all …]
Drelease-notes-3.2.rst13 * Added support for :ref:`bin-blobs` (also see :ref:`west-blobs`).
15 * Converted all supported boards from ``pinmux`` to :ref:`pinctrl-guide`.
17 * Support for :ref:`W1 api<w1_api>`.
31 * CVE-2022-2993: Under embargo until 2022-11-03
33 * CVE-2022-2741: Under embargo until 2022-10-14
35 API Changes
56 This definition can be used by third-party code to compile code conditional
58 Therefore, any third-party code integrated using the Zephyr build system will
91 changed from ``-ENETDOWN`` to ``-ENETUNREACH``. A return value of ``-ENETDOWN`` now indicates
108 deprecated kernel work queue API have been removed:
[all …]
Drelease-notes-2.5.rst27 * CVE-2021-3323: Under embargo until 2021-04-14
28 * CVE-2021-3321: Under embargo until 2021-04-14
29 * CVE-2021-3320: Under embargo until 2021-04-14
39 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
41 API Changes
56 * Changed vcnl4040 dts binding default for property 'proximity-trigger'.
63 * The :c:func:`mqtt_keepalive_time_left` function now returns -1 if keep alive
67 timeout usage must use the new-style k_timeout_t type and not the
84 * A new :ref:`regulator_api` API has been added to support controlling power
87 GPIO-only regulators a devicetree property ``supply-gpios`` is defined as a
[all …]
/Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/
DREADME.txt3 returns error code as described in the API documentation
15 These tests were written to increase test coverage for the Watchdog driver.
16 Since, coverage data is stored in the RAM, it is lost when watchdog fires.
26 Tests are based on the watchdog API documentation available here:
42 - WDT_FLAG_RESET_NONE - when watchdog expires, it's callback is serviced but
44 - WDT_FLAG_RESET_CPU_CORE - when watchdog expires, only one core is reset, while
46 - WDT_FLAG_RESET_SOC - when watchdog expires, target as "a whole" is reset.
68 - WDT_OPT_PAUSE_IN_SLEEP;
69 - WDT_OPT_PAUSE_HALTED_BY_DBG.
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst20 been completed. This allows for testing that high-level code can
21 handle these situations correctly. Test coverage can therefore
27 The diagram below shows application code / high-level tests at the top.
39 Separately we can test the STM32 and NXP I2C drivers on real hardware using API
49 Controller) on native_sim using emulators for all non-chip drivers.
56 * Ensure 100% test coverage for drivers (green)
63 native_sim. We can develop on a host, use source-level debugging, etc.
79 .. code-block:: C
87 The ``EMUL_DT_DEFINE()`` function accepts two API types:
89 #. ``bus_api`` - This points to the API for the upstream bus that the emulator
[all …]
/Zephyr-latest/doc/contribute/
Dcontributor_expectations.rst1 .. _contributor-expectations:
10 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
14 - Less wasted work if reviewers or maintainers reject the direction of the
17 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
20 - Easier to revert if the PR breaks functionality.
32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
40 - Adding new features or functionality.
42 - Modifying a feature, especially for API behavior contract changes.
[all …]
/Zephyr-latest/doc/project/
Ddocumentation.rst1 .. _code-documentation:
6 API Documentation
10 requirement for defining an API's success. Doxygen is a general purpose
12 generates either an on-line documentation browser (in HTML) and/or provides
21 features and can be traced back to features. We use the API documentation as the
44 :ref:`Ztest framework <test-framework>`. Test documentation should only be done
50 Test documentation should not interfere with the actual API documentation and
52 scheme and following a well-defined structure we will be able to group this
56 - All test code documentation should be grouped under the ``all_tests`` doxygen
58 - All test documentation should be under doxygen groups that are prefixed
[all …]
/Zephyr-latest/arch/posix/
DCMakeLists.txt1 # SPDX-License-Identifier: Apache-2.0
12 # For ex. target_compile_options(native_simulator INTERFACE "-m64")
16 # For ex. target_link_options(native_simulator INTERFACE "-lstdc++")
29 …roperty(TARGET native_simulator APPEND PROPERTY LOCALIZE_EXTRA_OPTIONS "--localize-symbol=spinel*")
47 # some gcc versions fail to build without -fPIC
48 zephyr_compile_options(-m64 -fPIC)
49 zephyr_link_libraries(-m64)
51 target_link_options(native_simulator INTERFACE "-m64")
52 target_compile_options(native_simulator INTERFACE "-m64")
54 zephyr_compile_options(-m32)
[all …]
/Zephyr-latest/tests/boards/intel_adsp/smoke/src/
Dipm.c2 * SPDX-License-Identifier: Apache-2.0
55 * We do this using the underlying intel_adsp_ipc API, which works in msg_transact()
57 * actual in-use amount of the message will be one word in msg_transact()
85 /* Do it twice just for coverage on the wait parameter */ in ZTEST()
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst3 API Lifecycle
7 given API will not change in future releases. At the same time, developers
15 :alt: API Life Cycle
16 :figclass: align-center
18 API Life Cycle
20 An up-to-date table of all APIs and their maturity level can be found in the
35 - Documentation of the API (usage)
38 - The API introduction should be accompanied by at least one implementation
39 of said API (in the case of peripheral APIs, this corresponds to one driver)
40 - At least one sample using the new API (may only build on one single board)
[all …]
/Zephyr-latest/doc/_scripts/
Dredirects.py3 SPDX-License-Identifier: Apache-2.0
10 - Please keep this list sorted alphabetically.
11 - URLs must be relative to document root (with NO leading slash), and
16 # zephyr-keep-sorted-start
30 ('connectivity/bluetooth/api/audio/shell/bap', 'connectivity/bluetooth/shell/audio/bap'),
31 …('connectivity/bluetooth/api/audio/shell/bap_broadcast_assistant', 'connectivity/bluetooth/shell/a…
32 …('connectivity/bluetooth/api/audio/shell/bap_scan_delegator', 'connectivity/bluetooth/shell/audio/…
33 ('connectivity/bluetooth/api/audio/shell/cap', 'connectivity/bluetooth/shell/audio/cap'),
34 ('connectivity/bluetooth/api/audio/shell/ccp', 'connectivity/bluetooth/shell/audio/ccp'),
35 ('connectivity/bluetooth/api/audio/shell/csip', 'connectivity/bluetooth/shell/audio/csip'),
[all …]
/Zephyr-latest/kernel/
Dinit.c2 * Copyright (c) 2010-2014 Wind River Systems, Inc.
4 * SPDX-License-Identifier: Apache-2.0
27 #include <zephyr/linker/linker-defs.h>
68 thread_data->init_thread, in z_init_static_threads()
69 thread_data->init_stack, in z_init_static_threads()
70 thread_data->init_stack_size, in z_init_static_threads()
71 thread_data->init_entry, in z_init_static_threads()
72 thread_data->init_p1, in z_init_static_threads()
73 thread_data->init_p2, in z_init_static_threads()
74 thread_data->init_p3, in z_init_static_threads()
[all …]
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.bash1 # Bash auto-completion for west subcommands and flags. To initialize, run
3 # source west-completion.bash
7 __west_previous_extglob_setting=$(shopt -p extglob)
8 shopt -s extglob
12 # bash_completion - programmable completion functions for bash 3.2+
14 # Copyright © 2006-2008, Ian Macdonald <ian@caliban.org>
15 # © 2009-2010, Bash Completion Maintainers
16 # <bash-completion-devel@lists.alioth.debian.org>
33 # http://bash-completion.alioth.debian.org/
41 # if test "${words_[cword_-1]}" = -w
[all …]

12