Home
last modified time | relevance | path

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

123456

/linux-6.12.1/include/trace/events/
Dcontext_tracking.h28 * user_enter - called when the kernel resumes to userspace
31 * This event occurs when the kernel resumes to userspace after
/linux-6.12.1/drivers/gpu/drm/xe/
Dxe_vm_doc.h245 * memory and kick the rebind worker which resumes all the engines execution.
472 * execs, execs, and resumes in the rebind worker we use both the VMs and
518 * 5. In compute mode, resumes in rebind worker shall wait on last rebind fence
520 * 6. In compute mode, resumes in rebind worker shall wait on the
535 * 4. Compute mode engine resumes are blocked behind any existing jobs from
/linux-6.12.1/Documentation/driver-api/firmware/
Dfirmware_cache.rst5 When Linux resumes from suspend some device drivers require firmware lookups to
/linux-6.12.1/arch/x86/kvm/vmx/
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
/linux-6.12.1/Documentation/devicetree/bindings/iio/proximity/
Ddevantech-srf04.yaml59 When the device gets suspended it's switched off and when it resumes
/linux-6.12.1/tools/power/pm-graph/config/
Dstandby-dev.cfg54 # Run two suspend/resumes back to back (default: false)
Dfreeze-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
Dstandby.cfg54 # Run two suspend/resumes back to back (default: false)
Dsuspend-dev.cfg54 # Run two suspend/resumes back to back (default: false)
Dsuspend-x2-proc.cfg54 # Run two suspend/resumes back to back (default: false)
Dsuspend.cfg54 # Run two suspend/resumes back to back (default: false)
Dstandby-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
Dfreeze-dev.cfg54 # Run two suspend/resumes back to back (default: false)
Dfreeze.cfg54 # Run two suspend/resumes back to back (default: false)
Dsuspend-callgraph.cfg55 # Run two suspend/resumes back to back (default: false)
Dexample.cfg82 # Run two suspend/resumes back to back and display in the same timeline (default: false)
Dcustom-timeline-functions.cfg37 # Run two suspend/resumes back to back (default: false)
/linux-6.12.1/Documentation/ABI/testing/
Ddebugfs-cros-ec42 where a system failed to go into S0ix. When the system resumes,
/linux-6.12.1/drivers/gpu/drm/xe/tests/
Dxe_kunit_helpers.c105 * This function makes sure that device is not wedged and then resumes it
/linux-6.12.1/sound/soc/sof/
Dsof-client-ipc-kernel-injector.c147 * type are enough to ensure that the parent SOF device resumes to bring the DSP
/linux-6.12.1/arch/s390/kernel/
Dwti.c149 * resumes when hypervisor decides to dispatch CPU in wti_thread_fn()
/linux-6.12.1/sound/pci/
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!),
/linux-6.12.1/tools/power/pm-graph/
DREADME189 successive suspend/resumes.
204 suspend/resumes over an extended period and analyze the behavior. This can be
376 # Suspend/Resume x2: run 2 suspend/resumes back to back (def: false)
/linux-6.12.1/arch/riscv/mm/
Dcacheflush.c42 * execution resumes on each hart.
/linux-6.12.1/drivers/gpu/drm/
Ddrm_modeset_helper.c226 * drm_atomic_helper_resume(), resumes fbdev if used and enables output polling

123456