Home
last modified time | relevance | path

Searched refs:process (Results 1 – 25 of 347) sorted by relevance

12345678910>>...14

/Zephyr-latest/subsys/logging/backends/
Dlog_backend_semihost.c44 static void process(const struct log_backend *const backend, union log_msg_generic *msg) in process() function
64 .process = process,
Dlog_backend_xtensa_sim.c40 static void process(const struct log_backend *const backend, in process() function
69 .process = process,
Dlog_backend_adsp.c73 static void process(const struct log_backend *const backend, in process() function
92 .process = process,
Dlog_backend_efi_console.c41 static void process(const struct log_backend *const backend, in process() function
81 .process = process,
Dlog_backend_native_posix.c73 static void process(const struct log_backend *const backend, in process() function
90 .process = process,
Dlog_backend_spinel.c32 static void process(const struct log_backend *const backend, in process() function
105 .process = process,
Dlog_backend_adsp_mtrace.c180 static void process(const struct log_backend *const backend, in process() function
210 .process = process,
Dlog_backend_ws.c141 static void process(const struct log_backend *const backend, in process() function
214 .process = process,
Dlog_backend_ble.c144 static void process(const struct log_backend *const backend, union log_msg_generic *msg) in process() function
191 const struct log_backend_api log_backend_ble_api = {.process = process,
/Zephyr-latest/scripts/utils/
Dtwister_to_list.py32 def process(conf): function
61 update |= process(common)
64 update |= process(spec)
/Zephyr-latest/tests/subsys/logging/log_switch_format/src/
Dmock_backend.c49 static void process(const struct log_backend *const backend, in process() function
116 .process = process,
/Zephyr-latest/tests/subsys/logging/log_syst/src/
Dmock_backend.c45 static void process(const struct log_backend *const backend, in process() function
126 .process = process,
/Zephyr-latest/doc/contribute/
Dproposals_and_rfcs.rst10 design process and produce a consensus among the project stakeholders.
12 The "RFC" (request for comments) process is intended to provide a consistent and
15 Contributors and project stakeholders should consider using this process if
26 The RFC process is a great opportunity to get more eyeballs on proposals coming
31 The RFC process can also be helpful to encourage discussions about a proposed
43 The process in itself consists in creating a GitHub issue with the :ref:`RFC
/Zephyr-latest/.github/
DSECURITY.md19 ## Reporting process
23 page for details on the process.
/Zephyr-latest/boards/native/native_posix/
DKconfig12 Will produce a console Linux process which can be executed natively.
26 When selected the execution of the process will be slowed down to real time.
28 If deselected, the process will run as fast as possible.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dprovisioning.rst6 Provisioning is the process of adding devices to a mesh network. It requires
12 Provisioning process. Before the provisioning process starts, the
19 The Provisioning process
25 Provisioning is a five-step process, involving the following steps:
36 To start the provisioning process, the unprovisioned device must first start
74 The provisioner initiates the Provisioning process by sending a Provisioning
86 Before the provisioning process can begin, the provisioner and the unprovisioned
89 In-band public key exchange is a part of the provisioning process and always
101 for each Provisioning process.
106 process is started by initializing pointers to
[all …]
/Zephyr-latest/tests/subsys/logging/log_blocking/src/
Dmain.c105 static void process(const struct log_backend *const backend, union log_msg_generic *msg) in process() function
135 .process = process,
/Zephyr-latest/boards/native/nrf_bsim/
DKconfig12 Will produce a console Linux process which can be executed natively.
23 Will produce a console Linux process which can be executed natively.
34 Will produce a console Linux process which can be executed natively.
45 Will produce a console Linux process which can be executed natively.
/Zephyr-latest/doc/security/
Dsecurity-overview.rst10 defined security process that helps developers build more secure
12 the key ideas of the security process and outlines which documents need
13 to be created. After the process is implemented and all supporting
20 We begin with an overview of the Zephyr development process, which
23 In subsequent sections, the individual parts of the process are treated
27 development process that ensures adherence to relevant coding
35 Finally, a process shall be defined for reporting, classifying,
43 .. figure:: media/security-process-steps.png
50 This document is a guideline for the development of a security process
52 Committee. It provides an overview of the Zephyr security process for
[all …]
Dhardening-tool.rst7 process, known as "hardening", involves strengthening the security of a system to protect it from
10 At a high-level, hardening a Zephyr application can be seen as a two-fold process:
18 To simplify this process, Zephyr offers a **hardening tool** designed to analyze an application's
/Zephyr-latest/tests/subsys/logging/log_stress/src/
Dmain.c51 static void process(const struct log_backend *const backend, in process() function
79 .process = process,
/Zephyr-latest/tests/subsys/logging/log_link_order/src/
Dmain.c26 static void process(const struct log_backend *const backend, in process() function
38 .process = process,
/Zephyr-latest/modules/
DKconfig.intel7 Build the Intel HAL module during build process.
DKconfig.xtensa7 Build the Xtensa HAL module during build process.
/Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/
Dhardware_adapter.py111 process = stdout = None
113process = subprocess.Popen(self.command, stdout=subprocess.PIPE, stderr=subprocess.STDOUT, env=sel…
114 stdout, _ = process.communicate(timeout=self._flashing_timeout)
116 process.kill()
131 if process is not None and process.returncode == 0:

12345678910>>...14