summaryrefslogtreecommitdiff
path: root/drivers/power/supply/collie_battery.c
diff options
context:
space:
mode:
authorGuenter Roeck <linux@roeck-us.net>2016-09-09 05:10:00 +0300
committerSebastian Reichel <sre@kernel.org>2016-09-19 22:02:17 +0300
commit17c6d3979e5bbff1de36a4e89015fa09ac495d27 (patch)
treeef0dd71aebc4183c4c7c00baadc7fa1ef8cc9e7d /drivers/power/supply/collie_battery.c
parent0610735928ee47870e083d5901caa371089216f1 (diff)
downloadlinux-17c6d3979e5bbff1de36a4e89015fa09ac495d27.tar.xz
sbs-battery: make writes to ManufacturerAccess optional
According to the Smart Battery Data Specification, the use of ManufacturerAcess (register 0x0) is implementation-defined. It appears that some batteries use writes to this register in order to implement certain functionality, but others may simply NAK all writes to it. As a result, write failures to ManufacturerAccess should not be used as an indicator of battery presence, nor as a failure to enter sleep mode. The failed write access was seen with SANYO AP13J3K. Cc: Brian Norris <briannorris@chromium.org> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Sebastian Reichel <sre@kernel.org>
Diffstat (limited to 'drivers/power/supply/collie_battery.c')
0 files changed, 0 insertions, 0 deletions