.TP gives a paragraph with a hanging indentation. That looks odd, so
let's use the non-indented .LP paragraph instead.
Also, switch to .IP for bulleting instead of hand-drawn ASCII bullets.
Signed-off-by: Brian Norris <computersforpeace(a)gmail.com>
---
man/thermal-conf.xml.5 | 34 +++++++++++++++++-----------------
man/thermald.8 | 12 +++++-------
2 files changed, 22 insertions(+), 24 deletions(-)
diff --git a/man/thermal-conf.xml.5 b/man/thermal-conf.xml.5
index b59d86c32e93..5205d1dfcb88 100644
--- a/man/thermal-conf.xml.5
+++ b/man/thermal-conf.xml.5
@@ -31,28 +31,28 @@ $(TDCONFDIR)/etc/thermald/thermal-conf.xml
.SH DESCRIPTION
.B thermal-conf.xml
is a configuration file for the thermal daemon. It is used to configure thermal sensors,
zone and cooling devices.The location of this file depends on the configuration option
used during build time.
-.TP
+.LP
The terminology used in this file confirms to "Advanced Configuration and Power
Interface Specification". The ACPI thermal model is based around conceptual platform
regions called thermal zones that physically contain devices, thermal sensors, and cooling
controls. For example of a thermal zone can be a CPU or a laptop cover. A zone can contain
multiple sensors for monitoring temperature. A cooling device provides interface to reduce
the temperature of a source device, which causes increase in the temperature. An example
of a cooling device is a FAN or some Linux driver which can throttle the source device.
-.TP
+.LP
A thermal zone configuration includes one or more trip points. A trip point is a
temperature at which a cooling device needs to be activated.
-.TP
+.LP
A cooling device can be either active or passive. An example of an active device is a
FAN, which will not reduce performance at the cost of consuming more power and noise. A
passive device uses performance throttling to control temperature. In addition to cooling
devices present in the thermal sysfs, the following cooling devices are built into the
thermald, which can be used as valid cooling device type:
-.TP
- - rapl_controller
-.TP
- - intel_pstate
-.TP
- - cpufreq
+.IP \[bu] 2
+rapl_controller
+.IP \[bu]
+intel_pstate
+.IP \[bu]
+cpufreq
.TP
The thermal sysfs under Linux (/sys/class/thermal) provides a way to represent per
platform ACPI configuration. The kernel thermal governor uses this data to keep the
platform thermals under control. But there are some limitations, which thermald tries to
resolve. For example:
-.TP
-- If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used
to correct the behavior without change in BIOS.
-.TP
-- There may be thermal zones exposed by the thermal sysfs without associated cooling
actions. In this case thermal conf.xml can be used to tie the cooling devices to those
zones.
-.TP
-- The best cooling method may not be in the thermal sysfs. In this case thermal-conf.xml
can be used to bind a zone to an external cooling device.
-.TP
-- Specify thermal relationships. A zone can be influenced by multiple source devices with
varying degrees. In this case thermal-conf.xml can be used to define the relative
influence for apply compensation.
+.IP \[bu]
+If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used to
correct the behavior without change in BIOS.
+.IP \[bu]
+There may be thermal zones exposed by the thermal sysfs without associated cooling
actions. In this case thermal conf.xml can be used to tie the cooling devices to those
zones.
+.IP \[bu]
+The best cooling method may not be in the thermal sysfs. In this case thermal-conf.xml
can be used to bind a zone to an external cooling device.
+.IP \[bu]
+Specify thermal relationships. A zone can be influenced by multiple source devices with
varying degrees. In this case thermal-conf.xml can be used to define the relative
influence for apply compensation.
.SH FILE FORMAT
The configuration file format confirms to XML specifications. A set of tags defined to
define platform, sensors, zones, cooling devices and trip points.
diff --git a/man/thermald.8 b/man/thermald.8
index 9b49334c7b92..93dc5c35c072 100644
--- a/man/thermald.8
+++ b/man/thermald.8
@@ -33,26 +33,24 @@ thermald \- start Linux thermal daemon
.B thermald
is a Linux daemon used to prevent the overheating of platforms. This daemon monitors
temperature and applies compensation using available cooling methods.
-
+.LP
By default, it monitors CPU temperature using available CPU digital temperature sensors
and maintains CPU temperature under control, before HW takes aggressive correction
action.
-
-.TP
+.LP
Thermal daemon looks for thermal sensors and thermal cooling drivers in the Linux thermal
sysfs (/sys/class/thermal) and builds a
list of sensors and cooling drivers. Each of the thermal sensors can optionally be binded
to a cooling drivers by the in kernel
drivers. In this case the Linux kernel thermal core can directly take actions based on
the temperature trip points, for each sensor
and associated cooling device. For example a trip temperature X in a sensor can be
associates a cooling driver Y. So when
the sensor temperature = X, the cooling driver "Y" is activated.
-
+.LP
Thermal daemon allows to change this relationship or add new one via a thermal
configuration file (thermal-conf.xml). This
file is automatically created and used, if the platform has ACPI thermal relationship
table. If not this needs to be
manually configured.
-
+.LP
When there is a sensor, which has no associate cooling device, via configuration file or
thermal relationship table, then
this sensor is tested for relationship with CPU load dynamically upto maximum 3 times. If
there is no relationship, then
it is added to a black list of unbinded sensors and not tried again.
-
-.TP
+.LP
Optionally thermal daemon can act as an exclusive thermal controller by using thermal
sysfs and acting as a user space governor.
In this case kernel thermal core is not active and decision is taken by thermal daemon
only.
--
1.9.1
Show replies by date