diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-15 00:56:23 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-15 00:56:23 -0400 |
commit | 50fa86172bec2769979b5eb0cd1a244391ae4bb0 (patch) | |
tree | 5fd4949b031e1362af8b226d6372da2604de13ff /Documentation/power | |
parent | 6b0490816671b2f4126a99998c9bf3c8c0472de2 (diff) | |
parent | 7881c64716f3a7d60b325ed0ad4d15f49b474a43 (diff) |
Merge tag 'for-v3.18' of git://git.infradead.org/battery-2.6
Pull power supply and reset updates from Sebastian Reichel:
- Initial support for the following chips
* max77836 (charger)
* max14577 (charger)
* bq27742 (battery gauge)
* ltc2952 (poweroff)
* stih416 (restart)
* syscon-reboot (restart)
* gpio-restart (restart)
- cleanup of power supply core
- misc fixes in power supply and reset drivers
* tag 'for-v3.18' of git://git.infradead.org/battery-2.6: (48 commits)
power: ab8500_fg: Fix build warning
Documentation: charger: max14577: Update the date of introducing ABI
power: reset: corrections for simple syscon reboot driver
Documentation: power: reset: Add documentation for generic SYSCON reboot driver
power: reset: Add generic SYSCON register mapped reset
bq27x00_battery: Fix flag reading for bq27742
power: reset: use restart_notifier mechanism for msm-poweroff
power: Add simple gpio-restart driver
power: reset: st: Provide DT bindings for ST's Power Reset driver
power: reset: Add restart functionality for STiH41x platforms
power: charger-manager: Fix NULL pointer exception with missing cm-fuel-gauge
power: max14577: Fix circular config SYSFS dependency
power: gpio-charger: do not use gpio value directly
power: max8925: Use of_get_child_by_name
power: max8925: Fix NULL ptr dereference on memory allocation failure
bq27x00_battery: Add support to bq27742
Documentation: charger: max14577: Document exported sysfs entry
devicetree: mfd: max14577: Add device tree bindings document
power: max17040: Add ID for MAX77836 Fuel Gauge block
charger: max14577: Configure battery-dependent settings from DTS and sysfs
...
Conflicts:
drivers/power/reset/Kconfig
drivers/power/reset/Makefile
Diffstat (limited to 'Documentation/power')
-rw-r--r-- | Documentation/power/charger-manager.txt | 2 | ||||
-rw-r--r-- | Documentation/power/power_supply_class.txt | 6 |
2 files changed, 7 insertions, 1 deletions
diff --git a/Documentation/power/charger-manager.txt b/Documentation/power/charger-manager.txt index b4f7f4b23f64..9ff1105e58d6 100644 --- a/Documentation/power/charger-manager.txt +++ b/Documentation/power/charger-manager.txt | |||
@@ -29,7 +29,7 @@ Charger Manager supports the following: | |||
29 | While the battery is being charged and the system is in suspend-to-RAM, | 29 | While the battery is being charged and the system is in suspend-to-RAM, |
30 | we may need to monitor the battery health by looking at the ambient or | 30 | we may need to monitor the battery health by looking at the ambient or |
31 | battery temperature. We can accomplish this by waking up the system | 31 | battery temperature. We can accomplish this by waking up the system |
32 | periodically. However, such a method wakes up devices unncessary for | 32 | periodically. However, such a method wakes up devices unnecessarily for |
33 | monitoring the battery health and tasks, and user processes that are | 33 | monitoring the battery health and tasks, and user processes that are |
34 | supposed to be kept suspended. That, in turn, incurs unnecessary power | 34 | supposed to be kept suspended. That, in turn, incurs unnecessary power |
35 | consumption and slow down charging process. Or even, such peak power | 35 | consumption and slow down charging process. Or even, such peak power |
diff --git a/Documentation/power/power_supply_class.txt b/Documentation/power/power_supply_class.txt index 48cff881cb8a..82dacc06e355 100644 --- a/Documentation/power/power_supply_class.txt +++ b/Documentation/power/power_supply_class.txt | |||
@@ -101,6 +101,10 @@ VOLTAGE_MAX, VOLTAGE_MIN - same as _DESIGN voltage values except that | |||
101 | these ones should be used if hardware could only guess (measure and | 101 | these ones should be used if hardware could only guess (measure and |
102 | retain) the thresholds of a given power supply. | 102 | retain) the thresholds of a given power supply. |
103 | 103 | ||
104 | VOLTAGE_BOOT - Reports the voltage measured during boot | ||
105 | |||
106 | CURRENT_BOOT - Reports the current measured during boot | ||
107 | |||
104 | CHARGE_FULL_DESIGN, CHARGE_EMPTY_DESIGN - design charge values, when | 108 | CHARGE_FULL_DESIGN, CHARGE_EMPTY_DESIGN - design charge values, when |
105 | battery considered full/empty. | 109 | battery considered full/empty. |
106 | 110 | ||
@@ -123,6 +127,8 @@ the current drawn from a charging source. | |||
123 | CHARGE_TERM_CURRENT - Charge termination current used to detect the end of charge | 127 | CHARGE_TERM_CURRENT - Charge termination current used to detect the end of charge |
124 | condition. | 128 | condition. |
125 | 129 | ||
130 | CALIBRATE - battery or coulomb counter calibration status | ||
131 | |||
126 | CONSTANT_CHARGE_VOLTAGE - constant charge voltage programmed by charger. | 132 | CONSTANT_CHARGE_VOLTAGE - constant charge voltage programmed by charger. |
127 | CONSTANT_CHARGE_VOLTAGE_MAX - maximum charge voltage supported by the | 133 | CONSTANT_CHARGE_VOLTAGE_MAX - maximum charge voltage supported by the |
128 | power supply object. | 134 | power supply object. |