power (reference) in projects: linux-4.4.14

Searched refs:power (Results 1 – 200 of 1508) sorted by relevance

/linux-4.4.14/drivers/base/power/
D	runtime.c	68 delta = now - dev->power.accounting_timestamp; in update_pm_runtime_accounting() 70 dev->power.accounting_timestamp = now; in update_pm_runtime_accounting() 72 if (dev->power.disable_depth > 0) in update_pm_runtime_accounting() 75 if (dev->power.runtime_status == RPM_SUSPENDED) in update_pm_runtime_accounting() 76 dev->power.suspended_jiffies += delta; in update_pm_runtime_accounting() 78 dev->power.active_jiffies += delta; in update_pm_runtime_accounting() 84 dev->power.runtime_status = status; in __update_runtime_status() 93 if (dev->power.timer_expires > 0) { in pm_runtime_deactivate_timer() 94 del_timer(&dev->power.suspend_timer); in pm_runtime_deactivate_timer() 95 dev->power.timer_expires = 0; in pm_runtime_deactivate_timer() [all …]
D	sysfs.c	105 dev->power.runtime_auto ? ctrl_auto : ctrl_on); in control_show() 134 spin_lock_irq(&dev->power.lock); in rtpm_active_time_show() 136 ret = sprintf(buf, "%i\n", jiffies_to_msecs(dev->power.active_jiffies)); in rtpm_active_time_show() 137 spin_unlock_irq(&dev->power.lock); in rtpm_active_time_show() 147 spin_lock_irq(&dev->power.lock); in rtpm_suspended_time_show() 150 jiffies_to_msecs(dev->power.suspended_jiffies)); in rtpm_suspended_time_show() 151 spin_unlock_irq(&dev->power.lock); in rtpm_suspended_time_show() 162 if (dev->power.runtime_error) { in rtpm_status_show() 164 } else if (dev->power.disable_depth) { in rtpm_status_show() 167 switch (dev->power.runtime_status) { in rtpm_status_show() [all …]
D	qos.c	63 struct dev_pm_qos qos = dev->power.qos; in __dev_pm_qos_flags() 67 lockdep_assert_held(&dev->power.lock); in __dev_pm_qos_flags() 93 spin_lock_irqsave(&dev->power.lock, irqflags); in dev_pm_qos_flags() 95 spin_unlock_irqrestore(&dev->power.lock, irqflags); in dev_pm_qos_flags() 109 lockdep_assert_held(&dev->power.lock); in __dev_pm_qos_read_value() 111 return IS_ERR_OR_NULL(dev->power.qos) ? in __dev_pm_qos_read_value() 112 0 : pm_qos_read_value(&dev->power.qos->resume_latency); in __dev_pm_qos_read_value() 124 spin_lock_irqsave(&dev->power.lock, flags); in dev_pm_qos_read_value() 126 spin_unlock_irqrestore(&dev->power.lock, flags); in dev_pm_qos_read_value() 144 struct dev_pm_qos qos = req->dev->power.qos; in apply_constraint() [all …]
D	main.c	94 dev->power.is_prepared = false; in device_pm_sleep_init() 95 dev->power.is_suspended = false; in device_pm_sleep_init() 96 dev->power.is_noirq_suspended = false; in device_pm_sleep_init() 97 dev->power.is_late_suspended = false; in device_pm_sleep_init() 98 init_completion(&dev->power.completion); in device_pm_sleep_init() 99 complete_all(&dev->power.completion); in device_pm_sleep_init() 100 dev->power.wakeup = NULL; in device_pm_sleep_init() 101 INIT_LIST_HEAD(&dev->power.entry); in device_pm_sleep_init() 129 if (dev->parent && dev->parent->power.is_prepared) in device_pm_add() 132 list_add_tail(&dev->power.entry, &dpm_list); in device_pm_add() [all …]
D	common.c	33 spin_lock_irq(&dev->power.lock); in dev_pm_get_subsys_data() 35 if (dev->power.subsys_data) { in dev_pm_get_subsys_data() 36 dev->power.subsys_data->refcount++; in dev_pm_get_subsys_data() 40 dev->power.subsys_data = psd; in dev_pm_get_subsys_data() 45 spin_unlock_irq(&dev->power.lock); in dev_pm_get_subsys_data() 65 spin_lock_irq(&dev->power.lock); in dev_pm_put_subsys_data() 72 dev->power.subsys_data = NULL; in dev_pm_put_subsys_data() 77 spin_unlock_irq(&dev->power.lock); in dev_pm_put_subsys_data()
D	wakeirq.c	41 spin_lock_irqsave(&dev->power.lock, flags); in dev_pm_attach_wake_irq() 42 if (dev_WARN_ONCE(dev, dev->power.wakeirq, in dev_pm_attach_wake_irq() 44 spin_unlock_irqrestore(&dev->power.lock, flags); in dev_pm_attach_wake_irq() 50 dev->power.wakeirq = wirq; in dev_pm_attach_wake_irq() 52 spin_unlock_irqrestore(&dev->power.lock, flags); in dev_pm_attach_wake_irq() 102 struct wake_irq wirq = dev->power.wakeirq; in dev_pm_clear_wake_irq() 108 spin_lock_irqsave(&dev->power.lock, flags); in dev_pm_clear_wake_irq() 110 dev->power.wakeirq = NULL; in dev_pm_clear_wake_irq() 111 spin_unlock_irqrestore(&dev->power.lock, flags); in dev_pm_clear_wake_irq() 223 struct wake_irq wirq = dev->power.wakeirq; in dev_pm_enable_wake_irq() [all …]
D	wakeup.c	243 spin_lock_irq(&dev->power.lock); in device_wakeup_attach() 244 if (dev->power.wakeup) { in device_wakeup_attach() 245 spin_unlock_irq(&dev->power.lock); in device_wakeup_attach() 248 dev->power.wakeup = ws; in device_wakeup_attach() 249 spin_unlock_irq(&dev->power.lock); in device_wakeup_attach() 264 if (!dev \|\| !dev->power.can_wakeup) in device_wakeup_enable() 295 ws = dev->power.wakeup; in device_wakeup_attach_irq() 320 ws = dev->power.wakeup; in device_wakeup_detach_irq() 369 spin_lock_irq(&dev->power.lock); in device_wakeup_detach() 370 ws = dev->power.wakeup; in device_wakeup_detach() [all …]
D	power.h	`5 if (!dev->power.early_init) { in device_pm_init_common() 6 spin_lock_init(&dev->power.lock); in device_pm_init_common() 7 dev->power.qos = NULL; in device_pm_init_common() 8 dev->power.early_init = true; in device_pm_init_common() 16 dev->power.disable_depth = 1; in pm_runtime_early_init() 117 return container_of(entry, struct device, power.entry); in to_device()`
D	domain_governor.c	`19 if (dev->power.subsys_data && dev->power.subsys_data->domain_data) in dev_update_qos_constraint() 51 spin_lock_irqsave(&dev->power.lock, flags); in default_stop_ok() 56 spin_unlock_irqrestore(&dev->power.lock, flags); in default_stop_ok() 64 spin_unlock_irqrestore(&dev->power.lock, flags); in default_stop_ok() 75 if (!dev->power.ignore_children) in default_stop_ok()`
D	domain.c	262 spin_lock_irq(&dev->power.lock); in genpd_dev_pm_qos_notifier() 264 pdd = dev->power.subsys_data ? in genpd_dev_pm_qos_notifier() 265 dev->power.subsys_data->domain_data : NULL; in genpd_dev_pm_qos_notifier() 273 spin_unlock_irq(&dev->power.lock); in genpd_dev_pm_qos_notifier() 282 if (!dev \|\| dev->power.ignore_children) in genpd_dev_pm_qos_notifier() 324 if (!pm_runtime_suspended(pdd->dev) \|\| pdd->dev->power.irq_safe) in genpd_poweroff() 444 if (dev->power.irq_safe) in pm_genpd_runtime_suspend() 479 if (dev->power.irq_safe) { in pm_genpd_runtime_resume() 796 \|\| (dev->power.wakeup_path && genpd_dev_active_wakeup(genpd, dev))) in pm_genpd_suspend_noirq() 829 \|\| (dev->power.wakeup_path && genpd_dev_active_wakeup(genpd, dev))) in pm_genpd_resume_noirq() [all …]
/linux-4.4.14/drivers/staging/nvec/
D	nvec_power.c	91 struct nvec_power power = in nvec_power_notifier() local 99 if (power->on != res->plu) { in nvec_power_notifier() 100 power->on = res->plu; in nvec_power_notifier() 113 static void get_bat_mfg_data(struct nvec_power power) in get_bat_mfg_data() argument 120 nvec_write_async(power->nvec, buf, 2); in get_bat_mfg_data() 127 struct nvec_power *power = in nvec_power_bat_notifier() local 138 if (power->bat_present == 0) { in nvec_power_bat_notifier() 140 get_bat_mfg_data(power); in nvec_power_bat_notifier() 143 power->bat_present = 1; in nvec_power_bat_notifier() 147 power->bat_status = in nvec_power_bat_notifier() [all …]
/linux-4.4.14/Documentation/devicetree/bindings/soc/rockchip/
D	power_domain.txt	3 Rockchip processors include support for multiple power domains which can be 4 powered up/down by software based on different application scenes to save power. 6 Required properties for power domain controller: 8 "rockchip,rk3288-power-controller" - for RK3288 SoCs. 9 - #power-domain-cells: Number of cells in a power-domain specifier. 14 Required properties for power domain sub nodes: 15 - reg: index of the power domain, should use macros in: 16 "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power domain. 17 - clocks (optional): phandles to clocks which need to be enabled while power domain 22 power: power-controller { [all …]
/linux-4.4.14/Documentation/devicetree/bindings/power/
D	power_domain.txt	4 used for power gating of selected IP blocks for power saving by reduced leakage 12 #power-domain-cells property in the PM domain provider node. 17 - #power-domain-cells : Number of cells in a PM domain specifier; 19 providing multiple PM domains (e.g. power controllers), but can be any value 23 - power-domains : A phandle and PM domain specifier as defined by bindings of 24 the power controller specified by phandle. 25 Some power domains might be powered from another power domain (or have 29 specified by this binding. More details about power domain specifier are 34 power: power-controller@12340000 { 35 compatible = "foo,power-controller"; [all …]
D	pd-samsung.txt	3 Exynos processors include support for multiple power domains which are used 4 to gate power to one or more peripherals on the processor. 8 * samsung,exynos4210-pd - for exynos4210 type power domain. 11 - #power-domain-cells: number of cells in power domain specifier; 16 devices in this power domain are set to oscclk before power gating 22 - clkN: Input clocks to the devices in this power domain. These clocks 23 will be reparented to oscclk before swithing power domain off. 27 the power domain. These clock should be enabled during power 29 - power-domains: phandle pointing to the parent power domain, for more details 30 see Documentation/devicetree/bindings/power/power_domain.txt [all …]
D	fsl,imx-gpc.txt	5 counters and Power Gating Control (PGC) for the CPU and PU (GPU/VPU) power 13 - pu-supply: Link to the LDO regulator powering the PU power domain 14 - clocks: Clock phandles to devices in the PU power domain that need 15 to be enabled during domain power-up for reset propagation. 16 - #power-domain-cells: Should be 1, see below: 18 The gpc node is a power-controller as documented by the generic power domain 19 bindings in Documentation/devicetree/bindings/power/power_domain.txt. 35 #power-domain-cells = <1>; 39 Specifying power domain for IP modules 42 IP cores belonging to a power domain should contain a 'power-domains' property [all …]
D	renesas,sysc-rmobile.txt	`32 Documentation/devicetree/bindings/power/power_domain.txt. 34 The nodes should be named by the real power area names, and thus their names 38 - #power-domain-cells: Must be 0. 42 index number for the corresponding power area in the various Power 64 #power-domain-cells = <0>; 70 #power-domain-cells = <0>; 74 #power-domain-cells = <0>; 80 #power-domain-cells = <0>; 89 Hardware blocks belonging to a PM domain should contain a "power-domains" 98 power-domains = <&pd_a3sp>;`
D	power-controller.txt	`1 * Generic system power control capability 4 sometimes able to control the system power. The device driver associated with these 7 standard property "system-power-controller" in its device node. This property 8 marks the device as able to control the system power. In order to test if this 17 system-power-controller;`
/linux-4.4.14/drivers/power/
D	wm831x_power.c	499 struct wm831x_power *power; in wm831x_power_probe() local 502 power = devm_kzalloc(&pdev->dev, sizeof(struct wm831x_power), in wm831x_power_probe() 504 if (power == NULL) in wm831x_power_probe() 507 power->wm831x = wm831x; in wm831x_power_probe() 508 platform_set_drvdata(pdev, power); in wm831x_power_probe() 511 snprintf(power->wall_name, sizeof(power->wall_name), in wm831x_power_probe() 513 snprintf(power->battery_name, sizeof(power->wall_name), in wm831x_power_probe() 515 snprintf(power->usb_name, sizeof(power->wall_name), in wm831x_power_probe() 518 snprintf(power->wall_name, sizeof(power->wall_name), in wm831x_power_probe() 520 snprintf(power->battery_name, sizeof(power->wall_name), in wm831x_power_probe() [all …]
D	axp20x_usb_power.c	51 struct axp20x_usb_power power = devid; in axp20x_usb_power_irq() local 53 power_supply_changed(power->supply); in axp20x_usb_power_irq() 61 struct axp20x_usb_power power = power_supply_get_drvdata(psy); in axp20x_usb_power_get_property() local 67 ret = regmap_read(power->regmap, AXP20X_VBUS_IPSOUT_MGMT, &v); in axp20x_usb_power_get_property() 74 ret = axp20x_read_variable_width(power->regmap, in axp20x_usb_power_get_property() 82 ret = regmap_read(power->regmap, AXP20X_VBUS_IPSOUT_MGMT, &v); in axp20x_usb_power_get_property() 102 ret = axp20x_read_variable_width(power->regmap, in axp20x_usb_power_get_property() 114 ret = regmap_read(power->regmap, AXP20X_PWR_INPUT_STATUS, &input); in axp20x_usb_power_get_property() 125 ret = regmap_read(power->regmap, AXP20X_USB_OTG_STATUS, &v); in axp20x_usb_power_get_property() 171 struct axp20x_usb_power *power; in axp20x_usb_power_probe() local [all …]
D	wm8350_power.c	47 if (!wm8350->power.rev_g_coeff) in wm8350_charge_time_min() 190 struct wm8350_power power = &wm8350->power; in wm8350_charger_handler() local 191 struct wm8350_charger_policy policy = power->policy; in wm8350_charger_handler() 199 power_supply_changed(power->battery); in wm8350_charger_handler() 206 power_supply_changed(power->battery); in wm8350_charger_handler() 234 power_supply_changed(power->battery); in wm8350_charger_handler() 235 power_supply_changed(power->usb); in wm8350_charger_handler() 236 power_supply_changed(power->ac); in wm8350_charger_handler() 472 struct wm8350_power power = &wm8350->power; in wm8350_power_probe() local 473 struct wm8350_charger_policy policy = power->policy; in wm8350_power_probe() [all …]
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
D	e6500_power_isa.dtsi	`37 power-isa-version = "2.06"; 38 power-isa-b; // Base 39 power-isa-e; // Embedded 40 power-isa-atb; // Alternate Time Base 41 power-isa-cs; // Cache Specification 42 power-isa-ds; // Decorated Storage 43 power-isa-e.ed; // Embedded.Enhanced Debug 44 power-isa-e.pd; // Embedded.External PID 45 power-isa-e.hv; // Embedded.Hypervisor 46 power-isa-e.le; // Embedded.Little-Endian [all …]`
D	e5500_power_isa.dtsi	`37 power-isa-version = "2.06"; 38 power-isa-b; // Base 39 power-isa-e; // Embedded 40 power-isa-atb; // Alternate Time Base 41 power-isa-cs; // Cache Specification 42 power-isa-ds; // Decorated Storage 43 power-isa-e.ed; // Embedded.Enhanced Debug 44 power-isa-e.pd; // Embedded.External PID 45 power-isa-e.hv; // Embedded.Hypervisor 46 power-isa-e.le; // Embedded.Little-Endian [all …]`
D	e500mc_power_isa.dtsi	`37 power-isa-version = "2.06"; 38 power-isa-b; // Base 39 power-isa-e; // Embedded 40 power-isa-atb; // Alternate Time Base 41 power-isa-cs; // Cache Specification 42 power-isa-ds; // Decorated Storage 43 power-isa-e.ed; // Embedded.Enhanced Debug 44 power-isa-e.pd; // Embedded.External PID 45 power-isa-e.hv; // Embedded.Hypervisor 46 power-isa-e.le; // Embedded.Little-Endian [all …]`
D	e500v2_power_isa.dtsi	`37 power-isa-version = "2.03"; 38 power-isa-b; // Base 39 power-isa-e; // Embedded 40 power-isa-atb; // Alternate Time Base 41 power-isa-cs; // Cache Specification 42 power-isa-e.le; // Embedded.Little-Endian 43 power-isa-e.pm; // Embedded.Performance Monitor 44 power-isa-ecl; // Embedded Cache Locking 45 power-isa-mmc; // Memory Coherence 46 power-isa-sp; // Signal Processing Engine [all …]`
/linux-4.4.14/Documentation/ABI/testing/
D	sysfs-class-powercap	6 The powercap/ class sub directory belongs to the power cap 8 Documentation/power/powercap/powercap.txt for details. 16 Here <control type> determines how the power is going to be 17 controlled. A <control type> can contain multiple power zones. 24 This allows to enable/disable power capping for a "control type". 25 This status affects every power zone using this "control_type. 27 What: /sys/class/powercap/<control type>/<power zone> 32 A power zone is a single or a collection of devices, which can 33 be independently monitored and controlled. A power zone sysfs 37 What: /sys/class/powercap/<control type>/<power zone>/<child power zone> [all …]
D	sysfs-power	`1 What: /sys/power/ 5 The /sys/power directory will contain files that will 6 provide a unified interface to the power management 9 What: /sys/power/state 13 The /sys/power/state file controls system sleep states. 27 "standby" - "power-on suspend", present if supported. 32 Documentation/power/states.txt for a description of what 33 "suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean. 35 What: /sys/power/disk 39 The /sys/power/disk file controls the operating mode of the [all …]`
D	sysfs-devices-power_state	`6 device objects representing ACPI device nodes that provide power 10 power state of the given device node. Its possible values, 11 "D0", "D1", "D2", "D3hot", and "D3cold", reflect the power state 14 If the device node uses shared ACPI power resources, this state 15 determines a list of power resources required not to be turned 16 off. However, some power resources needed by the device node in 17 higher-power (lower-number) states may also be ON because of`
D	sysfs-devices-power	1 What: /sys/devices/.../power/ 5 The /sys/devices/.../power directory contains attributes 6 allowing the user space to check and modify some power 9 What: /sys/devices/.../power/wakeup 13 The /sys/devices/.../power/wakeup attribute allows the user 21 have one of the following two values for the sysfs power/wakeup 35 What: /sys/devices/.../power/control 39 The /sys/devices/.../power/control attribute allows the user 40 space to control the run-time power management of the device. 43 power/control file: [all …]
D	sysfs-devices-real_power_state	`7 power management methods and use ACPI power resources for power 11 power state of the given device node as returned by the _PSC 12 control method or inferred from the configuration of power 14 "D3cold", reflect the power state names defined by the ACPI 19 the same device object. If that happens, some shared power`
D	sysfs-class-power-twl4030	`24 "auto" - draw power as appropriate for detected 25 power source and battery status. 26 "off" - do not draw any power. 33 This is useful for unstable power sources 43 "auto" - draw power as appropriate for detected 44 power source and battery status. 45 "off" - do not draw any power.`
D	sysfs-devices-power_resources_D1	`7 use ACPI power resources for power management and support ACPI 8 power state D1. 11 representing ACPI power resources that need to be turned on for 12 the given device node to be in ACPI power state D1. The names`
D	sysfs-devices-power_resources_D2	`7 use ACPI power resources for power management and support ACPI 8 power state D2. 11 representing ACPI power resources that need to be turned on for 12 the given device node to be in ACPI power state D2. The names`
D	sysfs-devices-power_resources_D3hot	`7 use ACPI power resources for power management and support ACPI 8 power state D3hot. 11 representing ACPI power resources that need to be turned on for 12 the given device node to be in ACPI power state D3hot. The`
D	sysfs-devices-power_resources_D0	`7 use ACPI power resources for power management. 10 representing ACPI power resources that need to be turned on for 11 the given device node to be in ACPI power state D0. The names`
D	sysfs-class-lcd	`6 Control LCD power, values are FB_BLANK_* from fb.h 7 - FB_BLANK_UNBLANK (0) : power on. 8 - FB_BLANK_POWERDOWN (4) : power off`
D	sysfs-class-fpga-manager	`25 * power off = FPGA power is off 26 * power up = FPGA reports power is up`
D	sysfs-bus-usb	123 What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm 132 power/usb2_hardware_lpm. The file holds a string value (enable 137 What: /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u1 138 /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u2 149 power/usb3_hardware_lpm_u1 and power/usb3_hardware_lpm_u2. These 192 What: /sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout 196 USB 2.0 devices may support hardware link power management (LPM) 200 Useful for power management tuning. 203 What: /sys/bus/usb/devices/.../power/usb2_lpm_besl 207 USB 2.0 devices that support hardware link power management (LPM) [all …]
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
D	twl4030-power.txt	1 Texas Instruments TWL family (twl4030) reset and power management module 3 The power management module inside the TWL family provides several facilities 4 to control the power resources, including power scripts. For now, the 9 "ti,twl4030-power" 10 "ti,twl4030-power-reset" 11 "ti,twl4030-power-idle" 12 "ti,twl4030-power-idle-osc-off" 14 The use of ti,twl4030-power-reset is recommended at least on 17 When using ti,twl4030-power-idle, the TI recommended configuration 20 When using ti,twl4030-power-idle-osc-off, the TI recommended [all …]
/linux-4.4.14/drivers/usb/musb/
D	musb_virthub.c	50 u8 power; in musb_host_finish_resume() local 56 power = musb_readb(musb->mregs, MUSB_POWER); in musb_host_finish_resume() 57 power &= ~MUSB_POWER_RESUME; in musb_host_finish_resume() 59 power); in musb_host_finish_resume() 60 musb_writeb(musb->mregs, MUSB_POWER, power); in musb_host_finish_resume() 80 u8 power; in musb_port_suspend() local 91 power = musb_readb(mbase, MUSB_POWER); in musb_port_suspend() 95 power &= ~MUSB_POWER_RESUME; in musb_port_suspend() 96 power \|= MUSB_POWER_SUSPENDM; in musb_port_suspend() 97 musb_writeb(mbase, MUSB_POWER, power); in musb_port_suspend() [all …]
/linux-4.4.14/Documentation/power/powercap/
D	powercap.txt	4 The power capping framework provides a consistent interface between the kernel 5 and the user space that allows power capping drivers to expose the settings to 10 The framework exposes power capping devices to user space via sysfs in the 12 'control types', which correspond to different methods of power capping. For 15 corresponds to the use of idle injection for controlling power. 18 monitored using the power capping method determined by the control type the 19 given zone belongs to. They each contain attributes for monitoring power, as 20 well as controls represented in the form of power constraints. If the parts of 21 the system represented by different power zones are hierarchical (that is, one 22 bigger part consists of multiple smaller parts that each have their own power [all …]
/linux-4.4.14/drivers/staging/vt6656/
D	rf.c	626 u8 power = priv->cck_pwr; in vnt_rf_setpower() local 639 power = priv->cck_pwr_tbl[channel]; in vnt_rf_setpower() 650 power = priv->ofdm_a_pwr_tbl[channel-15]; in vnt_rf_setpower() 652 power = priv->ofdm_pwr_tbl[channel-1]; in vnt_rf_setpower() 656 return vnt_rf_set_txpower(priv, power, rate); in vnt_rf_setpower() 686 int vnt_rf_set_txpower(struct vnt_private *priv, u8 power, u32 rate) in vnt_rf_set_txpower() argument 691 power += vnt_rf_addpower(priv); in vnt_rf_set_txpower() 692 if (power > VNT_RF_MAX_POWER) in vnt_rf_set_txpower() 693 power = VNT_RF_MAX_POWER; in vnt_rf_set_txpower() 695 if (priv->power == power) in vnt_rf_set_txpower() [all …]
/linux-4.4.14/Documentation/hwmon/
D	acpi_power_meter	4 This driver talks to ACPI 4.0 power meters. 16 This driver implements sensor reading support for the power meters exposed in 18 features--a power meter that returns average power use over a configurable 26 The power[1-]_is_battery knob indicates if the power supply is a battery. 27 Both power[1-]_average_{min,max} must be set before the trip points will work. 30 power[1-]_average sysfs file. 32 The power[1-]_{model_number, serial_number, oem_info} fields display arbitrary 36 Some computers have the ability to enforce a power cap in hardware. If this is 37 the case, the power[1-*]_cap and related sysfs files will appear. When the 38 average power consumption exceeds the cap, an ACPI event will be broadcast on [all …]
D	ina209	19 The TI / Burr-Brown INA209 monitors voltage, current, and power on the high side 20 of a D.C. power supply. It can perform measurements and calculations in the 22 calibration multiplier to scale the displayed current and power values. 61 power1_input power measurement (uW) 62 power1_input_highest power historical maximum reading (uW) 63 power1_reset_history reset power history 64 power1_max power max alarm limit (uW) 65 power1_crit power crit alarm limit (uW) 66 power1_max_alarm power max alarm limit exceeded 67 power1_crit_alarm power crit alarm limit exceeded [all …]
D	ibmaem	`20 This driver implements sensor reading support for the energy and power meters 27 last BMC reset, and a power sensor that returns average power use over a 31 range of energy and power use registers, the power cap as set by the AEM 37 The "power_cap" value displays the current system power cap, as set by the AEM 38 software. Setting the power cap from the host is not currently supported.`
D	ucd9000	24 ADC with a 2.5V internal reference for monitoring up to 13 power supply voltage, 27 The UCD90124 is a 12-rail PMBus/I2C addressable power-supply sequencer and 29 13 power-supply voltage, current, or temperature inputs. Twenty-six GPIO pins 30 can be used for power supply enables, power-on reset signals, external 35 The UCD9090 is a 10-rail PMBus/I2C addressable power-supply sequencer and 36 monitor. The device integrates a 12-bit ADC for monitoring up to 10 power-supply 37 voltage inputs. Twenty-three GPIO pins can be used for power supply enables, 38 power-on reset signals, external interrupts, cascading, or other system 42 The UCD90910 is a ten-rail I2C / PMBus addressable power-supply sequencer and 44 13 power-supply voltage, current, or temperature inputs.
D	lm25066	`104 power1_input Measured input power. 105 power1_average Average measured input power. 106 power1_max Maximum input power limit. 107 power1_alarm Input power alarm 108 power1_input_highest Historical maximum power. 109 power1_reset_history Write any value to reset maximum power history. 112 power2_input Measured output power. 113 power2_max Maximum output power limit. 114 power2_crit Critical output power limit.`
D	sysfs-interface	113 take drastic action such as power down or reset. At the very 124 take drastic action such as power down or reset. At the very 476 power[1-]_average Average power use 480 power[1-]_average_interval Power use averaging interval. A poll 486 power[1-]_average_interval_max Maximum power use averaging interval 490 power[1-]_average_interval_min Minimum power use averaging interval 494 power[1-]_average_highest Historical average maximum power use 498 power[1-]_average_lowest Historical average minimum power use 502 power[1-]_average_max A poll notification is sent to 503 power[1-]_average when power use [all …]
D	fam15h_power	`19 This driver permits reading of registers providing power information 22 For AMD Family 15h and 16h processors the following power values can 26 * BasePwrWatts: Specifies in watts the maximum amount of power 28 * ProcessorPwrWatts: Specifies in watts the maximum amount of power 30 * CurrPwrWatts: Specifies in watts the current amount of power being`
D	lineage-pem	`20 Lineage CPL power entry modules are nominally PMBus compliant. However, most 38 All Lineage CPL power entry modules have a built-in I2C bus master selector 47 alarms for output voltage, temperature, input voltage, input current, input power, 50 Input voltage, input current, input power, and fan speed measurement is only 65 power1_input Input power (uW, optional) 66 power1_alarm Input power alarm`
D	ltc2945	`18 and power consumption. 79 power1_max High power threshold 80 power1_input_lowest Historical minimum power use 81 power1_input_highest Historical maximum power use 83 power1_min_alarm Low power alarm 84 power1_max_alarm High power alarm`
D	ibmpowernv	`13 voltage/power for 'POWERNV' platform. 38 inX_input Measured power supply voltage 40 1: Failing power supply. 41 power1_input System power consumption (microWatt)`
D	max34440	`103 power[1,3]_label "pout[1,3]" 104 power[1,3]_input Measured power. 105 power[1,3]_average Historical average power. 106 power[1,3]_highest Historical maximum power.`
/linux-4.4.14/drivers/video/backlight/
D	lms501kf03.c	28 unsigned int power; member 220 static int lms501kf03_power_is_on(int power) in lms501kf03_power_is_on() argument 222 return (power) <= FB_BLANK_NORMAL; in lms501kf03_power_is_on() 283 static int lms501kf03_power(struct lms501kf03 *lcd, int power) in lms501kf03_power() argument 287 if (lms501kf03_power_is_on(power) && in lms501kf03_power() 288 !lms501kf03_power_is_on(lcd->power)) in lms501kf03_power() 290 else if (!lms501kf03_power_is_on(power) && in lms501kf03_power() 291 lms501kf03_power_is_on(lcd->power)) in lms501kf03_power() 295 lcd->power = power; in lms501kf03_power() 304 return lcd->power; in lms501kf03_get_power() [all …]
D	ams369fg06.c	40 unsigned int power; member 306 static int ams369fg06_power_is_on(int power) in ams369fg06_power_is_on() argument 308 return power <= FB_BLANK_NORMAL; in ams369fg06_power_is_on() 376 static int ams369fg06_power(struct ams369fg06 *lcd, int power) in ams369fg06_power() argument 380 if (ams369fg06_power_is_on(power) && in ams369fg06_power() 381 !ams369fg06_power_is_on(lcd->power)) in ams369fg06_power() 383 else if (!ams369fg06_power_is_on(power) && in ams369fg06_power() 384 ams369fg06_power_is_on(lcd->power)) in ams369fg06_power() 388 lcd->power = power; in ams369fg06_power() 397 return lcd->power; in ams369fg06_get_power() [all …]
D	ili9320.c	129 static int ili9320_power(struct ili9320 lcd, int power) in ili9320_power() argument 133 dev_dbg(lcd->dev, "power %d => %d\n", lcd->power, power); in ili9320_power() 135 if (POWER_IS_ON(power) && !POWER_IS_ON(lcd->power)) in ili9320_power() 137 else if (!POWER_IS_ON(power) && POWER_IS_ON(lcd->power)) in ili9320_power() 141 lcd->power = power; in ili9320_power() 143 dev_warn(lcd->dev, "failed to set power mode %d\n", power); in ili9320_power() 153 static int ili9320_set_power(struct lcd_device ld, int power) in ili9320_set_power() argument 157 return ili9320_power(lcd, power); in ili9320_set_power() 164 return lcd->power; in ili9320_get_power() 229 ili->power = FB_BLANK_POWERDOWN; in ili9320_probe_spi() [all …]
D	ld9040.c	41 unsigned int power; member 551 static int ld9040_power_is_on(int power) in ld9040_power_is_on() argument 553 return power <= FB_BLANK_NORMAL; in ld9040_power_is_on() 610 static int ld9040_power(struct ld9040 lcd, int power) in ld9040_power() argument 614 if (ld9040_power_is_on(power) && !ld9040_power_is_on(lcd->power)) in ld9040_power() 616 else if (!ld9040_power_is_on(power) && ld9040_power_is_on(lcd->power)) in ld9040_power() 620 lcd->power = power; in ld9040_power() 625 static int ld9040_set_power(struct lcd_device ld, int power) in ld9040_set_power() argument 629 if (power != FB_BLANK_UNBLANK && power != FB_BLANK_POWERDOWN && in ld9040_set_power() 630 power != FB_BLANK_NORMAL) { in ld9040_set_power() [all …]
D	platform_lcd.c	`29 unsigned int power; member 42 return plcd->power; in platform_lcd_get_power() 45 static int platform_lcd_set_power(struct lcd_device *lcd, int power) in platform_lcd_set_power() argument 50 if (power == FB_BLANK_POWERDOWN \|\| plcd->suspended) in platform_lcd_set_power() 54 plcd->power = power; in platform_lcd_set_power() 121 platform_lcd_set_power(plcd->lcd, plcd->power); in platform_lcd_suspend() 131 platform_lcd_set_power(plcd->lcd, plcd->power); in platform_lcd_resume()`
D	ltv350qv.c	26 int power; member 195 static int ltv350qv_power(struct ltv350qv lcd, int power) in ltv350qv_power() argument 199 if (POWER_IS_ON(power) && !POWER_IS_ON(lcd->power)) in ltv350qv_power() 201 else if (!POWER_IS_ON(power) && POWER_IS_ON(lcd->power)) in ltv350qv_power() 205 lcd->power = power; in ltv350qv_power() 210 static int ltv350qv_set_power(struct lcd_device ld, int power) in ltv350qv_set_power() argument 214 return ltv350qv_power(lcd, power); in ltv350qv_set_power() 221 return lcd->power; in ltv350qv_get_power() 240 lcd->power = FB_BLANK_POWERDOWN; in ltv350qv_probe()
D	s6e63m0.c	40 unsigned int power; member 493 static int s6e63m0_power_is_on(int power) in s6e63m0_power_is_on() argument 495 return power <= FB_BLANK_NORMAL; in s6e63m0_power_is_on() 565 static int s6e63m0_power(struct s6e63m0 lcd, int power) in s6e63m0_power() argument 569 if (s6e63m0_power_is_on(power) && !s6e63m0_power_is_on(lcd->power)) in s6e63m0_power() 571 else if (!s6e63m0_power_is_on(power) && s6e63m0_power_is_on(lcd->power)) in s6e63m0_power() 575 lcd->power = power; in s6e63m0_power() 580 static int s6e63m0_set_power(struct lcd_device ld, int power) in s6e63m0_set_power() argument 584 if (power != FB_BLANK_UNBLANK && power != FB_BLANK_POWERDOWN && in s6e63m0_set_power() 585 power != FB_BLANK_NORMAL) { in s6e63m0_set_power() [all …]
D	tdo24m.c	39 int power; member 284 static int tdo24m_power(struct tdo24m lcd, int power) in tdo24m_power() argument 288 if (POWER_IS_ON(power) && !POWER_IS_ON(lcd->power)) in tdo24m_power() 290 else if (!POWER_IS_ON(power) && POWER_IS_ON(lcd->power)) in tdo24m_power() 294 lcd->power = power; in tdo24m_power() 300 static int tdo24m_set_power(struct lcd_device ld, int power) in tdo24m_set_power() argument 304 return tdo24m_power(lcd, power); in tdo24m_set_power() 311 return lcd->power; in tdo24m_get_power() 360 lcd->power = FB_BLANK_POWERDOWN; in tdo24m_probe()
D	ili922x.c	143 int power; member 443 static int ili922x_lcd_power(struct ili922x lcd, int power) in ili922x_lcd_power() argument 447 if (POWER_IS_ON(power) && !POWER_IS_ON(lcd->power)) in ili922x_lcd_power() 449 else if (!POWER_IS_ON(power) && POWER_IS_ON(lcd->power)) in ili922x_lcd_power() 453 lcd->power = power; in ili922x_lcd_power() 458 static int ili922x_set_power(struct lcd_device ld, int power) in ili922x_set_power() argument 462 return ili922x_lcd_power(ili, power); in ili922x_set_power() 469 return ili->power; in ili922x_get_power() 513 ili->power = FB_BLANK_POWERDOWN; in ili922x_probe()
D	cr_bllcd.c	80 if (bd->props.power == FB_BLANK_UNBLANK) in cr_backlight_set_intensity() 84 if (bd->props.power == FB_BLANK_POWERDOWN) in cr_backlight_set_intensity() 160 static int cr_lcd_set_power(struct lcd_device *ld, int power) in cr_lcd_set_power() argument 162 if (power == FB_BLANK_UNBLANK) in cr_lcd_set_power() 164 if (power == FB_BLANK_POWERDOWN) in cr_lcd_set_power() 225 crp->cr_backlight_device->props.power = FB_BLANK_UNBLANK; in cr_backlight_probe() 239 crp->cr_backlight_device->props.power = FB_BLANK_POWERDOWN; in cr_backlight_remove()
D	corgi_lcd.c	93 int power; member 366 static int corgi_lcd_set_power(struct lcd_device *ld, int power) in corgi_lcd_set_power() argument 370 if (POWER_IS_ON(power) && !POWER_IS_ON(lcd->power)) in corgi_lcd_set_power() 373 if (!POWER_IS_ON(power) && POWER_IS_ON(lcd->power)) in corgi_lcd_set_power() 376 lcd->power = power; in corgi_lcd_set_power() 384 return lcd->power; in corgi_lcd_get_power() 430 if (bd->props.power != FB_BLANK_UNBLANK) in corgi_bl_update_status() 557 lcd->power = FB_BLANK_POWERDOWN; in corgi_lcd_probe() 570 lcd->bl_dev->props.power = FB_BLANK_UNBLANK; in corgi_lcd_probe() 591 lcd->bl_dev->props.power = FB_BLANK_UNBLANK; in corgi_lcd_remove()
D	l4f00242t03.c	`109 static int l4f00242t03_lcd_power_set(struct lcd_device *ld, int power) in l4f00242t03_lcd_power_set() argument 120 if (power <= FB_BLANK_NORMAL) { in l4f00242t03_lcd_power_set() 133 l4f00242t03_lcd_power_set(priv->ld, power); in l4f00242t03_lcd_power_set() 135 } else if (power < FB_BLANK_POWERDOWN) { in l4f00242t03_lcd_power_set() 149 l4f00242t03_lcd_power_set(ld, power); in l4f00242t03_lcd_power_set() 161 priv->lcd_state = power; in l4f00242t03_lcd_power_set()`
D	tosa_bl.c	`58 int power = max(props->power, props->fb_blank); in tosa_bl_update_status() local 61 if (power) in tosa_bl_update_status() 117 data->bl->props.power = FB_BLANK_UNBLANK; in tosa_bl_probe()`
D	generic_bl.c	`31 if (bd->props.power != FB_BLANK_UNBLANK) in genericbl_send_intensity() 85 bd->props.power = FB_BLANK_UNBLANK; in genericbl_probe() 99 bd->props.power = 0; in genericbl_remove()`
/linux-4.4.14/Documentation/thermal/
D	cpu-cooling-api.txt	45 implement the power extensions by using a simple cpu power model. The 48 The additional parameters are needed for the power model (See 2. Power 49 models). "capacitance" is the dynamic power coefficient (See 2.1 50 Dynamic power). "plat_static_func" is a function to calculate the 51 static power consumed by these cpus (See 2.2 Static power). 58 cpufreq cooling device with power extensions using the device tree 69 The power API registration functions provide a simple power model for 70 CPUs. The current power is calculated as dynamic + (optionally) 71 static power. This power model requires that the operating-points of 80 provide it, only dynamic power will be considered. [all …]
D	power_allocator.txt	21 The power allocator governor implements a 23 temperature as the control input and power as the controlled output: 47 \| S \|-------+----->\| sum e \|----->\| X \|--->\| S \|-->\| S \|-->\|power \| 59 Sustainable power 62 An estimate of the sustainable dissipatable power (in mW) should be 64 sustained power that can be dissipated at the desired control 65 temperature. This is the maximum sustained power for allocation at 66 the desired maximum temperature. The actual sustained power can vary 71 the thermal ramp. For reference, the sustainable power of a 4" phone 82 sustainable-power = <2500>; [all …]
/linux-4.4.14/drivers/acpi/
D	processor_idle.c	133 struct acpi_processor_power *pwr = &pr->power; in lapic_timer_check_state() 150 pr->power.timer_broadcast_on_state = state; in lapic_timer_check_state() 157 if (pr->power.timer_broadcast_on_state < INT_MAX) in __lapic_timer_propagate_broadcast() 174 int state = cx - pr->power.states; in lapic_timer_state_broadcast() 176 if (state >= pr->power.timer_broadcast_on_state) { in lapic_timer_state_broadcast() 264 pr->power.states[ACPI_STATE_C2].type = ACPI_STATE_C2; in acpi_processor_get_power_info_fadt() 265 pr->power.states[ACPI_STATE_C3].type = ACPI_STATE_C3; in acpi_processor_get_power_info_fadt() 278 pr->power.states[ACPI_STATE_C2].address = pr->pblk + 4; in acpi_processor_get_power_info_fadt() 279 pr->power.states[ACPI_STATE_C3].address = pr->pblk + 5; in acpi_processor_get_power_info_fadt() 282 pr->power.states[ACPI_STATE_C2].latency = acpi_gbl_FADT.c2_latency; in acpi_processor_get_power_info_fadt() [all …]
D	device_pm.c	73 device->parent->power.state : ACPI_STATE_D0; in acpi_device_get_power() 81 if (device->power.flags.power_resources) { in acpi_device_get_power() 86 if (device->power.flags.explicit_get) { in acpi_device_get_power() 114 if (!device->power.flags.ignore_parent && device->parent in acpi_device_get_power() 115 && device->parent->power.state == ACPI_STATE_UNKNOWN in acpi_device_get_power() 117 device->parent->power.state = ACPI_STATE_D0; in acpi_device_get_power() 130 if (adev->power.states[state].flags.explicit_set) { in acpi_dev_pm_explicit_set() 160 if (state == device->power.state) { in acpi_device_set_power() 174 if (!device->power.states[ACPI_STATE_D3_COLD].flags.valid) in acpi_device_set_power() 176 } else if (!device->power.states[state].flags.valid) { in acpi_device_set_power() [all …]
D	power.c	444 if (!adev->power.flags.power_resources) in acpi_power_add_remove_device() 449 &adev->power.states[state].resources, in acpi_power_add_remove_device() 671 struct list_head list = &device->power.states[i].resources; in acpi_power_get_inferred_state() 686 state = device->power.states[ACPI_STATE_D3_COLD].flags.valid ? in acpi_power_get_inferred_state() 696 return acpi_power_on_list(&device->power.states[state].resources); in acpi_power_on_resources() 706 if (device->power.state == state \|\| !device->flags.power_manageable) in acpi_power_transition() 709 if ((device->power.state < ACPI_STATE_D0) in acpi_power_transition() 710 \|\| (device->power.state > ACPI_STATE_D3_COLD)) in acpi_power_transition() 720 &device->power.states[state].resources); in acpi_power_transition() 722 if (!result && device->power.state < ACPI_STATE_D3_COLD) in acpi_power_transition() [all …]
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
D	scpsys.txt	`4 The System Control Processor System (SCPSYS) has several power management 7 The System Power Manager (SPM) inside the SCPSYS is for the MTCMOS power 11 power/power_domain.txt. It provides the power domains defined in 12 include/dt-bindings/power/mt8173-power.h. 16 - #power-domain-cells: Must be 1 22 before enabling certain power domains. 27 #power-domain-cells = <1>; 42 power-domains = <&scpsys MT8173_POWER_DOMAIN_AUDIO>;`
/linux-4.4.14/Documentation/devicetree/bindings/sound/
D	st,sta350.txt	`12 - power-down-gpios: a GPIO spec for the power down pin. If specified, 23 0: 2-channel (full-bridge) power, 2-channel data-out 24 1: 2 (half-bridge). 1 (full-bridge) on-board power 48 - st,ffx-power-output-mode: string 49 The FFX power output mode selects how the FFX output timing is 53 - "full-power-mode" 57 Only required for "st,ffx-power-output-mode" == 66 - st,max-power-use-mpcc: 70 - st,max-power-corr: 71 If present, power bridge correction for THD reduction near maximum [all …]`
D	st,sta32x.txt	`12 - power-down-gpios: a GPIO spec for the power down pin. If specified, 23 0: 2-channel (full-bridge) power, 2-channel data-out 24 1: 2 (half-bridge). 1 (full-bridge) on-board power 49 Only required for "st,ffx-power-output-mode" == 55 - st,max-power-use-mpcc: 59 - st,max-power-corr: 60 If present, power bridge correction for THD reduction near maximum 61 power output is enabled. 80 power-down-gpios = <&gpio1 16 0>; 82 // (full-bridge) power, [all …]`
D	tpa6130a2.txt	`14 - Vdd-supply - <phandle> - power supply regulator 18 - power-gpio - gpio pin to power the device 26 power-gpio = <&gpio4 2 GPIO_ACTIVE_HIGH>;`
D	tlv320aic32x4.txt	`9 "iov" - digital IO power supply 10 "ldoin" - LDO power supply 11 "dv" - Digital core power supply 12 "av" - Analog core power supply`
/linux-4.4.14/drivers/soc/rockchip/
D	Kconfig	`7 bool "Rockchip generic power domain" 11 Say y here to enable power domain support. 12 In order to meet high performance and low power requirements, a power 13 management unit is designed or saving power when RK3288 in low power 14 mode. The RK3288 PMU is dedicated for managing the power of the whole chip.`
/linux-4.4.14/include/linux/
D	pm_runtime.h	60 return dev->power.ignore_children in pm_children_suspended() 61 \|\| !atomic_read(&dev->power.child_count); in pm_children_suspended() 66 atomic_inc(&dev->power.usage_count); in pm_runtime_get_noresume() 71 atomic_add_unless(&dev->power.usage_count, -1, 0); in pm_runtime_put_noidle() 76 return dev->power.run_wake; in device_run_wake() 81 dev->power.run_wake = enable; in device_set_run_wake() 86 return dev->power.runtime_status == RPM_SUSPENDED in pm_runtime_suspended() 87 && !dev->power.disable_depth; in pm_runtime_suspended() 92 return dev->power.runtime_status == RPM_ACTIVE in pm_runtime_active() 93 \|\| dev->power.disable_depth; in pm_runtime_active() [all …]
D	pm_wakeup.h	83 return dev->power.can_wakeup; in device_can_wakeup() 88 return dev->power.can_wakeup && !!dev->power.wakeup; in device_may_wakeup() 116 dev->power.can_wakeup = capable; in device_set_wakeup_capable() 121 return dev->power.can_wakeup; in device_can_wakeup() 149 dev->power.should_wakeup = true; in device_wakeup_enable() 155 dev->power.should_wakeup = false; in device_wakeup_disable() 161 dev->power.should_wakeup = enable; in device_set_wakeup_enable() 174 return dev->power.can_wakeup && dev->power.should_wakeup; in device_may_wakeup()
D	lcd.h	`50 int (early_set_power)(struct lcd_device , int power); 52 int (r_early_set_power)(struct lcd_device , int power); 54 int (set_power)(struct lcd_device , int power); 105 static inline void lcd_set_power(struct lcd_device *ld, int power) in lcd_set_power() argument 109 ld->ops->set_power(ld, power); in lcd_set_power()`
/linux-4.4.14/arch/arm/boot/dts/
D	r8a73a4.dtsi	`31 power-domains = <&pd_a2sl>; 37 power-domains = <&pd_d4>; 51 power-domains = <&pd_a3bc>; 57 power-domains = <&pd_a3bc>; 100 power-domains = <&pd_a3sp>; 111 power-domains = <&pd_a3sp>; 122 power-domains = <&pd_c5>; 167 power-domains = <&pd_c4>; 202 power-domains = <&pd_c4>; 233 power-domains = <&pd_c5>; [all …]`
D	r8a7740.dtsi	`28 power-domains = <&pd_a3sm>; 43 power-domains = <&pd_a4s>; 53 power-domains = <&pd_d4>; 62 power-domains = <&pd_c5>; 88 power-domains = <&pd_a4s>; 110 power-domains = <&pd_a4s>; 132 power-domains = <&pd_a4s>; 154 power-domains = <&pd_a4s>; 163 power-domains = <&pd_a4s>; 180 power-domains = <&pd_a4r>; [all …]`
D	sh73a0.dtsi	`30 power-domains = <&pd_a2sl>; 37 power-domains = <&pd_a2sl>; 62 power-domains = <&pd_a4bc1>; 71 power-domains = <&pd_a4bc0>; 86 power-domains = <&pd_c5>; 111 power-domains = <&pd_a4s>; 133 power-domains = <&pd_a4s>; 155 power-domains = <&pd_a4s>; 177 power-domains = <&pd_a4s>; 191 power-domains = <&pd_a3sp>; [all …]`
D	r8a7794.dtsi	`75 power-domains = <&cpg_clocks>; 88 power-domains = <&cpg_clocks>; 101 power-domains = <&cpg_clocks>; 114 power-domains = <&cpg_clocks>; 127 power-domains = <&cpg_clocks>; 140 power-domains = <&cpg_clocks>; 153 power-domains = <&cpg_clocks>; 163 power-domains = <&cpg_clocks>; 183 power-domains = <&cpg_clocks>; 214 power-domains = <&cpg_clocks>; [all …]`
D	r8a7791.dtsi	`94 power-domains = <&cpg_clocks>; 107 power-domains = <&cpg_clocks>; 120 power-domains = <&cpg_clocks>; 133 power-domains = <&cpg_clocks>; 146 power-domains = <&cpg_clocks>; 159 power-domains = <&cpg_clocks>; 172 power-domains = <&cpg_clocks>; 185 power-domains = <&cpg_clocks>; 193 power-domains = <&cpg_clocks>; 211 power-domains = <&cpg_clocks>; [all …]`
D	r8a7779.dtsi	`176 power-domains = <&cpg_clocks>; 187 power-domains = <&cpg_clocks>; 198 power-domains = <&cpg_clocks>; 209 power-domains = <&cpg_clocks>; 219 power-domains = <&cpg_clocks>; 229 power-domains = <&cpg_clocks>; 239 power-domains = <&cpg_clocks>; 249 power-domains = <&cpg_clocks>; 259 power-domains = <&cpg_clocks>; 269 power-domains = <&cpg_clocks>; [all …]`
D	exynos4.dtsi	`85 pd_mfc: mfc-power-domain@10023C40 { 88 #power-domain-cells = <0>; 91 pd_g3d: g3d-power-domain@10023C60 { 94 #power-domain-cells = <0>; 97 pd_lcd0: lcd0-power-domain@10023C80 { 100 #power-domain-cells = <0>; 103 pd_tv: tv-power-domain@10023C20 { 106 #power-domain-cells = <0>; 107 power-domains = <&pd_lcd0>; 110 pd_cam: cam-power-domain@10023C00 { [all …]`
D	r7s72100.dtsi	`89 #power-domain-cells = <0>; 161 power-domains = <&cpg_clocks>; 174 power-domains = <&cpg_clocks>; 187 power-domains = <&cpg_clocks>; 200 power-domains = <&cpg_clocks>; 213 power-domains = <&cpg_clocks>; 226 power-domains = <&cpg_clocks>; 239 power-domains = <&cpg_clocks>; 252 power-domains = <&cpg_clocks>; 264 power-domains = <&cpg_clocks>; [all …]`
D	r8a7790.dtsi	`137 power-domains = <&cpg_clocks>; 150 power-domains = <&cpg_clocks>; 163 power-domains = <&cpg_clocks>; 176 power-domains = <&cpg_clocks>; 189 power-domains = <&cpg_clocks>; 202 power-domains = <&cpg_clocks>; 210 power-domains = <&cpg_clocks>; 228 power-domains = <&cpg_clocks>; 248 power-domains = <&cpg_clocks>; 265 power-domains = <&cpg_clocks>; [all …]`
D	r8a7778.dtsi	`56 power-domains = <&cpg_clocks>; 156 power-domains = <&cpg_clocks>; 167 power-domains = <&cpg_clocks>; 178 power-domains = <&cpg_clocks>; 189 power-domains = <&cpg_clocks>; 201 power-domains = <&cpg_clocks>; 216 power-domains = <&cpg_clocks>; 231 power-domains = <&cpg_clocks>; 299 power-domains = <&cpg_clocks>; 309 power-domains = <&cpg_clocks>; [all …]`
D	kirkwood-netxbig.dtsi	`66 label = "Back power switch (on\|auto)"; 72 label = "Back power switch (auto\|off)"; 130 blue-power { 131 label = "netxbig:blue:power"; 140 red-power { 141 label = "netxbig:red:power"; 216 pmx_button_power_off: pmx-button-power-off { 220 pmx_button_power_on: pmx-button-power-on {`
D	kirkwood-iconnect.dts	`46 pmx_led_power_blue: pmx-led-power-blue { 50 pmx_led_power_red: pmx-power-red { 101 power-blue { 102 label = "power:blue"; 106 power-red { 107 label = "power:red";`
D	bcm4709-buffalo-wxr-1900dhp.dts	`36 power-amber { 37 label = "bcm53xx:amber:power"; 42 power-white { 43 label = "bcm53xx:white:power"; 90 power {`
D	at91sam9x5dm.dtsi	`63 power-supply = <&bl_reg>; 69 regulator-name = "backlight-power-supply"; 78 power-supply = <&panel_reg>; 96 regulator-name = "panel-power-supply";`
D	omap3-evm-common.dtsi	`55 twl_power: power { 56 compatible = "ti,twl4030-power-omap3-evm", "ti,twl4030-power-idle"; 109 cap-power-off-card; 152 power = <50>;`
D	kirkwood-blackarmor-nas220.dts	`55 blue-power { 56 label = "nas220:blue:power"; 120 pmx_power_sata0: pmx-power-sata0 { 125 pmx_power_sata1: pmx-power-sata1 { 135 pmx_button_power: pmx-button-power {`
D	exynos3250.dtsi	`161 pd_cam: cam-power-domain@10023C00 { 164 #power-domain-cells = <0>; 167 pd_mfc: mfc-power-domain@10023C40 { 170 #power-domain-cells = <0>; 173 pd_g3d: g3d-power-domain@10023C60 { 176 #power-domain-cells = <0>; 179 pd_lcd0: lcd0-power-domain@10023C80 { 182 #power-domain-cells = <0>; 185 pd_isp: isp-power-domain@10023CA0 { 188 #power-domain-cells = <0>; [all …]`
D	exynos4415.dtsi	`131 pd_cam: cam-power-domain@10024000 { 134 #power-domain-cells = <0>; 137 pd_tv: tv-power-domain@10024020 { 140 #power-domain-cells = <0>; 143 pd_mfc: mfc-power-domain@10024040 { 146 #power-domain-cells = <0>; 149 pd_g3d: g3d-power-domain@10024060 { 152 #power-domain-cells = <0>; 155 pd_lcd0: lcd0-power-domain@10024080 { 158 #power-domain-cells = <0>; [all …]`
D	exynos5250.dtsi	`117 pd_gsc: gsc-power-domain@10044000 { 120 #power-domain-cells = <0>; 123 pd_mfc: mfc-power-domain@10044040 { 126 #power-domain-cells = <0>; 129 pd_disp1: disp1-power-domain@100440A0 { 132 #power-domain-cells = <0>; 265 power-domains = <&pd_mfc>; 721 power-domains = <&pd_gsc>; 731 power-domains = <&pd_gsc>; 741 power-domains = <&pd_gsc>; [all …]`
D	bcm4709-netgear-r7000.dts	`30 power-white { 31 label = "bcm53xx:white:power"; 36 power-amber { 37 label = "bcm53xx:amber:power";`
D	exynos4x12.dtsi	`53 pd_isp: isp-power-domain@10023CA0 { 56 #power-domain-cells = <0>; 132 power-domains = <&pd_isp>; 143 power-domains = <&pd_isp>; 154 power-domains = <&pd_isp>; 225 power-domains = <&pd_isp>; 236 power-domains = <&pd_isp>; 247 power-domains = <&pd_isp>; 258 power-domains = <&pd_isp>; 269 power-domains = <&pd_isp>; [all …]`
D	armada-370-seagate-nas-xbay.dtsi	`130 regulator-name = "SATA0 power"; 141 regulator-name = "SATA1 power"; 185 white-power { 186 label = "dart:white:power"; 191 red-power { 192 label = "dart:red:power";`
D	bcm4708-smartrg-sr400ac.dts	`30 power-white { 31 label = "bcm53xx:white:power"; 36 power-amber { 37 label = "bcm53xx:amber:power";`
D	kirkwood-dnskw.dtsi	`68 pmx_led_power: pmx-led-power { 84 pmx_button_power: pmx-button-power { 92 pmx_power_off: pmx-power-off { 96 pmx_power_back_on: pmx-power-back-on { 100 pmx_power_sata0: pmx-power-sata0 { 104 pmx_power_sata1: pmx-power-sata1 {`
D	exynos5420.dtsi	`180 power-domains = <&mfc_pd>; 251 gsc_pd: power-domain@10044000 { 254 #power-domain-cells = <0>; 259 isp_pd: power-domain@10044020 { 262 #power-domain-cells = <0>; 265 mfc_pd: power-domain@10044060 { 270 #power-domain-cells = <0>; 273 msc_pd: power-domain@10044120 { 276 #power-domain-cells = <0>; 279 disp_pd: power-domain@100440C0 { [all …]`
D	stih418.dtsi	`58 reset-names = "power", "softreset"; 72 reset-names = "power", "softreset"; 84 reset-names = "power", "softreset"; 98 reset-names = "power", "softreset";`
/linux-4.4.14/drivers/pcmcia/
D	pxa2xx_mainstone.c	91 unsigned long power = 0; in mst_pcmcia_configure_socket() local 95 case 0: power \|= MST_PCMCIA_PWR_VCC_0; break; in mst_pcmcia_configure_socket() 96 case 33: power \|= MST_PCMCIA_PWR_VCC_33; break; in mst_pcmcia_configure_socket() 97 case 50: power \|= MST_PCMCIA_PWR_VCC_50; break; in mst_pcmcia_configure_socket() 105 case 0: power \|= MST_PCMCIA_PWR_VPP_0; break; in mst_pcmcia_configure_socket() 106 case 120: power \|= MST_PCMCIA_PWR_VPP_120; break; in mst_pcmcia_configure_socket() 109 power \|= MST_PCMCIA_PWR_VPP_VCC; in mst_pcmcia_configure_socket() 118 power \|= MST_PCMCIA_RESET; in mst_pcmcia_configure_socket() 121 case 0: MST_PCMCIA0 = power; break; in mst_pcmcia_configure_socket() 122 case 1: MST_PCMCIA1 = power; break; in mst_pcmcia_configure_socket()
D	pxa2xx_trizeps4.c	30 extern void board_pcmcia_power(int power); 99 unsigned short power = 0; in trizeps_pcmcia_configure_socket() local 103 case 0: power &= 0xfc; break; in trizeps_pcmcia_configure_socket() 104 case 33: power \|= ConXS_BCR_S0_VCC_3V3; break; in trizeps_pcmcia_configure_socket() 114 case 0: power &= 0xf3; break; in trizeps_pcmcia_configure_socket() 115 case 33: power \|= ConXS_BCR_S0_VPP_3V3; break; in trizeps_pcmcia_configure_socket() 128 board_pcmcia_power(power); in trizeps_pcmcia_configure_socket()
/linux-4.4.14/Documentation/sound/alsa/
D	powersave.txt	4 AC97 and HD-audio drivers have the automatic power-saving mode. 8 With the automatic power-saving, the driver turns off the codec power 10 the device and/or no analog loopback is set, the power disablement is 11 done fully or partially. It'll save a certain power consumption, thus 14 The time-out for automatic power-off can be specified via power_save 17 power-saving. The default value of timeout is given via 26 automatic power-save mode with 10 seconds, write to 32 Note that you might hear click noise/pop when changing the power 34 power-down to the active state. These are often hardly to fix, so 38 power_save_controller. This enables/disables the power-save mode of [all …]
/linux-4.4.14/drivers/video/fbdev/exynos/
D	s6e8ax0.c	52 unsigned int power; member 666 static int s6e8ax0_set_power(struct lcd_device *ld, int power) in s6e8ax0_set_power() argument 672 if (power != FB_BLANK_UNBLANK && power != FB_BLANK_POWERDOWN && in s6e8ax0_set_power() 673 power != FB_BLANK_NORMAL) { in s6e8ax0_set_power() 678 if ((power == FB_BLANK_UNBLANK) && ops->set_blank_mode) { in s6e8ax0_set_power() 680 if ((POWER_IS_ON(power) && POWER_IS_OFF(lcd->power)) in s6e8ax0_set_power() 681 \|\| (POWER_IS_ON(power) && POWER_IS_NRM(lcd->power))) { in s6e8ax0_set_power() 682 ret = ops->set_blank_mode(lcd_to_master(lcd), power); in s6e8ax0_set_power() 683 if (!ret && lcd->power != power) in s6e8ax0_set_power() 684 lcd->power = power; in s6e8ax0_set_power() [all …]
/linux-4.4.14/Documentation/scsi/
D	link_power_management_policy.txt	`1 This parameter allows the user to set the link (interface) power management. 7 least possible power when possible. This may 9 when coming out of lower power states. 11 max_performance Generally, this means no power management. Tell 13 over power management. 15 medium_power Tell the controller to enter a lower power state 16 when possible, but do not enter the lowest power`
/linux-4.4.14/Documentation/power/regulator/
D	overview.txt	10 The intention is to allow systems to dynamically control regulator power output 11 in order to save power and prolong battery life. This applies to both voltage 24 o Regulator - Electronic device that supplies power to other devices. 35 o Consumer - Electronic device that is supplied power by a regulator. 40 power supply. Its supply voltage is set by the hardware, 47 o Power Domain - Electronic circuit that is supplied its input power by the 48 output power of a regulator, switch or by another power 59 That is one regulator and three power domains: 69 A power domain may have regulators that are supplied power 76 This gives us two regulators and two power domains: [all …]
D	design.txt	`12 - It is not possible to automatically determine the power configuration 14 have different power requirements, and not all components with power 25 requirement to do any runtime configuration of their power beyond 28 - Many of the power supplies in the system will be shared between many`
/linux-4.4.14/include/trace/events/
D	thermal.h	`115 unsigned long cdev_state, u32 power), 117 TP_ARGS(cpus, freq, cdev_state, power), 123 __field(u32, power ) 131 __entry->power = power; 136 __entry->power) 169 unsigned long cdev_state, u32 power), 171 TP_ARGS(cdev, freq, cdev_state, power), 177 __field(u32, power ) 184 __entry->power = power; 189 __entry->power)`
D	rpm.h	`38 &dev->power.usage_count); 39 __entry->disable_depth = dev->power.disable_depth; 40 __entry->runtime_auto = dev->power.runtime_auto; 41 __entry->request_pending = dev->power.request_pending; 42 __entry->irq_safe = dev->power.irq_safe; 44 &dev->power.child_count);`
/linux-4.4.14/drivers/power/reset/
D	Kconfig	2 bool "Board level reset or power off" 5 or shut it down, by manipulating the main power supply on the board. 7 Say Y here to enable board reset and power off 12 bool "ams AS3722 power-off driver" 15 This driver supports turning off board via a ams AS3722 power-off. 53 bool "GPIO power-off driver" 57 If your board needs a GPIO high/low to power down, say Y and 69 bool "Hisilicon power-off driver" 75 bool "IMX6 power-off driver" 78 This driver support power off external PMIC by PMIC_ON_REQ on i.mx6 [all …]
/linux-4.4.14/tools/
D	Makefile	`50 $(call descend,power/$@) 53 $(call descend,power/$@) 76 $(call descend,power/x86/$@) 90 $(call descend,power/$(@:_install=),install) 93 $(call descend,power/$(@:_install=),install) 102 $(call descend,power/x86/$(@:_install=),install) 116 $(call descend,power/acpi,clean) 119 $(call descend,power/cpupower,clean) 137 $(call descend,power/x86/$(@:_clean=),clean)`
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
D	power_supply.txt	`4 - power-supplies : This property is added to a supply in order to list the 5 devices which supply it power, referenced by their phandles. 9 usb-charger: power@e { 14 ac-charger: power@c { 22 power-supplies = <&usb-charger>, <&ac-charger>;`
D	axp20x_usb_power.txt	`1 AXP20x USB power supply 4 -compatible: "x-powers,axp202-usb-power-supply" 31 usb-power-supply: usb-power-supply { 32 compatible = "x-powers,axp202-usb-power-supply";`
D	qnap-poweroff.txt	`3 QNAP NAS devices have a microcontroller controlling the main power 6 microcontroller to turn the power off. This driver adds a handler to 7 pm_power_off which is called to turn the power off. 13 - compatible: Should be "qnap,power-off" or "synology,power-off"`
D	msm-poweroff.txt	`3 A power supply hold (ps-hold) bit is set to power the msm chipsets. 5 between poweroff and restart is determined by unique power manager IC`
/linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/
D	power_domain.txt	`3 UX500 supports multiple PM domains which are used to gate power to one or 13 - #power-domain-cells : Number of cells in a power domain specifier, must be 1. 18 #power-domain-cells = <1>; 24 - power-domains: A phandle and PM domain specifier. Below are the list of 34 power-domains = <&pm_domains DOMAIN_VAPE>`
/linux-4.4.14/Documentation/power/
D	states.txt	10 /sys/power/state file. Those strings may be "mem", "standby", "freeze" and 17 respectively. In that case, "mem" is always present in /sys/power/state, 20 in /sys/power/state in addition to "mem". If the system supports three 21 non-hibernation sleep states, "freeze" will be present in /sys/power/state in 33 space and putting all I/O devices into low-power states (possibly 34 lower-power than available at run time), such that the processors can 46 This state, if supported, offers moderate, though real, power savings, while 48 operating state is lost (the CPU retains power), so the system easily starts up 51 In addition to freezing user space and putting all I/O devices into low-power 63 This state, if supported, offers significant power savings as everything in the [all …]
D	devices.txt	8 Most of the code in Linux is device drivers, so most of the Linux power 14 power management goals, emphasizing the models and interfaces that are 21 Drivers will use one or both of these models to put devices into low-power 25 Drivers can enter low-power states as part of entering system-wide 26 low-power states like "suspend" (also known as "suspend-to-RAM"), or 32 cleanly power down hardware and software subsystems, then reactivate 36 leave the low-power state. This feature may be enabled or disabled 37 using the relevant /sys/devices/.../power/wakeup file (for Ethernet 39 purpose); enabling it may cost some power usage, but let the whole 40 system enter low-power states more often. [all …]
D	power_supply_class.txt	1 Linux power supply class 6 Power supply class used to represent battery, UPS, AC or DC power supply 10 every power supply out there. Attributes are available via sysfs and uevent 15 power supply, specific monitoring hardware may not be able to provide them 20 if it will be found that some attribute is applicable to many power supply 25 AC/USB power supply online status. (Note that specific details of the 38 kind of power supply, and can process/present them to a user in consistent 39 manner. Results for different power supplies and machines are also directly 42 See drivers/power/ds2760_battery.c and drivers/power/pda_power.c for the 84 AUTHENTIC - indicates the power supply (battery or charger) connected [all …]
D	pci.txt	5 An overview of concepts and the Linux kernel's interfaces related to PCI power 9 This document only covers the aspects of power management specific to PCI 11 power management refer to Documentation/power/devices.txt and 12 Documentation/power/runtime_pm.txt. 27 In general, power management is a feature allowing one to save energy by putting 28 devices into states in which they draw less power (low-power states) at the 31 Usually, a device is put into a low-power state when it is underutilized or 33 again, it has to be put back into the "fully functional" state (full-power 38 PCI devices may be put into low-power states in two ways, by using the device 41 approach, that is referred to as the native PCI power management (native PCI PM) [all …]
D	interface.txt	4 The power management subsystem provides a unified sysfs interface to 6 running. The interface exists in /sys/power/ directory (assuming sysfs 9 /sys/power/state controls system power state. Reading from this file 16 Documentation/power/states.txt for a description of each of those 20 /sys/power/disk controls the operating mode of the suspend-to-disk 26 Additionally, /sys/power/disk can be used to turn on one of the two testing 29 /sys/power/state will cause the kernel to disable nonboot CPUs and freeze 31 in the 'test' mode, writing 'disk' to /sys/power/state will cause the kernel 50 /sys/power/image_size controls the size of the image created by 62 /sys/power/pm_trace controls the code which saves the last PM event point in
D	runtime_pm.txt	9 Support for runtime power management (runtime PM) of I/O devices is provided 10 at the power management core (PM core) level by means of: 12 * The power management workqueue pm_wq in which bus types and device drivers can 15 them to be synchronized with system-wide power transitions (suspend to RAM, 17 include/linux/pm_runtime.h and defined in kernel/power/main.c. 19 * A number of runtime PM fields in the 'power' member of 'struct device' (which 26 * A set of helper functions defined in drivers/base/power/runtime.c that can be 90 put into a low power state. It is supposed to mean, however, that the 107 mechanism allowing the device to request a change of its power state, such as 111 low-power state during the execution of the suspend callback, it is expected [all …]
D	charger-manager.txt	9 Charger Manager is a platform_driver with power-supply-class entries. 21 A system may have multiple chargers (or power sources) and some of 23 own power-supply-class and each power-supply-class can provide 26 shows combined information as a single power-supply-class. 34 supposed to be kept suspended. That, in turn, incurs unnecessary power 35 consumption and slow down charging process. Or even, such peak power 37 (external power input < device power consumption), which not 117 : The power-supply-class name of the battery. Default is 125 an external power source is attached. 156 : An array ending with NULL that has power-supply-class names of [all …]
D	00-INDEX	`10 - How drivers interact with system-wide power management 16 - Power management user interface in /sys/power 26 - Tells userspace about battery, UPS, AC or DC power supply properties 32 - System power management states`
D	basic-pm-debugging.txt	`8 # echo reboot > /sys/power/disk 9 # echo disk > /sys/power/state 21 # echo platform > /sys/power/disk 22 # echo disk > /sys/power/state 30 # echo shutdown > /sys/power/disk 31 # echo disk > /sys/power/state 33 (it is similar to the "reboot" mode, but it requires you to press the power 43 there is the file /sys/power/pm_test that can be used to make the hibernation 69 /sys/power/pm_test (eg. "devices" to test the freezing of processes and 74 # echo devices > /sys/power/pm_test [all …]`
D	drivers-testing.txt	`17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt 26 (see: Documentation/power/basic-pm-debugging.txt, 1). 29 "platform" modes (see: Documentation/power/basic-pm-debugging.txt, 1). 37 e) Try the test modes of suspend (see: Documentation/power/basic-pm-debugging.txt, 42 (see: Documentation/power/basic-pm-debugging.txt, 2).`
/linux-4.4.14/Documentation/devicetree/bindings/input/
D	ti,palmas-pwrbutton.txt	`1 Texas Instruments Palmas family power button module 7 This module provides a simple power button event via an Interrupt. 11 - "ti,palmas-pwrbutton": For Palmas compatible power on button 13 - interrupts: Interrupt number of power button submodule on device. 17 - ti,palmas-long-press-seconds: Duration in seconds which the power 18 button should be kept pressed for Palmas to power off automatically. 22 which the power button should be kept pressed for Palmas to register`
D	da9062-onkey.txt	`17 - dlg,disable-key-power : Disable power-down using a long key-press. If this 20 triggered power down is enabled and the OnKey will support both KEY_POWER 29 dlg,disable-key-power;`
D	tps65218-pwrbutton.txt	`1 Texas Instruments TPS65218 power button 3 This driver provides a simple power button event via an Interrupt. 13 power-button {`
/linux-4.4.14/drivers/thermal/
D	cpu_cooling.c	60 u32 power; member 306 u64 power; in build_dyn_power_table() local 321 power = (u64)capacitance * freq_mhz * voltage_mv * voltage_mv; in build_dyn_power_table() 322 do_div(power, 1000000000); in build_dyn_power_table() 328 power_table[i].power = power; in build_dyn_power_table() 360 return pt[i - 1].power; in cpu_freq_to_power() 364 u32 power) in cpu_power_to_freq() argument 370 if (power < pt[i].power) in cpu_power_to_freq() 423 u32 power) in get_static_power() argument 432 power = 0; in get_static_power() [all …]
D	devfreq_cooling.c	260 u64 power; in get_dynamic_power() local 268 power = (u64)dfc_power->dyn_power_coeff * freq_mhz * voltage * voltage; in get_dynamic_power() 269 do_div(power, 1000000000); in get_dynamic_power() 271 return power; in get_dynamic_power() 276 u32 power) in devfreq_cooling_get_requested_power() argument 301 power = dyn_power + static_power; in devfreq_cooling_get_requested_power() 309 u32 power) in devfreq_cooling_state2power() argument 321 power = dfc->power_table[state] + static_power; in devfreq_cooling_state2power() 327 u32 power, unsigned long *state) in devfreq_cooling_power2state() argument 340 dyn_power = power - static_power; in devfreq_cooling_power2state() [all …]
/linux-4.4.14/drivers/clk/mxs/
D	clk-pll.c	`32 u8 power; member 42 writel_relaxed(1 << pll->power, pll->base + SET); in clk_pll_prepare() 53 writel_relaxed(1 << pll->power, pll->base + CLR); in clk_pll_unprepare() 89 void __iomem *base, u8 power, unsigned long rate) in mxs_clk_pll() argument 107 pll->power = power; in mxs_clk_pll()`
/linux-4.4.14/net/wireless/
D	genregdb.awk	`62 power = $6 67 sub(/$/, "", power) 68 sub(/$,/, "", power) 74 power = 10 * log(power)/log(10) 119 …printf "\t\tREG_RULE_EXT(%d, %d, %d, %d, %.0f, %d, %s),\n", start, end, bw, gain, power, dfs_cac, …`
/linux-4.4.14/drivers/powercap/
D	Kconfig	`2 # Generic power capping sysfs interface configuration 8 The power capping sysfs interface allows kernel subsystems to expose power 11 power zones representing parts of the system that can be subject to power 24 technology which allows power limits to be enforced and monitored on`
/linux-4.4.14/Documentation/devicetree/bindings/clock/
D	renesas,r8a7778-cpg-clocks.txt	`15 - #power-domain-cells: Must be 0 17 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed 19 "power-domains" property, as documented by the generic PM domain bindings in 20 Documentation/devicetree/bindings/power/power_domain.txt. 35 #power-domain-cells = <0>; 46 power-domains = <&cpg_clocks>;`
D	renesas,r8a7779-cpg-clocks.txt	`17 - #power-domain-cells: Must be 0 19 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed 21 "power-domains" property, as documented by the generic PM domain bindings in 22 Documentation/devicetree/bindings/power/power_domain.txt. 37 #power-domain-cells = <0>; 48 power-domains = <&cpg_clocks>;`
D	renesas,rz-cpg-clocks.txt	`19 - #power-domain-cells: Must be 0 21 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed 23 "power-domains" property, as documented by the generic PM domain bindings in 24 Documentation/devicetree/bindings/power/power_domain.txt. 39 #power-domain-cells = <0>; 52 power-domains = <&cpg_clocks>;`
D	renesas,rcar-gen2-cpg-clocks.txt	`25 - #power-domain-cells: Must be 0 27 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed 29 "power-domains" property, as documented by the generic PM domain bindings in 30 Documentation/devicetree/bindings/power/power_domain.txt. 47 #power-domain-cells = <0>; 58 power-domains = <&cpg_clocks>;`
D	renesas,cpg-mssr.txt	`34 - #power-domain-cells: Must be 0 36 power-managed through Module Standby should refer to the CPG device 37 node in their "power-domains" property, as documented by the generic PM 39 Documentation/devicetree/bindings/power/power_domain.txt. 53 #power-domain-cells = <0>; 67 power-domains = <&cpg>;`
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
D	gpio-poweroff.txt	`1 Driver a GPIO line that can be used to turn the power off. 3 The driver supports both level triggered and edge triggered power off. 10 and drive active, so triggering a level triggered power off 12 triggering positive edge triggered power off. After a delay of 100ms, 14 triggering negative edge triggered power off. After another 100ms 15 delay the GPIO is driver active again. If the power is still on and 22 low to power down the board set it to "Active Low", otherwise set`
/linux-4.4.14/Documentation/usb/
D	power-management.txt	33 component is "suspended" it is in a nonfunctional low-power state; it 35 "resumed" (returned to a functional full-power state) when the kernel 47 covered to some extent (see Documentation/power/*.txt for more 67 by pressing a power button or opening the cover. 118 We can categorize power management events in two broad classes: 131 The user interface for controlling dynamic PM is located in the power/ 133 /sys/bus/usb/devices/.../power/ where "..." is the device's ID. The 143 power/wakeup 154 power/control 172 power/autosuspend_delay_ms [all …]
D	chipidea.txt	`56 7) A-device power down the bus. 60 A-device should disconnect with B-device and power down the bus. 79 echo enabled > /sys/bus/platform/devices/ci_hdrc.0/power/wakeup 81 echo enabled > /sys/bus/platform/devices/2184000.usb/power/wakeup 83 echo enabled > /sys/bus/platform/devices/20c9000.usbphy/power/wakeup 85 echo enabled > /sys/bus/usb/devices/usb1/power/wakeup 87 echo enabled > /sys/bus/usb/devices/1-1/power/wakeup`
D	persist.txt	14 The technical term is "power session". 16 If a USB device's power session is interrupted then the system is 24 controller loses power during a system suspend, then when the system 43 Loss of power isn't the only mechanism to worry about. Anything that 44 interrupts a power session will have the same effect. For example, 48 controllers. Result: all the power sessions are destroyed and again 57 has happened; look for lines saying "root hub lost power or was reset". 70 persist across a power-session disruption. 74 reset or otherwise had lost power) then it applies a persistence check 77 can't work once the power session is gone. Instead it issues a USB [all …]
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
D	nvidia,tegra20-pmc.txt	5 modes. It provides power-gating controllers for SoC and CPU power-islands. 32 - nvidia,core-power-req-active-high : Boolean, core power request active-high 34 - nvidia,combined-power-req : Boolean, combined power request for CPU & Core 35 - nvidia,cpu-pwr-good-en : Boolean, CPU power good signal (from PMIC to PMC) 39 - nvidia,cpu-pwr-good-time : CPU power good time in uS. 40 - nvidia,cpu-pwr-off-time : CPU power off time in uS. 42 Core power good time in uS. 43 - nvidia,core-pwr-off-time : Core power off time in uS. 49 processor and always being the first boot processor when chip is power on 85 nvidia,core-power-req-active-high;
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/
D	qcom,idle-state.txt	26 Retention: Retention is a low power state where the core is clock gated and 33 Standalone PC: A cpu can power down and warmboot if there is a sufficient time 35 to indicate a core entering a power down state without consulting any other 36 cpu or the system resources. This helps save power only on that core. The SPM 37 sequence for this idle state is programmed to power down the supply to the 38 core, wait for the interrupt, restore power to the core, and ensure the 40 resume. Applying power and resetting the core causes the core to warmboot 42 kernel. Entering a power down state for the cpu, needs to be done by trapping 49 modes. In a hierarchical power domain SoC, this means L2 and other caches can 52 power modes possible at this state is vast, the exit latency and the residency [all …]
D	qcom,saw2.txt	`5 power-controller that transitions a piece of hardware (like a processor or 6 subsystem) into and out of low power modes via a direct connection to 8 system, notifying them when a low power state is entered or exited. 47 power-controller@2099000 { 54 saw0: power-controller@f9089000 {`
/linux-4.4.14/Documentation/devicetree/bindings/media/i2c/
D	adv7343.txt	`13 - adi,power-mode-sleep-mode: on enable the current consumption is reduced to 16 - adi,power-mode-pll-ctrl: PLL and oversampling control. This control allows 19 - ad,adv7343-power-mode-dac: array configuring the power on/off DAC's 1..6, 38 adi,power-mode-sleep-mode; 39 adi,power-mode-pll-ctrl;`
/linux-4.4.14/Documentation/
D	dcdbas.txt	`5 management interrupts and host control actions (system power cycle or 6 power off after OS shutdown) on certain Dell systems. 48 to perform a power cycle or power off of the system after the OS has finished 53 to schedule the driver to perform a power cycle or power off host control 60 Dell OpenManage performs the following steps to execute a power cycle or 61 power off host control action using this driver: 74 perform a power cycle or power off host control action:`
/linux-4.4.14/Documentation/devicetree/bindings/iio/frequency/
D	adf4350.txt	`16 - adi,power-up-frequency: If set in Hz the PLL tunes to 59 - adi,output-power: Output power selection. 60 Valid values for the power mode are: 65 - adi,aux-output-power: Auxiliary output power selection. 66 Valid values for the power mode are: 81 adi,power-up-frequency = <2400000000>; 84 adi,output-power = <3>;`
/linux-4.4.14/drivers/staging/rtl8192u/ieee80211/
D	ieee80211_softmac_wx.c	519 if (wrqu->power.disabled) { in ieee80211_wx_set_power() 523 if (wrqu->power.flags & IW_POWER_TIMEOUT) { in ieee80211_wx_set_power() 525 ieee->ps_timeout = wrqu->power.value / 1000; in ieee80211_wx_set_power() 528 if (wrqu->power.flags & IW_POWER_PERIOD) { in ieee80211_wx_set_power() 531 ieee->ps_period = wrqu->power.value / 1000; in ieee80211_wx_set_power() 535 switch (wrqu->power.flags & IW_POWER_MODE) { in ieee80211_wx_set_power() 570 wrqu->power.disabled = 1; in ieee80211_wx_get_power() 574 wrqu->power.disabled = 0; in ieee80211_wx_get_power() 576 if ((wrqu->power.flags & IW_POWER_TYPE) == IW_POWER_TIMEOUT) { in ieee80211_wx_get_power() 577 wrqu->power.flags = IW_POWER_TIMEOUT; in ieee80211_wx_get_power() [all …]
/linux-4.4.14/Documentation/gpio/
D	board.txt	`34 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; 42 "led" function, and GPIO 1 as the "power" GPIO: 44 struct gpio_desc red, green, blue, power; 50 power = gpiod_get(dev, "power", GPIOD_OUT_HIGH); 52 The led GPIOs will be active-high, while the power GPIO will be active-low (i.e. 53 gpiod_is_active_low(power) will be true). 79 "\\_SB.GPI0") {1} // power 94 "power-gpios", 145 GPIO_LOOKUP("gpio.0", 1, "power", GPIO_ACTIVE_LOW), 156 struct gpio_desc red, green, blue, power; [all …]`
/linux-4.4.14/arch/arm/mach-pxa/include/mach/
D	palm27x.h	`16 extern void __init palm27x_mmc_init(int detect, int ro, int power, 19 static inline void palm27x_mmc_init(int detect, int ro, int power, in palm27x_mmc_init() argument 34 extern void __init palm27x_lcd_init(int power, 37 #define palm27x_lcd_init(power, mode) do {} while (0) argument`
/linux-4.4.14/arch/arm/mach-omap2/
D	usb-musb.c	`50 .power = 50, /* up to 100 mA */ 58 .power = 100, 81 musb_plat.power = board_data->power >> 1; in usb_musb_init()`
/linux-4.4.14/Documentation/networking/
D	README.ipw2100	45 parameters include, without limitation, RF power, spectrum usage, 127 disable boolean disable=1 /* Do not power the HW */ 205 off No power management. Radio is always on. 206 on Automatic power management 207 1-5 Different levels of power management. The higher the 208 number the greater the power savings, but with an impact to 214 period of time. For higher power savings, the interval between last 221 while power management is enabled. If this is the case, you will need 222 to try and find a firmware update for your AP, or disable power 223 management (via `iwconfig eth1 power off`) [all …]
/linux-4.4.14/drivers/staging/rtl8192e/
D	rtllib_softmac_wx.c	580 if (wrqu->power.disabled) { in rtllib_wx_set_power() 585 if (wrqu->power.flags & IW_POWER_TIMEOUT) { in rtllib_wx_set_power() 586 ieee->ps_timeout = wrqu->power.value / 1000; in rtllib_wx_set_power() 591 if (wrqu->power.flags & IW_POWER_PERIOD) in rtllib_wx_set_power() 592 ieee->ps_period = wrqu->power.value / 1000; in rtllib_wx_set_power() 594 switch (wrqu->power.flags & IW_POWER_MODE) { in rtllib_wx_set_power() 628 wrqu->power.disabled = 1; in rtllib_wx_get_power() 632 wrqu->power.disabled = 0; in rtllib_wx_get_power() 634 if ((wrqu->power.flags & IW_POWER_TYPE) == IW_POWER_TIMEOUT) { in rtllib_wx_get_power() 635 wrqu->power.flags = IW_POWER_TIMEOUT; in rtllib_wx_get_power() [all …]
/linux-4.4.14/drivers/xen/
D	xen-acpi-processor.c	70 dst_cx_states = kcalloc(_pr->power.count, in push_cxx_to_hypervisor() 75 for (ok = 0, i = 1; i <= _pr->power.count; i++) { in push_cxx_to_hypervisor() 76 cx = &_pr->power.states[i]; in push_cxx_to_hypervisor() 109 op.u.set_pminfo.power.count = ok; in push_cxx_to_hypervisor() 110 op.u.set_pminfo.power.flags.bm_control = _pr->flags.bm_control; in push_cxx_to_hypervisor() 111 op.u.set_pminfo.power.flags.bm_check = _pr->flags.bm_check; in push_cxx_to_hypervisor() 112 op.u.set_pminfo.power.flags.has_cst = _pr->flags.has_cst; in push_cxx_to_hypervisor() 113 op.u.set_pminfo.power.flags.power_setup_done = in push_cxx_to_hypervisor() 116 set_xen_guest_handle(op.u.set_pminfo.power.states, dst_cx_states); in push_cxx_to_hypervisor() 123 for (i = 1; i <= _pr->power.count; i++) { in push_cxx_to_hypervisor() [all …]
/linux-4.4.14/drivers/idle/
D	Kconfig	`12 menu "Memory power savings" 19 tristate "Intel chipset idle memory power saving driver" 22 Enable memory power savings when idle with certain Intel server 24 Intel 7300. The power savings depends on the type and quantity of`
/linux-4.4.14/tools/power/cpupower/utils/
D	cpufreq-set.c	`70 int power = 0, match_count = 0, i, cp, pad; in string_to_frequency() local 92 power = unit->power_of_ten; in string_to_frequency() 103 while (power > -1 && isdigit(str[cp+1])) in string_to_frequency() 104 cp++, power--; in string_to_frequency() 106 if (power >= -1) /* not enough => pad */ in string_to_frequency() 107 pad = power + 1; in string_to_frequency() 109 pad = 0, cp += power + 1; in string_to_frequency()`
/linux-4.4.14/Documentation/sound/alsa/soc/
D	dapm.txt	8 Linux devices to use the minimum amount of power within the audio 13 all power switching is done within the ASoC core. No code changes or 14 recompiling are required for user space applications. DAPM makes power 18 DAPM spans the whole machine. It covers power control within the entire 19 audio subsystem, this includes internal codec power blocks and machine 20 level power systems. 22 There are 4 power domains within DAPM 24 1. Codec bias domain - VREF, VMID (core codec and audio power) 26 can be set at stream time if power is not needed for sidetone, etc. 41 All DAPM power switching decisions are made automatically by consulting an audio [all …]
D	overview.txt	`20 * Drivers tended to power up the entire codec when playing (or 22 power on portable devices. There was also no support for saving 23 power via changing codec oversampling rates, bias currents, etc. 41 its minimum power state at all times. This includes powering up/down 42 internal power blocks depending on the internal codec audio routing and any 47 signals the codec when to change power states. 91 clocking.txt: ASoC clocking for best power performance.`
/linux-4.4.14/drivers/net/wireless/iwlegacy/
D	3945.c	1344 s8 power; in il3945_hw_reg_set_scan_power() local 1352 power = min(ch_info->scan_power, clip_pwrs[RATE_6M_IDX_TBL]); in il3945_hw_reg_set_scan_power() 1354 power = min(power, il->tx_power_user_lmt); in il3945_hw_reg_set_scan_power() 1355 scan_power_info->requested_power = power; in il3945_hw_reg_set_scan_power() 1363 ch_info->power_info[rate_idx].power_table_idx - (power - in il3945_hw_reg_set_scan_power() 1430 txpower.power[i].tpc = ch_info->power_info[i].tpc; in il3945_send_tx_power() 1431 txpower.power[i].rate = il3945_rates[rate_idx].plcp; in il3945_send_tx_power() 1435 txpower.power[i].tpc.tx_gain, in il3945_send_tx_power() 1436 txpower.power[i].tpc.dsp_atten, txpower.power[i].rate); in il3945_send_tx_power() 1441 txpower.power[i].tpc = ch_info->power_info[i].tpc; in il3945_send_tx_power() [all …]
/linux-4.4.14/Documentation/ABI/obsolete/
D	sysfs-bus-usb	`1 What: /sys/bus/usb/devices/.../power/level 7 power/level. This file holds a power-level setting for 20 write "0" to power/autosuspend. 30 Use the power/control file instead; it does exactly the`
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
D	mmc-pwrseq-simple.txt	`1 * The simple MMC power sequence provider 3 The purpose of the simple MMC power sequence provider is to supports a set of 12 at initialization and prior we start the power up procedure of the card. 13 They will be de-asserted right after the power has been provided to the`
D	mmc.txt	39 - cap-power-off-card: powering off the card is safe 42 - full-pwr-cycle: full power cycle of the card is supported 70 - keep-power-in-suspend: Preserves card power during a suspend/resume cycle 75 MMC power sequences: 78 System on chip designs may specify a specific MMC power sequence. To 79 successfully detect an (e)MMC/SD/SDIO card, that power sequence must be 83 - mmc-pwrseq: phandle to the MMC power sequence node. See "mmc-pwrseq-*" 84 for documentation of MMC power sequence bindings. 121 keep-power-in-suspend;
/linux-4.4.14/Documentation/trace/
D	events-power.txt	`2 Subsystem Trace Points: power 4 The power tracing system captures events related to power transitions 15 Cf. include/trace/events/power.h for the events definitions. 59 The power domain events are used for power domains transitions 63 The first parameter gives the power domain name (e.g. "mpu_pwrdm"). 64 The second parameter is the power domain target state.`
/linux-4.4.14/Documentation/devicetree/bindings/arm/rockchip/
D	pmu.txt	`1 Rockchip power-management-unit: 4 The pmu is used to turn off and on different power domains of the SoCs 5 This includes the power to the CPU cores.`
/linux-4.4.14/drivers/net/wireless/ath/carl9170/
D	mac.c	507 unsigned int power, chains; in carl9170_set_mac_tpc() local 516 power = ar->power_2G_ofdm[0] & 0x3f; in carl9170_set_mac_tpc() 519 power = ar->power_5G_leg[0] & 0x3f; in carl9170_set_mac_tpc() 525 power = min_t(unsigned int, power, ar->hw->conf.power_level * 2); in carl9170_set_mac_tpc() 529 0x3c1e \| power << 20 \| chains << 26); in carl9170_set_mac_tpc() 531 power << 5 \| chains << 11 \| in carl9170_set_mac_tpc() 532 power << 21 \| chains << 27); in carl9170_set_mac_tpc() 534 power << 5 \| chains << 11 \| in carl9170_set_mac_tpc() 535 power << 21 \| chains << 27); in carl9170_set_mac_tpc()
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/disp/
D	g84.c	`42 .dac.power = nv50_dac_power, 45 .sor.power = nv50_sor_power, 48 .pior.power = nv50_pior_power,`
D	gt200.c	`42 .dac.power = nv50_dac_power, 45 .sor.power = nv50_sor_power, 48 .pior.power = nv50_pior_power,`
D	g94.c	`43 .dac.power = nv50_dac_power, 46 .sor.power = nv50_sor_power, 49 .pior.power = nv50_pior_power,`
D	gt215.c	`43 .dac.power = nv50_dac_power, 46 .sor.power = nv50_sor_power, 50 .pior.power = nv50_pior_power,`
D	nv50.h	`90 int (power)(NV50_DISP_MTHD_V1); member 96 int (power)(NV50_DISP_MTHD_V1); member 104 int (*power)(NV50_DISP_MTHD_V1); member`
/linux-4.4.14/arch/arm/mach-pxa/
D	palm27x.c	52 void __init palm27x_mmc_init(int detect, int ro, int power, in palm27x_mmc_init() argument 57 palm27x_mci_platform_data.gpio_power = power; in palm27x_mmc_init() 144 void __init palm27x_lcd_init(int power, struct pxafb_mode_info *mode) in palm27x_lcd_init() argument 148 if (gpio_is_valid(power)) { in palm27x_lcd_init() 149 if (!gpio_request(power, "LCD power")) { in palm27x_lcd_init() 153 if (!gpio_direction_output(power, 1)) { in palm27x_lcd_init() 157 palm27x_lcd_power = power; in palm27x_lcd_init()
/linux-4.4.14/Documentation/devicetree/bindings/phy/
D	hix5hd2-phy.txt	`12 - hisilicon,power-reg: offset and bit number within peripheral-syscon, 13 register of controlling sata power supply. 21 hisilicon,power-reg = <0x8 10>;`
D	ti-phy.txt	`10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control 15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on 17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on 21 "power", "pcie_pcs" and "control_sma" for control-phy-pcie 22 "power" for all other types 44 - ctrl-module : phandle of the control module used by PHY driver to power on 80 - ctrl-module : phandle of the control module used by PHY driver to power on`
/linux-4.4.14/Documentation/devicetree/bindings/usb/
D	pxa-usb.txt	`16 - "marvell,power-sense-low" - power sense pin is low-active. 17 - "marvell,power-control-low" - power control pin is low-active.`
/linux-4.4.14/drivers/media/platform/s5p-tv/
D	sii9234_drv.c	`35 struct regulator *power; member 239 regulator_disable(ctx->power); in sii9234_runtime_suspend() 252 ret = regulator_enable(ctx->power); in sii9234_runtime_resume() 272 regulator_disable(ctx->power); in sii9234_runtime_resume() 333 ctx->power = devm_regulator_get(dev, "hdmi-en"); in sii9234_probe() 334 if (IS_ERR(ctx->power)) { in sii9234_probe() 336 return PTR_ERR(ctx->power); in sii9234_probe()`
/linux-4.4.14/Documentation/devicetree/bindings/media/
D	hix5hd2-ir.txt	`11 - hisilicon,power-syscon: phandle of syscon used to control power. 23 hisilicon,power-syscon = <&sysctrl>;`
D	samsung-s5c73m3.txt	`17 - vdd-int-supply : digital power supply (1.2V); 18 - vdda-supply : analog power supply (1.2V); 19 - vdd-reg-supply : regulator input power supply (2.8V); 20 - vddio-host-supply : host I/O power supply (1.8V to 2.8V); 21 - vddio-cis-supply : CIS I/O power supply (1.2V to 1.8V); 22 - vdd-af-supply : lens power supply (2.8V);`
D	s5p-mfc.txt	`31 - power-domains : power-domain property defined with a phandle 32 to respective power domain. 41 power-domains = <&pd_mfc>;`
/linux-4.4.14/drivers/net/ieee802154/
D	cc2520.c	`637 u8 power; in cc2520_set_tx_power() local 641 power = 0xF7; in cc2520_set_tx_power() 644 power = 0xF2; in cc2520_set_tx_power() 647 power = 0xAB; in cc2520_set_tx_power() 650 power = 0x13; in cc2520_set_tx_power() 653 power = 0x32; in cc2520_set_tx_power() 656 power = 0x81; in cc2520_set_tx_power() 659 power = 0x88; in cc2520_set_tx_power() 662 power = 0x2C; in cc2520_set_tx_power() 665 power = 0x03; in cc2520_set_tx_power() [all …]`
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
D	edp.txt	`11 - power-domains: Should be <&mmcc MDSS_GDSC>. 22 - lvl-vdd-supply: phandle to regulator device node which is used to supply power 24 - panel-en-gpios: GPIO pin to supply power to panel. 42 power-domains = <&mmcc MDSS_GDSC>;`
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
D	dpll.txt	`10 modes (locked, low power stop etc.) This binding has several 51 - ti,low-power-stop : DPLL supports low power stop mode, gating output 52 - ti,low-power-bypass : DPLL output matches rate of parent bypass clock 67 ti,low-power-stop; 68 ti,low-power-bypass;`
/linux-4.4.14/arch/arm/mach-s3c24xx/
D	sleep-s3c2410.S	`54 orr r8, r8, #S3C2410_MISCCR_SDSLEEP @ SDRAM power-down signals 55 orr r9, r9, #S3C2410_CLKCON_POWER @ power down command 66 streq r8, [r5] @ SDRAM power-down config`
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
D	img,tz1090-pdc-pinctrl.txt	`52 - low-power-enable: Flag, power-on-start weak pull-down for invalid power. 53 - low-power-disable: Flag, power-on-start weak pull-down disabled. 84 drive-strength, low-power-enable, and low-power-disable.`
/linux-4.4.14/drivers/media/pci/mantis/
D	mantis_dvb.c	43 int mantis_frontend_power(struct mantis_pci *mantis, enum mantis_power power) in mantis_frontend_power() argument 47 switch (power) { in mantis_frontend_power() 50 mantis_gpio_set_bits(mantis, config->power, POWER_ON); in mantis_frontend_power() 52 mantis_gpio_set_bits(mantis, config->power, POWER_ON); in mantis_frontend_power() 58 mantis_gpio_set_bits(mantis, config->power, POWER_OFF); in mantis_frontend_power() 63 dprintk(MANTIS_DEBUG, 1, "Unknown state <%02x>", power); in mantis_frontend_power()
/linux-4.4.14/net/mac802154/
D	trace.h	`126 TP_PROTO(struct ieee802154_local *local, s32 power), 127 TP_ARGS(local, power), 130 __field(s32, power) 134 __entry->power = power; 137 __entry->power)`
/linux-4.4.14/drivers/macintosh/
D	windfarm_pm91.c	220 s32 new_setpoint, temp, power; in wf_smu_cpu_fans_tick() local 238 rc = wf_sensor_get(sensor_cpu_power, &power); in wf_smu_cpu_fans_tick() 247 FIX32TOPRINT(temp), FIX32TOPRINT(power)); in wf_smu_cpu_fans_tick() 256 new_setpoint = wf_cpu_pid_run(&st->pid, power, temp); in wf_smu_cpu_fans_tick() 410 s32 new_setpoint, power; in wf_smu_slots_fans_tick() local 420 rc = wf_sensor_get(sensor_slots_power, &power); in wf_smu_slots_fans_tick() 429 FIX32TOPRINT(power)); in wf_smu_slots_fans_tick() 432 if (power > (st->pid.param.itarget + 0x50000)) in wf_smu_slots_fans_tick() 436 new_setpoint = wf_pid_run(&st->pid, power); in wf_smu_slots_fans_tick()
/linux-4.4.14/drivers/gpu/drm/shmobile/
D	shmob_drm_backlight.c	`27 if (bdev->props.power != FB_BLANK_UNBLANK \|\| in shmob_drm_backlight_update() 54 scon->backlight->props.power = mode == DRM_MODE_DPMS_ON in shmob_drm_backlight_dpms() 80 backlight->props.power = FB_BLANK_POWERDOWN; in shmob_drm_backlight_init()`
/linux-4.4.14/drivers/phy/
D	phy-omap-control.c	`88 val = readl(control_phy->power); in omap_control_phy_power() 143 writel(val, control_phy->power); in omap_control_phy_power() 307 control_phy->power = devm_ioremap_resource(&pdev->dev, res); in omap_control_phy_probe() 308 if (IS_ERR(control_phy->power)) { in omap_control_phy_probe() 310 return PTR_ERR(control_phy->power); in omap_control_phy_probe()`
/linux-4.4.14/Documentation/devicetree/bindings/leds/
D	leds-netxbig.txt	`35 blue-power { 36 label = "netxbig:blue:power"; 45 red-power { 46 label = "netxbig:red:power";`
/linux-4.4.14/drivers/media/platform/s5p-mfc/
D	s5p_mfc_pm.c	`67 atomic_set(&pm->power, 0); in s5p_mfc_init_pm() 124 atomic_set(&pm->power, 1); in s5p_mfc_power_on() 134 atomic_set(&pm->power, 0); in s5p_mfc_power_off()`
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
D	rtc-omap.txt	`17 - system-power-controller: whether the rtc is controlling the system power 30 system-power-controller;`
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
D	renesas,intc-irqpin.txt	`34 - power-domains: Must contain a reference to the power domain. This property is 35 mandatory if the irqpin controller instance is part of a controllable power 61 power-domains = <&pd_a4s>;`

12 3 4 5 6 7 8

Project(s)

Full Search
Definition
Symbol
File Path
History
Type