Searched full:burn (Results 1 – 25 of 50) sorted by relevance
12
| /Linux-v6.1/drivers/platform/mellanox/ |
| D | mlxbf-bootctl.c | 212 * partially programmed (and thus invalid). The process is to burn the in secure_boot_fuse_state_show()
213 * eFuse for the new key start bit, burn the key eFuses, then burn the in secure_boot_fuse_state_show()
|
| /Linux-v6.1/arch/sh/include/mach-ecovec24/mach/ |
| D | partner-jet-setup.txt | 13 LIST "Use the following command to burn the zImage to flash via JTAG:"
|
| /Linux-v6.1/arch/arm64/kernel/ |
| D | sys_compat.c | 80 * the fires of hell burn in your belly if you break this rule. ;) in compat_arm_syscall()
|
| /Linux-v6.1/Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7192.yaml | 75 path are enabled. When BURN = 0, the burnout currents are disabled.
|
| /Linux-v6.1/arch/mips/kernel/ |
| D | reset.c | 69 * We're going to burn some power running round the in machine_hang()
|
| /Linux-v6.1/drivers/nvmem/ |
| D | imx-ocotp.c | 263 * to physically burn out a fuse. in imx_ocotp_set_imx6_timing()
265 * - Minimum STROBE_READ i.e. the time to wait post OTP fuse burn before in imx_ocotp_set_imx6_timing()
276 * burn. in imx_ocotp_set_imx6_timing()
|
| /Linux-v6.1/arch/sh/include/mach-kfr2r09/mach/ |
| D | partner-jet-setup.txt | 12 LIST "Use the following command to burn the zImage to flash via JTAG:"
|
| /Linux-v6.1/Documentation/process/ |
| D | management-style.rst | 24 People", and NOT read it. Burn it, it's a great symbolic gesture.
148 remember not to burn any bridges, bomb any innocent villagers, or
|
| /Linux-v6.1/tools/thermal/tmon/ |
| D | pid.c | 50 * 1. use CPU burn to produce open loop unit step response
|
| /Linux-v6.1/Documentation/translations/zh_CN/core-api/ |
| D | workqueue.rst | 265 5 w1 and w2 start and burn CPU
|
| /Linux-v6.1/Documentation/core-api/ |
| D | workqueue.rst | 260 again before finishing. w1 and w2 burn CPU for 5ms then sleep for
313 5 w1 and w2 start and burn CPU
|
| /Linux-v6.1/drivers/media/common/ |
| D | ttpci-eeprom.c | 9 would be possible to write routines to burn a different (encoded)
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| D | dma.rst | 40 the time, that can really burn up resources on systems which use an
|
| /Linux-v6.1/Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 119 If kinit doesn't meet your current needs and you've got bytes to burn,
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | rtc.rst | 70 burn up 100% CPU by polling gettimeofday etc. etc.
|
| /Linux-v6.1/kernel/ |
| D | scftorture.c | 253 // Update statistics and occasionally burn up mass quantities of CPU time,
254 // if told to do so via scftorture.longwait. Otherwise, occasionally burn
|
| /Linux-v6.1/arch/sparc/kernel/ |
| D | entry.S | 1238 WRITE_PAUSE ! burn them cycles
1255 WRITE_PAUSE ! burn baby burn
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | aspeed-bmc-bytedance-g220a.dts | 103 event-burn-in-signal {
104 label = "burn-in";
|
| /Linux-v6.1/tools/testing/selftests/kvm/ |
| D | rseq_test.c | 63 * burn a lot cycles and the test will take longer than normal to in next_cpu()
|
| /Linux-v6.1/security/integrity/evm/ |
| D | evm_crypto.c | 423 /* burn the original key contents */ in evm_init_key()
|
| /Linux-v6.1/block/ |
| D | bio-integrity.c | 452 * kintegrityd won't block much but may burn a lot of CPU cycles. in bio_integrity_init()
|
| /Linux-v6.1/arch/arm/include/asm/hardware/ |
| D | sa1111.h | 49 * Pour gasoline over them and finally burn them. Now think about coding.
|
| /Linux-v6.1/arch/parisc/kernel/ |
| D | head.S | 161 /* Load the return address...er...crash 'n burn */
|
| /Linux-v6.1/drivers/regulator/ |
| D | hi6421-regulator.c | 374 * more LDO or BUCKs simultaneously, or it may burn the chip. in hi6421_regulator_enable()
|
| /Linux-v6.1/tools/testing/selftests/cgroup/ |
| D | test_cpu.c | 536 * that burn a CPU for a few seconds.
|
12
