Searched refs:goal (Results 1 – 25 of 26) sorted by relevance
12
| /Zephyr-latest/drivers/video/ |
| D | video_common.c | 111 uint64_t goal = desired->numerator; in video_closest_frmival_stepwise() local
117 goal *= stepwise->min.denominator * stepwise->max.denominator * stepwise->step.denominator; in video_closest_frmival_stepwise()
120 goal = CLAMP(goal, min, max); in video_closest_frmival_stepwise()
123 match->numerator = min + DIV_ROUND_CLOSEST(goal - min, step) * step; in video_closest_frmival_stepwise()
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | application.py | 252 for goal in goals:
253 if goal in {'build', 'sign'}:
255 elif goal == 'flash':
257 elif goal == 'debug':
259 elif goal == 'debugserver':
261 elif goal == 'attach':
384 for goal in goals:
385 if goal == 'build':
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig.espi_emul | 15 eSPI is an interface using SPI wires, whose main goal is to reduce the
|
| /Zephyr-latest/samples/userspace/syscall_perf/ |
| D | README.rst | 9 The goal of this sample application is to measure the performance loss when a
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 9 goal is to support configuration without having to change any source code.
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 27 … constrained devices, across multiple architectures. The Zephyr Project’s goal is to establish a n…
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 27 … constrained devices, across multiple architectures. The Zephyr Project’s goal is to establish a n…
|
| D | response_100k.html.bin | 27 … constrained devices, across multiple architectures. The Zephyr Project’s goal is to establish a n…
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | index.rst | 18 These options have the goal to document an available hardware feature and
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 9 Since, main goal is to detect (and report) invalid use of the driver,
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 22 is the case for all API calls is an ongoing one, but the overall goal is
24 subsystem in the direction of such goal are welcome.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 11 approach of the project's safety effort. The goal is **NOT** to create new requirements to request
|
| D | safety_overview.rst | 19 In this section we give the reader an overview of what the general goal of the safety certification
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 14 The goal here is to demonstrate:
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 34 | Its foremost goal is functional support for the API on all board targets.
|
| /Zephyr-latest/tests/ztest/error_hook/ |
| D | README.txt | 22 error happened. This is why we add a hook on it, in order to achieve that goal.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 156 The Zephyr project uses an automated quality assurance process. The goal
402 evaluated. The main goal is to keep the code as simple as
616 One goal of creating a secure branch of the Zephyr RTOS is to create a
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 184 The scope of this test suite may grow over time. The goal is to specify
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 11 restrictions on the size, format or usage of the images. The primary design goal of the subsystem is
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 300 The Zephyr project follows industry standards and processes with the goal of
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 33 …The word "image" is used because your main goal is usually to generate the binaries of the firmware
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 63 The goal of the early boot sequence is to take the system from the state it is
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 490 platform_allow if the goal is to limit scope due to timing or
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.2.rst | 120 possible to fully achieve this goal. We recommend to switch to the new GPIO
|
| /Zephyr-latest/doc/contribute/coding_guidelines/ |
| D | index.rst | 1289 non-measurable component to what "commonly used" means, the ultimate goal is
|
12
