Skip to content

Commit b4540e1

Browse files
committed
Explain power management problems in the PTP context
Signed-off-by: Florian Kauer <florian.kauer@linutronix.de>
1 parent 722928b commit b4540e1

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

source/timesync.rst

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -280,6 +280,29 @@ single instance (per network interface) of both the daemons is running at a
280280
time. ``pgrep`` can be useful to ensure only one instance of a particular
281281
process is running. Look at pgrep(1) manpage for more details.
282282

283+
Check power management settings
284+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
285+
286+
Several power management mechanisms exist that set components
287+
(such as the CPU, NIC and the PCIe bus between CPU and NIC)
288+
into modes where the power consumption is reduced if they are
289+
inactive for some time. However, in these modes it can take
290+
100 µs or more until they are fully active again.
291+
292+
In such a situation, phc2sys might report timeouts or you might
293+
measure a large difference between System clock and PHC even
294+
though phc2sys reports only small offsets.
295+
296+
If your BIOS supports it, enable the Intel(R) Time Coordinated
297+
Computing (TCC) mode that optimizes/disables several power management
298+
mechanisms for usage in real-time applications. Otherwise,
299+
you should at least disable PCIe ASPM, e.g. with
300+
301+
.. code:: console
302+
303+
echo performance > /sys/module/pcie_aspm/parameters/policy
304+
305+
283306
References
284307
----------
285308

0 commit comments

Comments
 (0)