docs(linux): Power_Management: Put latency constraint in correct section

Documentation details a resume latency constraint that would allow a
device to not be powered off during suspend/resume in the device
constraint section. This puts the resume latency constraint into the
correct section.

Signed-off-by: Kendall Willis <[email protected]>

Author: kwillis01

source/linux/Foundational_Components/Power_Management/pm_sw_arch.rst

@@ -174,11 +174,6 @@ are required.
    Some devices may disable the wakeup property by default. These can be enabled via
    the sysfs interface (e.g., :file:`/sys/bus/platform/devices/\*/power/wakeup`)
 
-If a device wants to put a constraint to be not powered-off, it can use the Linux
-QoS framework and set the DEV_PM_QOS_RESUME_LATENCY equal to 0.
-An example is shown in the following RemoteProc driver:
-https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/ti_k3_r5_remoteproc.c?h=10.00.07#n535
-
 Resume Latency Constraint
 -------------------------
 
@@ -200,6 +195,11 @@ Default constraint is "no constraint", but it can be changed as shown in the exa
 Setting a resume latency constraint impacts the deepest low power mode system can enter.
 The various modes and their latencies are documented here: https://downloads.ti.com/tisci/esd/latest/2_tisci_msgs/pm/lpm.html#tisci-msg-lpm-set-latency-constraint
 
+If a device wants to put a constraint to be not powered-off, it can use the Linux
+QoS framework and set the DEV_PM_QOS_RESUME_LATENCY equal to 0.
+An example is shown in the following RemoteProc driver:
+https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/ti_k3_r5_remoteproc.c?h=10.00.07#n535
+
 .. note::
 
    The constraints need to be set before each system suspend as DM firmware clears all