Searched full:phases (Results 1 – 25 of 27) sorted by relevance
12
/Documentation/driver-api/pm/ |
D | devices.rst | 134 they are called in phases for every device, respecting the parent-child 266 System Power Management Phases 269 Suspending or resuming the system is done in several phases. Different phases 274 callbacks. The various phases always run after tasks have been frozen and 275 before they are unfrozen. Furthermore, the ``*_noirq`` phases run at a time 279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods 316 the phases are: ``prepare``, ``suspend``, ``suspend_late``, ``suspend_noirq``. 323 suspend-related phases, during the ``prepare`` phase the device 342 ``suspend_noirq`` phases as well as all of the corresponding phases of 389 "quiesce device" and "save device state" phases, in which cases [all …]
|
/Documentation/devicetree/bindings/mmc/ |
D | rockchip-dw-mshc.yaml | 75 to control the clock phases, "ciu-sample" is required for tuning 85 low speeds or in case where all phases work at tuning time. 88 rockchip,desired-num-phases:
|
/Documentation/hwmon/ |
D | pmbus-core.rst | 169 support multiple phases, the phase parameter can be ignored. If the chip 170 supports multiple phases, a phase value of 0xff indicates all phases. 210 If the chip does not support multiple phases, the phase parameter is 211 ignored. Otherwise, a phase value of 0xff selects all phases. 220 not support multiple phases, the phase parameter is ignored. Otherwise, a phase 221 value of 0xff selects all phases.
|
D | mp2975.rst | 60 - 'k' is number of configured phases (from 1 to 8); 63 - indexes 2*n+1 ... 2*n + k for phases.
|
D | tps53679.rst | 56 output channels and up to 8 phases per channel.
|
/Documentation/power/ |
D | pci.rst | 431 management callbacks for this purpose. They are executed in phases such that 433 belonging to the given subsystem before the next phase begins. These phases 440 be preserved, such as one of the ACPI sleep states S1-S3, the phases are: 444 The following PCI bus type's callbacks, respectively, are used in these phases:: 509 S1-S3, into the working state (ACPI S0), the phases are: 514 phases:: 562 to be free) in the following three phases: 573 The other two phases, however, are different. 591 back to the fully functional state and this is done in the following phases: 617 three phases: [all …]
|
D | suspend-and-interrupts.rst | 38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
|
/Documentation/crypto/ |
D | intro.rst | 57 following phases that are reflected in the API calls applicable to such
|
/Documentation/admin-guide/mm/ |
D | memory-hotplug.rst | 42 Phases of memory hotplug 45 There are 2 phases in Memory Hotplug: 74 phases can be execute in seamless way.)
|
/Documentation/driver-api/driver-model/ |
D | overview.rst | 69 The above abstraction prevents unnecessary pain during transitional phases.
|
/Documentation/admin-guide/pm/ |
D | suspend-flows.rst | 79 Devices are suspended in four phases called *prepare*, *suspend*, 139 Devices are resumed in four phases called *noirq resume*, *early resume*,
|
/Documentation/devicetree/bindings/power/supply/ |
D | rohm,bd99954.yaml | 31 # The BD99954 data sheet divides charging to three phases.
|
/Documentation/timers/ |
D | timekeeping.rst | 41 the counter register is read in two phases on the bus lowest 16 bits first
|
/Documentation/filesystems/ |
D | sharedsubtree.rst | 950 The overall algorithm breaks the operation into 3 phases: (look at 954 2. commit phases. 955 3. abort phases.
|
/Documentation/devicetree/bindings/arm/ |
D | idle-states.yaml | 54 The following diagram depicts the CPU execution phases and related timing 67 Diagram 1: CPU idle state execution phases
|
/Documentation/process/ |
D | 1.Intro.rst | 18 release cycle, and the mechanics of the merge window. The various phases in
|
/Documentation/scsi/ |
D | st.rst | 311 max_sg_segs) and the number of segments used in phases 1 and 2 316 is smaller than the number of segments used in phases 1 and 2,
|
D | ChangeLog.sym53c8xx | 97 * Simpler handling of illegal phases and data overrun from
|
/Documentation/admin-guide/ |
D | initrd.rst | 14 initrd is mainly designed to allow system startup to occur in two phases,
|
/Documentation/RCU/Design/Memory-Ordering/ |
D | Tree-RCU-Memory-Ordering.rst | 34 two phases, one of which is executed before the grace period and 314 section with the various phases of grace-period initialization.
|
/Documentation/driver-api/ |
D | xillybus.rst | 331 bootstrap process is done in three phases:
|
/Documentation/RCU/ |
D | whatisRCU.rst | 68 "reclamation" phases. The removal phase removes references to data items 80 Splitting the update into removal and reclamation phases permits the
|
D | checklist.rst | 111 readers see valid data at all phases of the update.
|
/Documentation/scheduler/ |
D | sched-deadline.rst | 325 A typical real-time task is composed of a repetition of computation phases 711 the preliminary phases of the merge and we really seek feedback that would
|
/Documentation/networking/dsa/ |
D | dsa.rst | 326 prepare/abort/commit phases are often simplified into a prepare phase which
|
12