Home
last modified time | relevance | path

Searched full:depicts (Results 1 – 15 of 15) sorted by relevance

/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-opal.txt22 and depend on the specific hardware implementation. The example below depicts
/linux/drivers/scsi/isci/
H A Disci.h400 * enum sci_io_status - This enumeration depicts all of the possible IO
433 * enum sci_task_status - This enumeration depicts all of the possible task
H A Dsas.h208 * struct sci_sas_address - This structure depicts how a SAS address is
H A Dunsolicited_frame_control.h68 * depicts actual header information received on the link.
H A Dremote_device.h163 * enum sci_remote_device_states - This enumeration depicts all the states
H A Dphy.h231 * enum sci_phy_counter_id - This enumeration depicts the various pieces of
H A Dhost.h213 * enum sci_controller_states - This enumeration depicts all the states
/linux/Documentation/admin-guide/
H A Dbug-bisect.rst14 instead: it depicts everything from start to finish while covering multiple
/linux/Documentation/arch/x86/
H A Damd-hfi.rst49 special scheduling behaviors. The below table depicts an example of thread
/linux/drivers/gpu/drm/i915/
H A Di915_vgpu.c219 * To give an example, the drawing below depicts one typical scenario after
/linux/Documentation/driver-api/acpi/
H A Dlinuxized-acpica.rst33 The following figure depicts the Linux ACPI subsystem where the ACPICA
/linux/Documentation/driver-api/nvdimm/
H A Dbtt.rst37 next arena). The following depicts the "On-disk" metadata layout::
/linux/Documentation/power/
H A Denergy-model.rst38 The figure below depicts an example of drivers (Arm-specific here, but the
/linux/Documentation/devicetree/bindings/cpu/
H A Didle-states.yaml74 The following diagram depicts the CPU execution phases and related timing
/linux/drivers/gpu/drm/
H A Ddrm_gpuvm.c171 * The following diagram depicts the basic relationships of existing GPU VA