| /Zephyr-Core-3.6.0/include/zephyr/input/ |
| D | input_hid.h | 16 * @brief Convert an input code to HID code.
18 * Takes an input code as input and returns the corresponding HID code as
19 * output. The return value is -1 if the code is not found, if found it can
22 * @param input_code Event code (see @ref INPUT_KEY_CODES).
23 * @retval the HID code corresponding to the input code.
24 * @retval -1 if there's no HID code for the specified input code.
29 * @brief Convert an input code to HID modifier.
31 * Takes an input code as input and returns the corresponding HID modifier as
34 * @param input_code Event code (see @ref INPUT_KEY_CODES).
35 * @retval the HID modifier corresponding to the input code.
[all …]
|
| /Zephyr-Core-3.6.0/doc/_extensions/zephyr/ |
| D | domain.py | 12 specific to the Zephyr RTOS project (ex. code samples).
17 - ``zephyr:code-sample::`` - Defines a code sample.
20 code sample is a good showcase of) as options.
21 The content of the directive is used as the description of the code sample.
26 .. zephyr:code-sample:: blinky
36 - ``:zephyr:code-sample:`` - References a code sample.
37 The role takes the ID of the code sample as the argument. The role renders as a link to the code
38 sample, and the link text is the name of the code sample (or a custom text if an explicit name is
44 Check out :zephyr:code-sample:`sample-foo` for an example of how to use the foo API. You may
45 also be interested in :zephyr:code-sample:`this one <sample-bar>`.
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/ |
| D | bluetooth-shell.rst | 19 .. code-block:: console
25 The first step is enabling Bluetooth. To do so, use the :code:`bt init` command. The following
28 .. code-block:: console
52 :kconfig:option:`CONFIG_BT_ID_MAX`. To create a new identity, use :code:`bt id-create` command. You
53 can then use it by selecting it with its ID :code:`bt id-select <id>`. Finally, you can list all the
54 available identities with :code:`id-show`.
59 Start scanning by using the :code:`bt scan on` command. Depending on the environment you're in, you
60 may see a lot of lines printed on the shell. To stop the scan, run :code:`bt scan off`, the
65 .. code-block:: console
82 address and by periodic advertising interval. To apply a filter, use the :code:`bt scan-set-filter`
[all …]
|
| /Zephyr-Core-3.6.0/doc/develop/getting_started/ |
| D | index.rst | 11 - Get the source code
27 .. code-block:: bash
83 .. code-block:: bash
90 .. code-block:: bash
99 .. code-block:: bash
115 .. code-block:: bash
124 .. code-block:: bash
133 .. code-block:: bash
140 .. code-block:: bash
179 .. code-block:: bat
[all …]
|
| /Zephyr-Core-3.6.0/doc/contribute/ |
| D | external.rst | 6 In some cases it is desirable to leverage existing, external source code in
10 This section describes the circumstances under which external source code can be
20 code analysis, testing or simulation please refer to the
28 External source code licensed under the Apache-2.0 license is not subject to
31 Integrating code into the Zephyr Project from other projects that use a license
48 for contributed code, we ensure that the Zephyr community can develop products
54 Just like with any other regular contribution, one that contains external code
55 needs to be evaluated for merit. However, in the particular case of code that
59 Committee and evaluated carefully before the external source code is accepted
66 important for source code that deals with security or cryptography.
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/networking/api/ |
| D | zperf.rst | 20 .. code-block:: console
25 in Zephyr. See :zephyr:code-sample:`zperf sample application <zperf>` for details.
33 .. code-block:: console
39 .. code-block:: console
46 .. code-block:: console
53 .. code-block:: console
61 .. code-block:: console
68 .. code-block:: console
75 .. code-block:: console
82 .. code-block:: console
[all …]
|
| D | net_mgmt.rst | 14 layer code itself, to call defined network routines at any level in
16 example, by using these APIs, application code can request a scan be done on a
21 by eliminating code at build time for management routines that are not
53 pair of layer and code, whereas on the command part it will be a mask of
67 code. This makes it possible for different events to be handled by the
73 layer and layer code. A callback handler function **must** check
74 the event code (passed as an argument) against the specific network
83 layer code.)
87 .. code-block:: c
134 .. code-block:: c
[all …]
|
| /Zephyr-Core-3.6.0/cmake/modules/ |
| D | FindDeprecated.cmake | 5 # FindDeprecated module provides a single location for deprecated CMake build code.
6 # Whenever CMake code is deprecated it should be moved to this module and
7 # corresponding COMPONENTS should be created with name identifying the deprecated code.
9 # This makes it easier to maintain deprecated code and cleanup such code when it
13 # CMakeList.txt contains deprecated code, like:
18 # such code can easily be around for a long time, so therefore such code should
22 # # This code has been deprecated after Zephyr x.y
28 # and then in the original CMakeLists.txt, this code is inserted instead:
42 # This code was deprecated after Zephyr v3.1.0
58 # This code was deprecated after Zephyr v3.3.0
[all …]
|
| /Zephyr-Core-3.6.0/samples/net/zperf/ |
| D | Kconfig | 7 bool "Relocate networking code into RAM"
10 Relocate networking code into RAM when running the zperf
11 sample. Can improve performance on platforms with fast code
17 string "Networking code RAM location"
20 Region to relocate networking code to
|
| /Zephyr-Core-3.6.0/dts/bindings/input/ |
| D | zephyr,lvgl-encoder-input.yaml | 14 rotation-input-code = <INPUT_REL_Y>;
15 button-input-code = <INPUT_KEY_0>;
23 rotation-input-code:
27 Input event code associated with rotation (INPUT_REL_*).
29 button-input-code:
32 Input event key code for encoder button (INPUT_KEY_* or INPUT_BTN_*).
|
| /Zephyr-Core-3.6.0/samples/net/sockets/echo_async_select/ |
| D | README.rst | 1 .. zephyr:code-sample:: async-sockets-echo-select
13 the :zephyr:code-sample:`async-sockets-echo` sample.
15 The source code for this sample application can be found at:
38 .. code-block:: console
44 it. Unlike the :zephyr:code-sample:`sockets-echo` sample, this application
48 by changing ``NUM_FDS`` defined in the source code.
53 The same application source code can be built for a POSIX system, e.g.
54 Linux. (Note: if you look at the source, you will see that the code is
60 .. code-block:: console
66 .. code-block:: console
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/shell/ |
| D | bap.rst | 15 .. code-block:: console
75 .. code-block:: console
88 .. code-block:: console
99 .. code-block:: console
109 .. code-block:: console
117 .. code-block:: console
127 .. code-block:: console
135 .. code-block:: console
145 The command :code:`bap create_broadcast_sink 0xEF6716` will either use existing periodic advertising
148 .. code-block:: console
[all …]
|
| D | iso.rst | 7 .. code-block:: console
19 create-big :Create a BIG as a broadcaster [enc <broadcast code>]
22 [enc <broadcast code>]
30 .. code-block:: console
37 .. code-block:: console
43 .. code-block:: console
51 .. code-block:: console
60 .. code-block:: console
|
| /Zephyr-Core-3.6.0/tests/drivers/eeprom/api/src/ |
| D | main.c | 33 zassert_equal(-EINVAL, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
51 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
54 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
57 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
65 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
68 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
71 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
90 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
93 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
96 zassert_equal(0, rc, "Unexpected error code (%d)", rc); in ZTEST_USER()
[all …]
|
| /Zephyr-Core-3.6.0/doc/services/device_mgmt/ |
| D | mcumgr_callbacks.rst | 10 (and module) code to receive callbacks for MCUmgr events that they are
11 interested in and react to them or return a status code to the calling function
26 registration and notification system into the code. This will not provide any
36 application code as per:
38 .. code-block:: c
54 /* Return OK status code to continue with acceptance to underlying handler */
65 This code registers a handler for the :c:enumerator:`MGMT_EVT_OP_CMD_DONE`
85 .. code-block:: c
93 The following code is not allowed, and will cause undefined operation, because
97 .. code-block:: c
[all …]
|
| /Zephyr-Core-3.6.0/samples/subsys/usb/hid-mouse/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-hid-mouse
38 .. code-block:: none
58 .. code-block:: console
76 .. code-block:: console
85 Event code 272 (BTN_LEFT)
86 Event code 273 (BTN_RIGHT)
87 Event code 274 (BTN_MIDDLE)
89 Event code 0 (REL_X)
90 Event code 1 (REL_Y)
91 Event code 8 (REL_WHEEL)
[all …]
|
| /Zephyr-Core-3.6.0/doc/services/debugging/ |
| D | gdbstub.rst | 75 .. code-block:: bash
81 .. code-block:: bash
106 .. code-block:: bash
112 .. code-block:: text
118 .. code-block:: text
124 .. code-block:: text
134 .. code-block:: text
140 GDB also shows where the code execution is stopped. In this case,
145 .. code-block:: text
155 #. Use command ``list`` to show the source code and surroundings where
[all …]
|
| /Zephyr-Core-3.6.0/samples/net/sockets/echo_async/ |
| D | README.rst | 1 .. zephyr:code-sample:: async-sockets-echo
13 the :zephyr:code-sample:`sockets-echo` sample. It's a more involved application,
17 The source code for this sample application can be found at:
40 .. code-block:: console
46 it. Unlike the above-mentioned :zephyr:code-sample:`sockets-echo` sample, this application
50 by changing ``NUM_FDS`` defined in the source code.
55 The same application source code can be built for a POSIX system, e.g.
56 Linux. (Note: if you look at the source, you will see that the code is
62 .. code-block:: console
68 .. code-block:: console
[all …]
|
| /Zephyr-Core-3.6.0/samples/subsys/display/lvgl/boards/ |
| D | native_posix.overlay | 29 zephyr,code = <INPUT_KEY_R>;
34 zephyr,code = <INPUT_KEY_B>;
39 zephyr,code = <INPUT_KEY_0>;
44 zephyr,code = <INPUT_KEY_LEFT>;
49 zephyr,code = <INPUT_KEY_RIGHT>;
54 zephyr,code = <INPUT_KEY_ENTER>;
67 rotation-input-code = <INPUT_REL_WHEEL>;
68 button-input-code = <INPUT_KEY_0>;
85 /* Skip pin 0 with the unknown code 0 */
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_set_adv_own_addr/src/ |
| D | test_suite_invalid_inputs.c | 81 zassert_true(err == -ENOTSUP, "Unexpected error code '%d' was returned", err); in ZTEST()
87 * Operation fails if bt_id_set_adv_private_addr() failed and a negative error code is returned.
93 * - bt_id_set_adv_private_addr() fails and returns a negative error code (failure)
96 * - bt_id_set_adv_own_addr() returns a negative error code (failure)
111 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
119 * Operation fails if bt_id_set_adv_random_addr() failed and a negative error code is returned.
124 * - bt_id_set_adv_random_addr() fails and returns a negative error code (failure)
127 * - bt_id_set_adv_own_addr() returns a negative error code (failure)
147 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
158 * Operation fails if bt_id_set_adv_random_addr() failed and a negative error code is returned.
[all …]
|
| /Zephyr-Core-3.6.0/samples/application_development/code_relocation_nocopy/ |
| D | README.rst | 3 Code relocation nocopy
8 A simple example that demonstrates how relocation of code, data or bss sections
11 Differently from the code relocation sample, this sample is relocating the
12 content of the ext_code.c file to a different FLASH section and the code is XIP
13 directly from there without the need to copy / relocate the code.
23 In this sample we relocate some of the code to the external flash memory with
36 .. code-block:: console
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_create/src/ |
| D | test_suite_invalid_inputs.c | 26 * - '-EINVAL' error code is returned representing invalid values were used.
34 zassert_true(err == -EINVAL, "Unexpected error code '%d' was returned", err); in ZTEST()
46 * - '-EINVAL' error code is returned representing invalid values were used.
55 zassert_true(err == -EINVAL, "Unexpected error code '%d' was returned", err); in ZTEST()
68 * - '-ENOMEM' error code is returned representing invalid values were used.
78 zassert_true(err == -ENOMEM, "Unexpected error code '%d' was returned", err); in ZTEST()
90 * - '-EINVAL' error code is returned representing invalid values were used.
102 zassert_true(err == -EINVAL, "Unexpected error code '%d' was returned", err); in ZTEST()
114 * - '-EINVAL' error code is returned representing invalid values were used.
122 zassert_true(err == -EINVAL, "Unexpected error code '%d' was returned", err); in ZTEST()
[all …]
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_set_adv_private_addr/src/ |
| D | test_suite_invalid_cases.c | 43 * - bt_rand() fails and returns a negative error code (failure)
46 * - bt_id_set_adv_private_addr() returns a negative error code (failure)
59 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
75 * - bt_id_set_adv_random_addr() fails and returns a negative error code (failure)
78 * - bt_id_set_adv_private_addr() returns a negative error code (failure)
88 /* This will make set_random_address() returns a negative number error code */ in ZTEST()
93 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
102 * - bt_rpa_create() fails and returns a negative error code (failure)
107 * - bt_id_set_adv_private_addr() returns a negative error code (failure)
121 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
[all …]
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_set_private_addr/src/ |
| D | test_suite_invalid_cases.c | 42 * - bt_rand() fails and returns a negative error code (failure)
46 * - bt_id_set_private_addr() returns a negative error code (failure)
58 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
66 * - bt_rpa_create() fails and returns a negative error code (failure)
70 * - bt_id_set_private_addr() returns a negative error code (failure)
82 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
99 * - set_random_address() fails and returns a negative error code (failure)
102 * - bt_id_set_private_addr() returns a negative error code (failure)
112 /* This will make set_random_address() returns a negative number error code */ in ZTEST()
117 zassert_true(err < 0, "Unexpected error code '%d' was returned", err); in ZTEST()
|
| /Zephyr-Core-3.6.0/include/zephyr/fs/ |
| D | fs_sys.h | 33 * @return 0 on success, negative errno code on fail.
43 * @return Number of bytes read on success, negative errno code on fail.
52 * @return Number of bytes written on success, negative errno code on fail.
62 * @return New position in the file or negative errno code on fail.
69 * @return Current position in the file or negative errno code on fail.
77 * @return 0 on success, negative errno code on fail.
84 * @return 0 on success, negative errno code on fail.
91 * @return 0 on success, negative errno code on fail.
105 * @return 0 on success, negative errno code on fail.
113 * @return 0 on success, negative errno code on fail.
[all …]
|
