Searched refs:impact (Results 26 – 50 of 51) sorted by relevance
123
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 48 performance impact but can be useful for debugging.
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 32 Details on the behavioral impact of each attribute are in the following
|
| /Zephyr-latest/doc/project/ |
| D | tsc.rst | 195 Abstentions do not impact the number of votes needed to decide a vote.
|
| D | release_process.rst | 133 Bugs of moderate severity and higher that have impact on all users are typically
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 139 a direct impact on how Zephyr headers are interpreted and the extension is
|
| /Zephyr-latest/subsys/shell/ |
| D | Kconfig | 129 This feature has high impact on flash usage.
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 23 cloud service. The particulars of these interfaces can impact the threat
293 lifecycle that impact security include initial provisioning, normal
|
| D | vulnerabilities.rst | 475 bypass security checks performed by system call handlers. The impact
|
| /Zephyr-latest/arch/arc/ |
| D | Kconfig | 380 is not frequent. To reduce the impact on interrupt handling,
|
| /Zephyr-latest/doc/services/shell/ |
| D | index.rst | 37 Some of these features have a significant impact on RAM and flash usage,
750 set too high, the logger thread could be blocked and impact other logger
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | workqueue.rst | 14 to a lower-priority thread so it does not impact time-sensitive processing.
214 existing system workqueue work items without an unacceptable impact;
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 204 by post-process steps that will impact the size of the final binary.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 130 * to not impact the interrupt latency observed by HW interrupts.
186 * does not impact interrupt latency
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 49 - **Applications** running on Zephyr can impact device
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 7 based. Use of these macros has no impact on scheduling. They can be used from
|
| /Zephyr-latest/modules/mbedtls/ |
| D | Kconfig.tls-generic | 392 of asymmetric cryptography, however this might have an impact on the
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 320 **TODO:** Find and define ways, guidelines and processes which minimally impact the daily work
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 891 large impact.
918 describing the change, its rationale and impact, etc. before any pull
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 90 impact, however. Unlike uniprocessor apps, SMP apps using
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 493 negatively impact the ability for the compiler to detect errors and
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.ll_sw_split | 660 else will impact controller stability.
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | Kconfig | 442 Setting this value to a very large number can impact the processing time
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.3.rst | 76 The changes have an impact on users that use the hwinfo API to identify
|
| D | release-notes-2.4.rst | 730 impact in the cooperation between the flash driver and the Controller.
|
| D | release-notes-3.3.rst | 830 at the child level. This change will only impact out-of-tree pin control
|
123
