linux-toradex.git/include/linux/power, branch v4.14-rc7

power: supply: bq24190_charger: Export 5V boost converter as regulator

2017-08-30T15:31:51+00:00

Register the 5V boost converter as a regulator named "usb_otg_vbus".

This commit also adds support for bq24190_platform_data, through which
non device-tree platforms can pass the regulator_init_data (containing
mappings for the consumer amongst other things).

Signed-off-by: Hans de Goede 
Acked-by: Tony Lindgren 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: Enable data memory update for certain chips

2017-08-29T10:44:27+00:00

Support data memory update on BQ27425. Parameters from TI datasheets are also
provided for BQ27500, 545, 421, 441, 621; however these are commented out,
as they are not tested.

Add BQ27XXX_O_CFGUP & _O_RAM for use in bq27xxx_chip_data[n].opts
and by data memory update functions.

Signed-off-by: Liam Breck 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: Add chip IDs for previously shadowed chips

2017-08-29T10:37:35+00:00

For the existing features, these chips act like others already ID'd,
so they had false but functional IDs. We will be adding features
which require correct IDs, so the following IDs are added:
BQ2752X, 531, 542, 546, 742, 425, 441, 621

Chip-specific features are now tracked by BQ27XXX_O_* flags in di->opts.

No functional changes to the driver.

Signed-off-by: Liam Breck 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: move platform driver code into bq27xxx_battery_hdq.c

2017-07-25T13:31:21+00:00

When the BQ27xxx driver was originally written the w1 subsystem only
allowed device drivers for w1 attached devices to live in the w1
subsystem. Kernel driver subsystems expect that the driver for a device
live in the directory of the subsystem for which it implements
functionality, not in the directory of the bus that it is attached. To
work around this, the BQ27xxx driver was implemented as a platform device
driver and the interface driver would instantiate this device from within
the w1 directory, then pass a w1 read callback as platform data.

As we can now have the w1 interface driver in the power/supply directory
(like we do already with the i2c interface driver) we can remove this
middle-layer platform driver.

Signed-off-by: Andrew F. Davis 
Acked-by: Pali Rohár 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: Add power_supply_battery_info support

2017-06-08T15:57:38+00:00

Previously there was no way to configure these chips in the event that the
defaults didn't match the battery in question.

For chips with RAM data memory (and also those with flash/NVM data memory
if CONFIG_BATTERY_BQ27XXX_DT_UPDATES_NVM is defined and the user has not
set module param dt_monitored_battery_updates_nvm=0) we now call
power_supply_get_battery_info(), check its values, and write battery
properties to chip data memory if there is a dm_regs table for the chip.

Signed-off-by: Matt Ranostay 
Signed-off-by: Liam Breck 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: Add chip data memory read/write support

2017-06-08T15:57:34+00:00

Add these to enable read/write of chip data memory RAM/NVM/flash:
  bq27xxx_battery_seal()
  bq27xxx_battery_unseal()
  bq27xxx_battery_set_cfgupdate()
  bq27xxx_battery_soft_reset()
  bq27xxx_battery_read_dm_block()
  bq27xxx_battery_write_dm_block()
  bq27xxx_battery_checksum_dm_block()

Signed-off-by: Matt Ranostay 
Signed-off-by: Liam Breck 
Signed-off-by: Sebastian Reichel

power: supply: bq27xxx: Add bulk transfer bus methods

2017-06-08T14:29:29+00:00

Declare bus.write/read_bulk/write_bulk().
Add I2C write/read_bulk/write_bulk() to implement the above.
Add bq27xxx_write/read_block/write_block() helpers to call the above.

Signed-off-by: Matt Ranostay 
Signed-off-by: Liam Breck 
Acked-by: "Andrew F. Davis" 
Signed-off-by: Sebastian Reichel

power: supply: max17042_battery: Add support for the STATUS property

2017-05-01T10:37:29+00:00

Userspace prefers the driver having a status property over having to guess
itself. Specifically this will properly make the GNOME3 UI (and likely
others) properly show discharging / charging / full status, instead
of always showing discharging as status.

Note that in the case there is no charger driver supplying the max17042,
then a status of unknown will get returned. At least upower treats
this the same as not having a status attribute, so in this case nothing
changes from a userspace pov.

Signed-off-by: Hans de Goede 
Reviewed-by: Krzysztof Kozlowski 
Signed-off-by: Sebastian Reichel

power: supply: max17042_battery: Add default platform_data fallback data

2017-05-01T10:37:25+00:00

Some x86 machines use a max17047 fuel-gauge and x86 might be missing
platform_data if not provided by SFI.

This commit adds default platform_data as fallback option so that the
driver can work on boards where no platform_data is provided.

Since not all boards have a thermistor hooked up, set temp_min to 0 and
change the health checks from temp <= temp_min to temp < temp_min to
not trigger on such boards (where temp reads 0).

Signed-off-by: Hans de Goede 
Reviewed-by: Krzysztof Kozlowski 
Signed-off-by: Sebastian Reichel

power: supply: bq24190_charger: Use i2c-core irq-mapping code

2017-04-13T23:41:34+00:00

The i2c-core already maps of irqs before calling the driver's probe
function and there are no in tree users of
bq24190_platform_data->gpio_int.

Remove the redundant custom irq-mapping code and just use client->irq.

Cc: Liam Breck 
Cc: Tony Lindgren 
Signed-off-by: Hans de Goede 
Reviewed-by: Andy Shevchenko 
Acked-by: Tony Lindgren 
Signed-off-by: Sebastian Reichel