brintos

brintos / linux-shallow public Read only

0
0
Text · 4.9 KiB · ca491ec Raw
153 lines · plain
1What:		/sys/class/powercap/2Date:		September 20133KernelVersion:	3.134Contact:	linux-pm@vger.kernel.org5Description:6		The powercap/ class sub directory belongs to the power cap7		subsystem. Refer to8		Documentation/power/powercap/powercap.rst for details.9 10What:		/sys/class/powercap/<control type>11Date:		September 201312KernelVersion:	3.1313Contact:	linux-pm@vger.kernel.org14Description:15		A <control type> is a unique name under /sys/class/powercap.16		Here <control type> determines how the power is going to be17		controlled. A <control type> can contain multiple power zones.18 19What:		/sys/class/powercap/<control type>/enabled20Date:		September 201321KernelVersion:	3.1322Contact:	linux-pm@vger.kernel.org23Description:24		This allows to enable/disable power capping for a "control type".25		This status affects every power zone using this "control_type.26 27What:		/sys/class/powercap/<control type>/<power zone>28Date:		September 201329KernelVersion:	3.1330Contact:	linux-pm@vger.kernel.org31Description:32		A power zone is a single or a collection of devices, which can33		be independently monitored and controlled. A power zone sysfs34		entry is qualified with the name of the <control type>.35		E.g. intel-rapl:0:1:1.36 37What:		/sys/class/powercap/<control type>/<power zone>/<child power zone>38Date:		September 201339KernelVersion:	3.1340Contact:	linux-pm@vger.kernel.org41Description:42		Power zones may be organized in a hierarchy in which child43		power zones provide monitoring and control for a subset of44		devices under the parent. For example, if there is a parent45		power zone for a whole CPU package, each CPU core in it can46		be a child power zone.47 48What:		/sys/class/powercap/.../<power zone>/name49Date:		September 201350KernelVersion:	3.1351Contact:	linux-pm@vger.kernel.org52Description:53		Specifies the name of this power zone.54 55What:		/sys/class/powercap/.../<power zone>/energy_uj56Date:		September 201357KernelVersion:	3.1358Contact:	linux-pm@vger.kernel.org59Description:60		Current energy counter in micro-joules. Write "0" to reset.61		If the counter can not be reset, then this attribute is62		read-only.63 64What:		/sys/class/powercap/.../<power zone>/max_energy_range_uj65Date:		September 201366KernelVersion:	3.1367Contact:	linux-pm@vger.kernel.org68Description:69		Range of the above energy counter in micro-joules.70 71 72What:		/sys/class/powercap/.../<power zone>/power_uw73Date:		September 201374KernelVersion:	3.1375Contact:	linux-pm@vger.kernel.org76Description:77		Current power in micro-watts.78 79What:		/sys/class/powercap/.../<power zone>/max_power_range_uw80Date:		September 201381KernelVersion:	3.1382Contact:	linux-pm@vger.kernel.org83Description:84		Range of the above power value in micro-watts.85 86What:		/sys/class/powercap/.../<power zone>/constraint_X_name87Date:		September 201388KernelVersion:	3.1389Contact:	linux-pm@vger.kernel.org90Description:91		Each power zone can define one or more constraints. Each92		constraint can have an optional name. Here "X" can have values93		from 0 to max integer.94 95What:		/sys/class/powercap/.../<power zone>/constraint_X_power_limit_uw96Date:		September 201397KernelVersion:	3.1398Contact:	linux-pm@vger.kernel.org99Description:100		Power limit in micro-watts should be applicable for101		the time window specified by "constraint_X_time_window_us".102		Here "X" can have values from 0 to max integer.103 104What:		/sys/class/powercap/.../<power zone>/constraint_X_time_window_us105Date:		September 2013106KernelVersion:	3.13107Contact:	linux-pm@vger.kernel.org108Description:109		Time window in micro seconds. This is used along with110		constraint_X_power_limit_uw to define a power constraint.111		Here "X" can have values from 0 to max integer.112 113 114What:		/sys/class/powercap/<control type>/.../constraint_X_max_power_uw115Date:		September 2013116KernelVersion:	3.13117Contact:	linux-pm@vger.kernel.org118Description:119		Maximum allowed power in micro watts for this constraint.120		Here "X" can have values from 0 to max integer.121 122What:		/sys/class/powercap/<control type>/.../constraint_X_min_power_uw123Date:		September 2013124KernelVersion:	3.13125Contact:	linux-pm@vger.kernel.org126Description:127		Minimum allowed power in micro watts for this constraint.128		Here "X" can have values from 0 to max integer.129 130What:		/sys/class/powercap/.../<power zone>/constraint_X_max_time_window_us131Date:		September 2013132KernelVersion:	3.13133Contact:	linux-pm@vger.kernel.org134Description:135		Maximum allowed time window in micro seconds for this136		constraint. Here "X" can have values from 0 to max integer.137 138What:		/sys/class/powercap/.../<power zone>/constraint_X_min_time_window_us139Date:		September 2013140KernelVersion:	3.13141Contact:	linux-pm@vger.kernel.org142Description:143		Minimum allowed time window in micro seconds for this144		constraint. Here "X" can have values from 0 to max integer.145 146What:		/sys/class/powercap/.../<power zone>/enabled147Date:		September 2013148KernelVersion:	3.13149Contact:	linux-pm@vger.kernel.org150Description:151		This allows to enable/disable power capping at power zone level.152		This applies to current power zone and its children.153