Skip to content
Snippets Groups Projects
Select Git revision
  • 162bc7f5afd75b72acbe3c5f3488ef7e64a3fe36
  • vme-testing default
  • ci-test
  • master
  • remoteproc
  • am625-sk-ov5640
  • pcal6534-upstreaming
  • lps22df-upstreaming
  • msc-upstreaming
  • imx8mp
  • iio/noa1305
  • vme-next
  • vme-next-4.14-rc4
  • v4.14-rc4
  • v4.14-rc3
  • v4.14-rc2
  • v4.14-rc1
  • v4.13
  • vme-next-4.13-rc7
  • v4.13-rc7
  • v4.13-rc6
  • v4.13-rc5
  • v4.13-rc4
  • v4.13-rc3
  • v4.13-rc2
  • v4.13-rc1
  • v4.12
  • v4.12-rc7
  • v4.12-rc6
  • v4.12-rc5
  • v4.12-rc4
  • v4.12-rc3
32 results

debug_core.c

Blame
  • sysfs.c 21.09 KiB
    /*
     * drivers/base/power/sysfs.c - sysfs entries for device PM
     */
    
    #include <linux/device.h>
    #include <linux/string.h>
    #include <linux/export.h>
    #include <linux/pm_qos.h>
    #include <linux/pm_runtime.h>
    #include <linux/atomic.h>
    #include <linux/jiffies.h>
    #include "power.h"
    
    /*
     *	control - Report/change current runtime PM setting of the device
     *
     *	Runtime power management of a device can be blocked with the help of
     *	this attribute.  All devices have one of the following two values for
     *	the power/control file:
     *
     *	 + "auto\n" to allow the device to be power managed at run time;
     *	 + "on\n" to prevent the device from being power managed at run time;
     *
     *	The default for all devices is "auto", which means that devices may be
     *	subject to automatic power management, depending on their drivers.
     *	Changing this attribute to "on" prevents the driver from power managing
     *	the device at run time.  Doing that while the device is suspended causes
     *	it to be woken up.
     *
     *	wakeup - Report/change current wakeup option for device
     *
     *	Some devices support "wakeup" events, which are hardware signals
     *	used to activate devices from suspended or low power states.  Such
     *	devices have one of three values for the sysfs power/wakeup file:
     *
     *	 + "enabled\n" to issue the events;
     *	 + "disabled\n" not to do so; or
     *	 + "\n" for temporary or permanent inability to issue wakeup.
     *
     *	(For example, unconfigured USB devices can't issue wakeups.)
     *
     *	Familiar examples of devices that can issue wakeup events include
     *	keyboards and mice (both PS2 and USB styles), power buttons, modems,
     *	"Wake-On-LAN" Ethernet links, GPIO lines, and more.  Some events
     *	will wake the entire system from a suspend state; others may just
     *	wake up the device (if the system as a whole is already active).
     *	Some wakeup events use normal IRQ lines; other use special out
     *	of band signaling.
     *
     *	It is the responsibility of device drivers to enable (or disable)
     *	wakeup signaling as part of changing device power states, respecting
     *	the policy choices provided through the driver model.
     *
     *	Devices may not be able to generate wakeup events from all power
     *	states.  Also, the events may be ignored in some configurations;
     *	for example, they might need help from other devices that aren't
     *	active, or which may have wakeup disabled.  Some drivers rely on
     *	wakeup events internally (unless they are disabled), keeping
     *	their hardware in low power modes whenever they're unused.  This
     *	saves runtime power, without requiring system-wide sleep states.
     *
     *	async - Report/change current async suspend setting for the device
     *
     *	Asynchronous suspend and resume of the device during system-wide power
     *	state transitions can be enabled by writing "enabled" to this file.
     *	Analogously, if "disabled" is written to this file, the device will be
     *	suspended and resumed synchronously.
     *
     *	All devices have one of the following two values for power/async:
     *