tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: devices.rst: better reference documentation docs

There's no need to use either :file: or :doc: tags for documentation,
as automarkup.py automatically converts Documentation/*.rst into
a cross-reference.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Link: https://lore.kernel.org/r/5d9c9949a104d10b537a2d780bccad69a2dc58f9.1623824363.git.mchehab+huawei@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Mauro Carvalho Chehab and committed by
Jonathan Corbet 559a66b8 a557f67c

+4 -4
+4 -4
Documentation/driver-api/pm/devices.rst
··· 217 217 flag is clear. 218 218 219 219 For more information about the runtime power management framework, refer to 220 - :file:`Documentation/power/runtime_pm.rst`. 220 + Documentation/power/runtime_pm.rst. 221 221 222 222 223 223 Calling Drivers to Enter and Leave System Sleep States ··· 655 655 actions that either require user space to be available, or at least won't 656 656 interfere with user space. 657 657 658 - For details refer to :doc:`notifiers`. 658 + For details refer to Documentation/driver-api/pm/notifiers.rst. 659 659 660 660 661 661 Device Low-Power (suspend) States ··· 726 726 727 727 Devices may be defined as IRQ-safe which indicates to the PM core that their 728 728 runtime PM callbacks may be invoked with disabled interrupts (see 729 - :file:`Documentation/power/runtime_pm.rst` for more information). If an 729 + Documentation/power/runtime_pm.rst for more information). If an 730 730 IRQ-safe device belongs to a PM domain, the runtime PM of the domain will be 731 731 disallowed, unless the domain itself is defined as IRQ-safe. However, it 732 732 makes sense to define a PM domain as IRQ-safe only if all the devices in it ··· 805 805 -------------------------------------------- 806 806 807 807 During system-wide resume from a sleep state it's easiest to put devices into 808 - the full-power state, as explained in :file:`Documentation/power/runtime_pm.rst`. 808 + the full-power state, as explained in Documentation/power/runtime_pm.rst. 809 809 [Refer to that document for more information regarding this particular issue as 810 810 well as for information on the device runtime power management framework in 811 811 general.] However, it often is desirable to leave devices in suspend after