| /linux-2.6.39/Documentation/power/ |
| D | devices.txt | 136 they are called in phases for every device, respecting the parent-child
243 Suspending or resuming the system is done in several phases. Different phases
248 various phases always run after tasks have been frozen and before they are
249 unfrozen. Furthermore, the *_noirq phases run at a time when IRQ handlers have
252 All phases use bus, type, or class callbacks (that is, methods defined in
271 When the system goes into the standby or memory sleep state, the phases are:
279 time.) Unlike the other suspend-related phases, during the prepare
306 At the end of these phases, drivers should have stopped all I/O transactions
326 When resuming from standby or memory sleep, the phases are:
353 At the end of these phases, drivers should be as functional as they were before
[all …]
|
| D | pci.txt | 422 callbacks for this purpose. They are executed in phases such that each phase
424 to the given subsystem before the next phase begins. These phases always run
430 be preserved, such as one of the ACPI sleep states S1-S3, the phases are:
434 The following PCI bus type's callbacks, respectively, are used in these phases:
498 S1-S3, into the working state (ACPI S0), the phases are:
503 phases:
550 to be free) in the following three phases:
561 The other two phases, however, are different.
579 back to the fully functional state and this is done in the following phases:
605 three phases:
[all …]
|
| /linux-2.6.39/drivers/scsi/ |
| D | g_NCR5380.c | 883 …for (i = 0; (phases[i].value != PHASE_UNKNOWN) && (phases[i].value != (status & PHASE_MASK)); ++i); in generic_NCR5380_proc_info()
884 PRINTP("Phase %s\n" ANDP phases[i].name); in generic_NCR5380_proc_info()
|
| D | NCR5380.c | 359 } phases[] __maybe_unused = { variable
470 …for (i = 0; (phases[i].value != PHASE_UNKNOWN) && (phases[i].value != (status & PHASE_MASK)); ++i); in NCR5380_print_phase()
471 printk("scsi%d : phase %s\n", instance->host_no, phases[i].name); in NCR5380_print_phase()
|
| D | sun3_NCR5380.c | 599 } phases[] = { variable
621 for (i = 0; (phases[i].value != PHASE_UNKNOWN) && in NCR5380_print_phase()
622 (phases[i].value != (status & PHASE_MASK)); ++i); in NCR5380_print_phase()
623 printk(KERN_DEBUG "scsi%d: phase %s\n", HOSTNO, phases[i].name); in NCR5380_print_phase()
|
| D | atari_NCR5380.c | 599 } phases[] = { variable
622 for (i = 0; (phases[i].value != PHASE_UNKNOWN) && in NCR5380_print_phase()
623 (phases[i].value != (status & PHASE_MASK)); ++i) in NCR5380_print_phase()
625 printk(KERN_DEBUG "scsi%d: phase %s\n", HOSTNO, phases[i].name); in NCR5380_print_phase()
|
| D | sym53c416.c | 201 enum phases enum
|
| /linux-2.6.39/drivers/scsi/arm/ |
| D | fas216.c | 250 static const char *phases[] = { in fas216_bus_phase() local
257 return phases[stat & STAT_BUSMASK]; in fas216_bus_phase()
262 static const char *phases[] = { in fas216_drv_phase() local
276 if (info->scsi.phase < ARRAY_SIZE(phases) && in fas216_drv_phase()
277 phases[info->scsi.phase]) in fas216_drv_phase()
278 return phases[info->scsi.phase]; in fas216_drv_phase()
|
| /linux-2.6.39/Documentation/driver-model/ |
| D | overview.txt | 64 This abstraction is prevention of unnecessary pain during transitional phases.
|
| /linux-2.6.39/Documentation/ |
| D | memory-hotplug.txt | 58 There are 2 phases in Memory Hotplug.
86 phases can be execute in seamless way.)
|
| D | initrd.txt | 14 initrd is mainly designed to allow system startup to occur in two phases,
|
| D | feature-removal-schedule.txt | 103 different phases of swsusp "sleep" transitions; and userspace policy
|
| /linux-2.6.39/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 475 * Now determine what phases the host wants us
599 * Data phases on the bus are from the
656 * Main loop for information transfer phases. Wait for the
921 * As a target, we control the phases,
1344 * For data-in phases, wait for any pending acks from the
1346 * send Ignore Wide Residue messages for data-in phases.
|
| D | aic7xxx.reg | 130 * Possible phases in SCSISIGI
161 * Possible phases to write into SCSISIG0
|
| D | aic79xx.seq | 845 * Main loop for information transfer phases. Wait for the
1754 * For data-in phases, wait for any pending acks from the
1756 * send Ignore Wide Residue messages for data-in phases.
2121 * phases that are typically caused by CRC errors in status packet
|
| D | aic79xx.reg | 1745 * Possible phases to write into SCSISIG0
1776 * Possible phases in SCSISIGI
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | sharedsubtree.txt | 896 The overall algorithm breaks the operation into 3 phases: (look at
900 2. commit phases.
901 3. abort phases.
|
| /linux-2.6.39/drivers/scsi/aic7xxx_old/ |
| D | aic7xxx.reg | 112 * Possible phases in SCSISIGI
141 * Possible phases to write into SCSISIG0
|
| D | aic7xxx.seq | 264 * for "in" phases
286 * Main loop for information transfer phases. Wait for the target
|
| /linux-2.6.39/Documentation/scsi/ |
| D | st.txt | 227 max_sg_segs) and the number of segments used in phases 1 and 2
232 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
|
| /linux-2.6.39/Documentation/RCU/ |
| D | whatisRCU.txt | 50 "reclamation" phases. The removal phase removes references to data items
62 Splitting the update into removal and reclamation phases permits the
|
| D | checklist.txt | 91 readers see valid data at all phases of the update.
|
| /linux-2.6.39/Documentation/development-process/ |
| D | 1.Intro | 24 the mechanics of the merge window. The various phases in the patch
|
| /linux-2.6.39/Documentation/cgroups/ |
| D | memory.txt | 95 The memory controller implementation has been divided into phases. These
|