linux-toradex.git/drivers/power/power_supply_core.c, branch v3.7.6

Thermal: Remove tc1/tc2 in generic thermal layer.

2012-09-24T06:44:36+00:00

Remove tc1/tc2 in generic thermal layer.
.get_trend() callback starts to take effect from this patch.

Signed-off-by: Zhang Rui 
Reviewed-by: Rafael J. Wysocki 
Reviewed-by: Valentin, Eduardo

Merge with upstream to accommodate with thermal changes

2012-07-31T12:16:47+00:00

This merge is performed to take commit c56f5c0342dfee11a1 ("Thermal: Make
Thermal trip points writeable") out of Linus' tree and then fixup power
supply class. This is needed since thermal stuff added a new argument:

  CC      drivers/power/power_supply_core.o
drivers/power/power_supply_core.c: In function ‘psy_register_thermal’:
drivers/power/power_supply_core.c:204:6: warning: passing argument 3 of ‘thermal_zone_device_register’ makes integer from pointer without a cast [enabled by default]
include/linux/thermal.h:154:29: note: expected ‘int’ but argument is of type ‘struct power_supply *’
drivers/power/power_supply_core.c:204:6: error: too few arguments to function ‘thermal_zone_device_register’
include/linux/thermal.h:154:29: note: declared here
make[1]: *** [drivers/power/power_supply_core.o] Error 1
make: *** [drivers/power/] Error 2

Signed-off-by: Anton Vorontsov

power_supply: Register battery as a thermal zone

2012-06-18T04:25:39+00:00

Battery and charger contribute to Thermals in most of the embedded
devices. So, it makes sense to identify them as Thermal zones in a
particular platform.

This patch registers a thermal zone if the power supply is reporting
a temperature property. The thermal zone will be used by platform's
thermal management solution.

Signed-off-by: Jenny TC 
Signed-off-by: Anton Vorontsov

power_supply: Drop usage of nowarn variant of sysfs_create_link()

2012-01-07T11:24:51+00:00

The function is not exported to modules, plus we do want to catch anyone
who tries to create complex hierarchy (in that case we'd need to change
'powers' symlink to a directory, probably under a different name to not
break ABI).

This patch fixes the following build error:

 ERROR: "sysfs_create_link_nowarn" [drivers/power/power_supply.ko] undefined!

Reported-by: Stephen Rothwell 
Signed-off-by: Anton Vorontsov

power_supply: Assume mains power by default

2012-01-06T01:50:32+00:00

If no power class device is found in power_supply_is_system_supplied(),
the function currently returns 0, which basically means that the system
is supposed to be running on battery. In practice, mobile devices tend
to always implement at least one power class device and more often two
(battery and AC adapter). Systems with no registered power class
devices are more likely to be desktop systems, where the system is
always powered by mains.

So, change the default return value of
power_supply_is_system_supplied() from 0 (running on battery) to 1
(running on mains.)

Signed-off-by: Jean Delvare 
Cc: David Woodhouse 
Cc: Matthew Garrett 
Cc: Alex Deucher 
Signed-off-by: Anton Vorontsov

power_supply: allow a power supply to explicitly point to powered device

2011-12-09T17:52:07+00:00

If a power supply has a scope of "Device", then allow the power supply
to indicate what device it actually powers. This is represented in the
power supply's sysfs directory as a symlink named "powers", which points to
the sysfs directory of the powered device.

If the device has children, then the sub-devices are also powered by
the same power supply.

Signed-off-by: Jeremy Fitzhardinge 
Cc: Richard Hughes

power_supply: Initialize changed_work before calling device_add

2011-02-22T10:01:42+00:00

Calling device_add causes an inital uevent for that device to be generated.
The power_supply uevent function calls the drivers get_property function,
which might causes the driver to update its state, which again might
causes the driver to call power_supply_changed(). Since the power_supplys
changed_work has not been initialized at this point the behavior is
undefined and can result in an OOPS.

This patch fixes the issue by initializing the power_supplys changed_work
prior to adding the power_supplys device to the device tree.

Reported-by: Grazvydas Ignotas 
Signed-off-by: Lars-Peter Clausen 
Tested-by: Grazvydas Ignotas

power_supply: Don't use flush_scheduled_work()

2010-12-21T23:39:56+00:00

flush_scheduled_work() is deprecated and scheduled to be removed.

In battery drivers, the work can be canceled on probe failure and
removal and should be flushed on suspend.  Replace
flush_scheduled_work() usages with direct cancels and flushes.

Signed-off-by: Tejun Heo 
Signed-off-by: Anton Vorontsov

power_supply: Fix use after free and memory leak

2010-12-21T23:39:55+00:00

device_unregister() might free its argument.  This leads to freed
memory use in kfree().  Also use put_device() instead of kfree()
as dev may be already used in another layer after call to device_add().

Signed-off-by: Vasiliy Kulikov 
Signed-off-by: Anton Vorontsov

power_supply: Use attribute groups

2010-05-19T08:14:28+00:00

This fixes a race between power supply device and initial
attributes creation, plus makes it possible to implement
writable properties.

[Daniel Mack - removed superflous return statement
 and dropped .mode attribute from POWER_SUPPLY_ATTR]

Suggested-by: Greg KH 
Suggested-by: Kay Sievers 
Signed-off-by: Anton Vorontsov 
Tested-by: Daniel Mack