Searched full:sensitive (Results 1 – 25 of 72) sorted by relevance
123
| /Zephyr-latest/ |
| D | .codechecker.yml | 9 # Enable the sensitive profile
10 - --enable=sensitive
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_assistant/ |
| D | Kconfig | 13 Matching is not case sensitive.
22 Matching is not case sensitive.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tsn.rst | 3 Time Sensitive Networking
|
| D | gptp.rst | 15 Time-Sensitive Applications in Bridged Local Area Networks).
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 79 sensitive nature of security reports. The issues are only visible to
106 Security sensitive vulnerabilities shall be made public after an
116 sensitive nature of what is being fixed, and shall not refer to CVE
134 that release. Because of the sensitive nature of these
199 Due to the sensitive nature of security vulnerabilities, it is
|
| D | secure-coding.rst | 46 documentation about how security-sensitive issues are handled by the
258 Because security issues are often sensitive, this issue tracking
|
| /Zephyr-latest/tests/kernel/mem_protect/demand_paging/mem_map/boards/ |
| D | qemu_x86_tiny.conf | 4 # The test is highly sensitive to size of kernel image.
|
| /Zephyr-latest/tests/posix/common/boards/ |
| D | qemu_x86_tiny.conf | 4 # The test is highly sensitive to size of kernel image.
|
| /Zephyr-latest/dts/bindings/input/ |
| D | cirque,pinnacle-common.yaml | 18 ADC attenuation, 1x is the most sensitive and 4x is the least sensitive.
|
| /Zephyr-latest/dts/bindings/stepper/adi/ |
| D | adi,trinamic-stallguard.yaml | 20 -64 to +63: A higher value makes StallGuard2 less sensitive and requires more torque
|
| /Zephyr-latest/samples/bluetooth/cap_acceptor/ |
| D | Kconfig | 48 will only listen to the specified broadcast source. Not case sensitive.
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | nxp,fxls8974-common.yaml | 37 Range in g. Default value is 2 because it is the most sensitive setting.
|
| /Zephyr-latest/include/zephyr/arch/x86/ia32/scripts/ |
| D | shared_kernel_pages.ld | 14 * no sensitive data should be here as Meltdown exploits may read it.
|
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | wdog.S | 41 /* Disable interrupts if they're on. This is timing-sensitive code. */
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_sink/ |
| D | Kconfig | 36 will only listen to the specified broadcast source. Not case sensitive.
|
| /Zephyr-latest/dts/bindings/serial/ |
| D | st,stm32-uart-base.yaml | 90 allows more reliable communication with UART devices sensitive to variation of inter-frames
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 158 that applications wipe all sensitive data from memory when it is no
162 Wiping sensitive data includes:
|
| /Zephyr-latest/doc/services/debugging/ |
| D | debugmon.rst | 9 This strategy makes it possible to debug time-sensitive software, that would
|
| /Zephyr-latest/arch/x86/core/ia32/ |
| D | userspace.S | 84 /* Trampoline stack should have nothing sensitive in it at this point */
142 /* Trampoline stack should have nothing sensitive in it at this point */
182 /* Trampoline stack should have nothing sensitive in it at this point */
|
| /Zephyr-latest/lib/heap/ |
| D | Kconfig | 14 environments that require sensitive detection of memory
|
| /Zephyr-latest/doc/kernel/services/scheduling/ |
| D | index.rst | 186 only when dealing with lower priority threads that are less time-sensitive.
255 Use preemptive threads to give priority to time-sensitive processing
256 over less time-sensitive processing.
|
| /Zephyr-latest/arch/x86/core/ |
| D | Kconfig.ia32 | 126 For vulnerable systems that process sensitive information in the
|
| /Zephyr-latest/arch/x86/core/intel64/ |
| D | userspace.S | 55 /* Trampoline stack should have nothing sensitive in it at this point */
158 * calling convention, but sensitive data may lurk in caller-saved regs
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 26 read operation is very fast. The expectation is that very sensitive
129 timing-sensitive applications with long uptimes will be configured to
247 a correct default for timing sensitive applications (because it
|
| /Zephyr-latest/tests/arch/x86/cpu_scrubs_regs/src/ |
| D | main.c | 21 * that all of them were scrubbed and do not contain any sensitive data in z_impl_test_cpu_write_reg()
|
123
