Skip to content

bq27xxx_battery partial series

Liam Breck linux-devicetree linux-pm 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest7 of 11 patches 3 repliesIn review

7 of 11 patches are in this archive. The cover letter announces 11.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
5/11power: bq27xxx_battery: Add chip data memory read/write supportdrivers/power/supply/bq27xxx_battery.c include/linux/power/bq27xxx_battery.h+252 -01 reply
6/11power: bq27xxx_battery: Add power_supply_battery_info supportdrivers/power/supply/bq27xxx_battery.c include/linux/power/bq27xxx_battery.h+188 -10 replies
7/11power: bq27xxx_battery: Enable data memory update for certain chipsdrivers/power/supply/bq27xxx_battery.c drivers/power/supply/bq27xxx_battery_i2c.c include/linux/power/bq27xxx_battery.h+105 -120 replies
8/11devicetree: power: bq27xxx: Add monitored-battery documentationDocumentation/devicetree/bindings/power/supply/bq27xxx.txt+24 -71 reply
9/11power: bq27xxx_battery: Flag identical register maps when in debug modedrivers/power/supply/bq27xxx_battery.c+21 -00 replies
10/11power: bq27xxx_battery: Remove duplicate register arraysdrivers/power/supply/bq27xxx_battery.c include/linux/power/bq27xxx_battery.h+10 -1360 replies
11/11power: bq27xxx_battery: Disable flash/NVM data memory updatedrivers/power/supply/bq27xxx_battery.c include/linux/power/bq27xxx_battery.h+7 -70 replies

Reviews trailers per patch

1 of 7 patches has a Reviewed-by or Acked-by.

PatchRob Herring
5/11
6/11
7/11
8/11A-b
9/11
10/11
11/11

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH v12.6 0/11] bq27xxx_battery partial series

Latest changes:

New patch to disable updates to flash/NVM. The purpose of this series has always been to update NVM or RAM via DT. It was Sebastian's idea to site the properties in a fixed/simple-battery node representing the battery to the fuel gauge (i.e. your characterization that I "misused" the battery node is mistaken). I relent only because I've switched from a NVM to RAM gauge. I expect others will succeed in reverting this. Also, I have no need for a knob which lets userspace trigger NVM update, so I leave that to others.

Add module param use_monitored_battery to the power_supply_battery_info patch; it is dropped in the above patch. Allowing users to ignore the DT properties is the correct solution IMO.

Add Copyright notice

unseal() returns error on key==0

Skip reset on non-cfgupdate chips if not updated

Emit warning if no dm_regs table

Map orig ID to chip ID via bq27xxx_chips[]

Drop "prototypes" in enum comments

Rename dupes detector bq27xxx_battery_dbg_regs_dupes()

^.^ ^.^ - We can has test?