Home
last modified time | relevance | path

Searched full:leakage (Results 1 – 25 of 64) sorted by relevance

123

/freebsd/sys/contrib/device-tree/Bindings/reserved-memory/
H A Dshared-dma-pool.yaml36 unexpected addresses, possibly leading to data leakage or
40 leakage and system memory corruption, the system needs to
/freebsd/contrib/lutok/
H A DREADME5 RAII to prevent resource leakage, expose C++-friendly data types, report
/freebsd/sys/contrib/device-tree/src/arm/synaptics/
H A Dberlin2cd-valve-steamlink.dts42 * less depending on leakage value in OTP), and buck2 likely used for
/freebsd/sys/contrib/device-tree/Bindings/nvmem/
H A Drockchip,otp.yaml114 cpu_leakage: cpu-leakage@17 {
/freebsd/sys/contrib/device-tree/Bindings/sound/
H A Dnuvoton,nau8325.yaml26 pin, it is important to use a low-leakage capacitor.
/freebsd/tools/test/stress2/misc/
H A Dthr3.sh29 # Demonstrate VM leakage. Not seen on FreeBSD HEAD.
/freebsd/sys/contrib/device-tree/Bindings/power/
H A Dpower_domain.txt4 used for power gating of selected IP blocks for power saving by reduced leakage
H A Dpower-domain.yaml17 leakage current. Moreover, in some cases the similar PM domains may also be
/freebsd/sys/security/mac_ifoff/
H A Dmac_ifoff.c43 * enabled. Prevents protocol stack-driven packet leakage in unsafe
/freebsd/contrib/llvm-project/lldb/docs/design/
H A Dsbapi.rst
/freebsd/contrib/netbsd-tests/lib/libc/gen/
H A Dt_dir.c144 "Check telldir(3) for memory leakage (PR lib/24324)"); in ATF_TC_HEAD()
/freebsd/tests/sys/fs/fusefs/
H A Dutils.hh262 * to document the leakage, and provide a single point of suppression
/freebsd/contrib/llvm-project/llvm/lib/Target/M68k/MCTargetDesc/
H A DM68kAsmBackend.cpp57 // Specifically ignore overflow/underflow as long as the leakage is in applyFixup()
/freebsd/sys/dev/ath/ath_hal/ar9002/
H A Dar9285_cal.c163 /* Carrier leakage Calibration fix */
/freebsd/sys/contrib/device-tree/src/arm64/rockchip/
H A Drk3588-base.dtsi2723 cpub0_leakage: cpu-leakage@17 {
2727 cpub1_leakage: cpu-leakage@18 {
2731 cpul_leakage: cpu-leakage@19 {
2735 log_leakage: log-leakage@1a {
2739 gpu_leakage: gpu-leakage@1b {
2748 npu_leakage: npu-leakage@28 {
2752 codec_leakage: codec-leakage@29 {
H A Drk3399-gru-chromebook.dtsi470 * Note strange pullup enable. Apparently this avoids leakage but
H A Drk3399-base.dtsi1511 cpub_leakage: cpu-leakage@17 {
1514 gpu_leakage: gpu-leakage@18 {
1517 center_leakage: center-leakage@19 {
1520 cpul_leakage: cpu-leakage@1a {
1523 logic_leakage: logic-leakage@1b {
/freebsd/sys/contrib/device-tree/src/arm/allwinner/
H A Dsun8i-a83t-bananapi-m3.dts331 * avoid any leakage or mismatch.
/freebsd/crypto/libecc/
H A DREADME.md1063 secret leakage resistance into a very complex problem, especially when writing
1069 * Any shared hardware resource can become a leakage source (the caches, the
1072 leakage sources.
1106 operations are (tentatively) used to limit leakage of different operations,
1119 where the library runs with leakage assessments. Because of the very nature of
1120 C code and CPU microarchitectural details, it is very complex without such a leakage
/freebsd/crypto/openssl/test/
H A Dstack_test.c214 /* free -- we rely on the debug malloc to detect leakage here */ in test_uchar_stack()
/freebsd/contrib/llvm-project/compiler-rt/lib/safestack/
H A Dsafestack.cpp86 // leakage of the stack pointer can be prevented. Currently, libc can leak the
/freebsd/crypto/openssl/crypto/dsa/
H A Ddsa_ossl.c310 * small timing information leakage. We then choose the sum that is in dsa_sign_setup()
/freebsd/sys/ofed/drivers/infiniband/ulp/ipoib/
H A Dipoib.h236 * leakage may occur. Therefore, it is good programming practice to tear down a
/freebsd/sys/contrib/device-tree/src/arm/aspeed/
H A Daspeed-bmc-facebook-harma.dts578 "leakage-detect-alert","","","",
/freebsd/sys/contrib/device-tree/src/arm/ti/omap/
H A Domap3-pandora-common.dtsi216 * disabling this regulator causes current leakage, and LCD flicker

123