summaryrefslogtreecommitdiffstats
path: root/Documentation/power/pci.txt
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-10-18 08:12:27 -0400
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2016-10-24 06:12:35 -0400
commit8c27ceff3604b249a9efafbd1bd8b141b79e619d (patch)
tree82e4ab0c2825fa25c3168e648268883c0b23ee30 /Documentation/power/pci.txt
parent9d85025b0418163fae079c9ba8f8445212de8568 (diff)
docs: fix locations of several documents that got moved
The previous patch renamed several files that are cross-referenced along the Kernel documentation. Adjust the links to point to the right places. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/power/pci.txt')
-rw-r--r--Documentation/power/pci.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/power/pci.txt b/Documentation/power/pci.txt
index 44558882aa60..85c746cbab2c 100644
--- a/Documentation/power/pci.txt
+++ b/Documentation/power/pci.txt
@@ -8,7 +8,7 @@ management. Based on previous work by Patrick Mochel <mochel@transmeta.com>
8 8
9This document only covers the aspects of power management specific to PCI 9This document only covers the aspects of power management specific to PCI
10devices. For general description of the kernel's interfaces related to device 10devices. For general description of the kernel's interfaces related to device
11power management refer to Documentation/power/devices.txt and 11power management refer to Documentation/power/admin-guide/devices.rst and
12Documentation/power/runtime_pm.txt. 12Documentation/power/runtime_pm.txt.
13 13
14--------------------------------------------------------------------------- 14---------------------------------------------------------------------------
@@ -417,7 +417,7 @@ pm->runtime_idle() callback.
4172.4. System-Wide Power Transitions 4172.4. System-Wide Power Transitions
418---------------------------------- 418----------------------------------
419There are a few different types of system-wide power transitions, described in 419There are a few different types of system-wide power transitions, described in
420Documentation/power/devices.txt. Each of them requires devices to be handled 420Documentation/power/admin-guide/devices.rst. Each of them requires devices to be handled
421in a specific way and the PM core executes subsystem-level power management 421in a specific way and the PM core executes subsystem-level power management
422callbacks for this purpose. They are executed in phases such that each phase 422callbacks for this purpose. They are executed in phases such that each phase
423involves executing the same subsystem-level callback for every device belonging 423involves executing the same subsystem-level callback for every device belonging
@@ -623,7 +623,7 @@ System restore requires a hibernation image to be loaded into memory and the
623pre-hibernation memory contents to be restored before the pre-hibernation system 623pre-hibernation memory contents to be restored before the pre-hibernation system
624activity can be resumed. 624activity can be resumed.
625 625
626As described in Documentation/power/devices.txt, the hibernation image is loaded 626As described in Documentation/power/admin-guide/devices.rst, the hibernation image is loaded
627into memory by a fresh instance of the kernel, called the boot kernel, which in 627into memory by a fresh instance of the kernel, called the boot kernel, which in
628turn is loaded and run by a boot loader in the usual way. After the boot kernel 628turn is loaded and run by a boot loader in the usual way. After the boot kernel
629has loaded the image, it needs to replace its own code and data with the code 629has loaded the image, it needs to replace its own code and data with the code
@@ -677,7 +677,7 @@ controlling the runtime power management of their devices.
677 677
678At the time of this writing there are two ways to define power management 678At the time of this writing there are two ways to define power management
679callbacks for a PCI device driver, the recommended one, based on using a 679callbacks for a PCI device driver, the recommended one, based on using a
680dev_pm_ops structure described in Documentation/power/devices.txt, and the 680dev_pm_ops structure described in Documentation/power/admin-guide/devices.rst, and the
681"legacy" one, in which the .suspend(), .suspend_late(), .resume_early(), and 681"legacy" one, in which the .suspend(), .suspend_late(), .resume_early(), and
682.resume() callbacks from struct pci_driver are used. The legacy approach, 682.resume() callbacks from struct pci_driver are used. The legacy approach,
683however, doesn't allow one to define runtime power management callbacks and is 683however, doesn't allow one to define runtime power management callbacks and is
@@ -1046,5 +1046,5 @@ PCI Local Bus Specification, Rev. 3.0
1046PCI Bus Power Management Interface Specification, Rev. 1.2 1046PCI Bus Power Management Interface Specification, Rev. 1.2
1047Advanced Configuration and Power Interface (ACPI) Specification, Rev. 3.0b 1047Advanced Configuration and Power Interface (ACPI) Specification, Rev. 3.0b
1048PCI Express Base Specification, Rev. 2.0 1048PCI Express Base Specification, Rev. 2.0
1049Documentation/power/devices.txt 1049Documentation/power/admin-guide/devices.rst
1050Documentation/power/runtime_pm.txt 1050Documentation/power/runtime_pm.txt