hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PCI/PM: Wrap long lines in documentation 

Documentation/power/pci.rst is wrapped to fit in 80 columns, but directory
structure changes made a few lines longer.  Wrap them so they all fit in 80
columns again.

Link: https://lore.kernel.org/r/20191014230016.240912-7-helgaas@kernel.org
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
Bjorn Helgaas 2019-10-08 15:25:23 -05:00
parent 85a9b0507d
commit b64cf7a171
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
Documentation/power/pci.rst
View File

@ -426,12 +426,12 @@ pm->runtime_idle() callback.
2.4. System-Wide Power Transitions 2.4. System-Wide Power Transitions
---------------------------------- ----------------------------------
There are a few different types of system-wide power transitions, described in There are a few different types of system-wide power transitions, described in
Documentation/driver-api/pm/devices.rst. Each of them requires devices to be handled Documentation/driver-api/pm/devices.rst. Each of them requires devices to be
in a specific way and the PM core executes subsystem-level power management handled in a specific way and the PM core executes subsystem-level power
callbacks for this purpose. They are executed in phases such that each phase management callbacks for this purpose. They are executed in phases such that
involves executing the same subsystem-level callback for every device belonging each phase involves executing the same subsystem-level callback for every device
to the given subsystem before the next phase begins. These phases always run belonging to the given subsystem before the next phase begins. These phases
after tasks have been frozen. always run after tasks have been frozen.
2.4.1. System Suspend 2.4.1. System Suspend
^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
@ -636,12 +636,12 @@ System restore requires a hibernation image to be loaded into memory and the
pre-hibernation memory contents to be restored before the pre-hibernation system pre-hibernation memory contents to be restored before the pre-hibernation system
activity can be resumed. activity can be resumed.
As described in Documentation/driver-api/pm/devices.rst, the hibernation image is loaded As described in Documentation/driver-api/pm/devices.rst, the hibernation image
into memory by a fresh instance of the kernel, called the boot kernel, which in is loaded into memory by a fresh instance of the kernel, called the boot kernel,
turn is loaded and run by a boot loader in the usual way. After the boot kernel which in turn is loaded and run by a boot loader in the usual way. After the
has loaded the image, it needs to replace its own code and data with the code boot kernel has loaded the image, it needs to replace its own code and data with
and data of the "hibernated" kernel stored within the image, called the image the code and data of the "hibernated" kernel stored within the image, called the
kernel. For this purpose all devices are frozen just like before creating image kernel. For this purpose all devices are frozen just like before creating
the image during hibernation, in the the image during hibernation, in the
prepare, freeze, freeze_noirq prepare, freeze, freeze_noirq
@ -691,8 +691,8 @@ controlling the runtime power management of their devices.
At the time of this writing there are two ways to define power management At the time of this writing there are two ways to define power management
callbacks for a PCI device driver, the recommended one, based on using a callbacks for a PCI device driver, the recommended one, based on using a
dev_pm_ops structure described in Documentation/driver-api/pm/devices.rst, and the dev_pm_ops structure described in Documentation/driver-api/pm/devices.rst, and
"legacy" one, in which the .suspend(), .suspend_late(), .resume_early(), and the "legacy" one, in which the .suspend(), .suspend_late(), .resume_early(), and
.resume() callbacks from struct pci_driver are used. The legacy approach, .resume() callbacks from struct pci_driver are used. The legacy approach,
however, doesn't allow one to define runtime power management callbacks and is however, doesn't allow one to define runtime power management callbacks and is
not really suitable for any new drivers. Therefore it is not covered by this not really suitable for any new drivers. Therefore it is not covered by this