Home
last modified time | relevance | path

Searched full:resumes (Results 1 – 25 of 159) sorted by relevance

1234567

/openbmc/linux/include/trace/events/
H A Dcontext_tracking.h28 * user_enter - called when the kernel resumes to userspace
31 * This event occurs when the kernel resumes to userspace after
/openbmc/qemu/docs/devel/migration/
H A DCPR.rst23 resumes by running QEMU with the ``-incoming`` option. Because the
68 issued, then QEMU automatically resumes VM execution.
/openbmc/linux/block/
H A Dblk-pm.c185 * hook typically resumes the device and corrects runtime status
195 * runtime resumes. It does everything necessary to restart the queue.
/openbmc/qemu/tests/tcg/multiarch/gdbstub/
H A Dinterrupt.py57 "thread %d resumes correctly on interrupt" % thread.num)
/openbmc/linux/Documentation/driver-api/firmware/
H A Dfirmware_cache.rst5 When Linux resumes from suspend some device drivers require firmware lookups to
/openbmc/linux/Documentation/devicetree/bindings/iio/proximity/
H A Ddevantech-srf04.yaml59 When the device gets suspended it's switched off and when it resumes
/openbmc/linux/tools/power/pm-graph/config/
H A Dsuspend-x2-proc.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dsuspend.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dstandby.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dstandby-dev.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dfreeze.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dsuspend-dev.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dfreeze-dev.cfg54 # Run two suspend/resumes back to back (default: false)
H A Dstandby-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
H A Dfreeze-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
H A Dsuspend-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
H A Dexample.cfg82 # Run two suspend/resumes back to back and display in the same timeline (default: false)
/openbmc/linux/arch/x86/kvm/vmx/
H A Dvmenter.S172 * resumes below at 'vmx_vmexit' due to the VMCS HOST_RIP setting.
179 * If VMRESUME/VMLAUNCH and corresponding vmexit succeed, execution resumes at
/openbmc/linux/Documentation/ABI/testing/
H A Ddebugfs-cros-ec42 where a system failed to go into S0ix. When the system resumes,
/openbmc/u-boot/drivers/ddr/fsl/
H A Darm_ddr_gen3.c26 * 2 resumes from step 1 and continues to initialize
160 * get the clocks started. Step 2 resumes after reset signal is in fsl_ddr_set_memctl_regs()
/openbmc/linux/arch/riscv/mm/
H A Dcacheflush.c37 * execution resumes on each hart.
/openbmc/linux/sound/soc/sof/
H A Dsof-client-ipc-kernel-injector.c147 * type are enough to ensure that the parent SOF device resumes to bring the DSP
/openbmc/u-boot/arch/nios2/cpu/
H A Dexceptions.S74 /* Return address fixup: execution resumes by re-issue of
/openbmc/linux/arch/x86/kernel/
H A Dcet.c89 * continue. Otherwise when the CPU resumes from the instruction that just
/openbmc/linux/sound/pci/
H A Dazt3328.h162 /* bit 8; sure, this _pauses_ playback (later resumes at same spot!),
165 /* bit 9; sure, this _pauses_ playback (later resumes at same spot!),

1234567