Home
last modified time | relevance | path

Searched full:burn (Results 1 – 25 of 41) sorted by relevance

12

/linux/arch/sh/include/mach-ecovec24/mach/
H A Dpartner-jet-setup.txt13 LIST "Use the following command to burn the zImage to flash via JTAG:"
/linux/drivers/nvmem/
H A Dimx-ocotp.c256 * to physically burn out a fuse. in imx_ocotp_set_imx6_timing()
258 * - Minimum STROBE_READ i.e. the time to wait post OTP fuse burn before in imx_ocotp_set_imx6_timing()
269 * burn. in imx_ocotp_set_imx6_timing()
/linux/arch/arm64/kernel/
H A Dsys_compat.c80 * the fires of hell burn in your belly if you break this rule. ;) in compat_arm_syscall()
/linux/arch/mips/kernel/
H A Dreset.c69 * We're going to burn some power running round the in machine_hang()
/linux/arch/sh/include/mach-kfr2r09/mach/
H A Dpartner-jet-setup.txt12 LIST "Use the following command to burn the zImage to flash via JTAG:"
/linux/Documentation/process/
H A Dmanagement-style.rst24 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/tools/thermal/tmon/
H A Dpid.c50 * 1. use CPU burn to produce open loop unit step response
/linux/Documentation/driver-api/usb/
H A Ddma.rst40 the time, that can really burn up resources on systems which use an
/linux/drivers/platform/mellanox/
H A Dmlxbf-bootctl.c307 * partially programmed (and thus invalid). The process is to burn the in secure_boot_fuse_state_show()
308 * eFuse for the new key start bit, burn the key eFuses, then burn the in secure_boot_fuse_state_show()
/linux/drivers/media/common/
H A Dttpci-eeprom.c9 would be possible to write routines to burn a different (encoded)
/linux/Documentation/devicetree/bindings/iio/adc/
H A Dadi,ad7192.yaml100 path are enabled. When BURN = 0, the burnout currents are disabled.
/linux/Documentation/driver-api/early-userspace/
H A Dearly_userspace_support.rst119 If kinit doesn't meet your current needs and you've got bytes to burn,
/linux/Documentation/admin-guide/
H A Drtc.rst70 burn up 100% CPU by polling gettimeofday etc. etc.
/linux/arch/sparc/kernel/
H A Dentry.S1238 WRITE_PAUSE ! burn them cycles
1255 WRITE_PAUSE ! burn baby burn
/linux/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-bytedance-g220a.dts103 event-burn-in-signal {
104 label = "burn-in";
/linux/tools/testing/selftests/kvm/
H A Drseq_test.c58 * burn a lot cycles and the test will take longer than normal to in next_cpu()
/linux/fs/bcachefs/
H A Dbuckets.h53 * So now we use bit_spin_lock(), with fun games since we can't burn a whole
/linux/Documentation/core-api/
H A Dworkqueue.rst274 again before finishing. w1 and w2 burn CPU for 5ms then sleep for
327 5 w1 and w2 start and burn CPU
/linux/security/integrity/evm/
H A Devm_crypto.c441 /* burn the original key contents */ in evm_init_key()
/linux/arch/parisc/kernel/
H A Dhead.S160 /* Load the return address...er...crash 'n burn */
/linux/Documentation/translations/zh_CN/core-api/
H A Dworkqueue.rst279 5 w1 and w2 start and burn CPU
/linux/arch/arm/include/asm/hardware/
H A Dsa1111.h49 * Pour gasoline over them and finally burn them. Now think about coding.
/linux/drivers/regulator/
H A Dhi6421-regulator.c374 * more LDO or BUCKs simultaneously, or it may burn the chip. in hi6421_regulator_enable()
/linux/drivers/input/touchscreen/
H A Dmxs-lradc-ts.c406 * start a dummy conversion to burn time to settle the signals in mxs_lradc_complete_touch_event()
/linux/Documentation/input/joydev/
H A Djoystick.rst581 :A: Yes, it is possible, but it'll burn your serial port or the pad. It

12