aboutsummaryrefslogtreecommitdiff
path: root/drivers/power
AgeCommit message (Collapse)Author
2009-03-03fix-hdq-sample-period-calc.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2009-03-03Subject: pcf50633_charger_detection_fix.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=f4fd6631973dbc67a5f4708014e81ca6e610ca05 pcf50633_charger_detection_fix.patch Fix PCF50633 charger detection code. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-02-26fix-hdq-increase-break-timing.patchAndy Green
This removes the unstable operation by increasing break timing from 170us to 230us, the datasheet minimum was 190us. Signed-off-by: Andy Green <andy@openmoko.com>
2009-02-26Subject: fix_gta03_fiq_stuff.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=c94ea3d685fa6e9b24d62adb11a7ad6087b9edf5 fix_gta03_fiq_stuff.patch Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-02-22gta02_use_new_fiq_and_hdq_stuff.patchBalaji Rao
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-02-22introduce_generic_hdq_gpio_bitbang_driver.patchBalaji Rao
Introduce a new generic HDQ gpio based bitbang driver Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-02-08power: pcf50633 wall charger current limit fixRask Ingemann Lambertsen
Hi. The recent patch to fix a USB current limit violation when turning the device off triggered a bug in setting the battery charge current limit. We now get a charge current limit of 0 mA on the GTA02 when plugging in the wall charger (just as when setting 1000 mA in /sys/class/[...]/chg_curlim). This patch fixes it (and a comment typo). Tested on a GTA02 with a wall charger. Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
2009-02-06MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-MERGE-via-mokopatc ↵merge
hes-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505 pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505 / 1c405b6ccee468298e7ccbfd9a3a3f4d123207b0 ... parent commitmessage: From: merge <null@invalid> MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414 stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414 / 71be0a45396066b1f8f27f8f4f87937247a129e1 ... parent commitmessage: From: merge <null@invalid> MERGE-via-mokopatches-tracking-hist-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011 mokopatches-tracking-hist top was MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011 / 1be1b01373f572a02c6f1f99863c8c11ed2f9f5b ... parent commitmessage: From: merge <null@invalid> MERGE-via-master-MERGE-via-master-hist-1232625318 master top was MERGE-via-master-hist-1232625318 / dd4b117123ae66451695810017eb72fbdfc05df5 ... parent commitmessage: From: merge <null@invalid> MERGE-master-patchset-edits
2009-02-05fix-pcf50633-set-charging-limit-with-usb-limit.patchAndy Green
Cedric noticed that when he turned his GTA02 OFF while hooked to a "dumb" USB charger that should only be asked for 100mA, suddenly much more current was demanded. When PMU enters PMU standmy when we go OFF, its USB current limit is reset to the variant default of 500mA. Since we previously had the charging current limit fixed at 1A, it meant we immediately charge at 500mA. This patch makes the charging limit follow the USB current limit, so that even when we go off, no more than the last authorized amount of current will be taken, even if the USB current limit is later broken by the variant default. Reported-by: Cedric Berger <cedric.berger74@gmail.com> Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-29 pcf50633_charging_current_control.patchBalaji Rao
Introduces battery charging current control. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-01-28Subject: pcf50633_introduce_charging_restart_interval.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=1bb6adaa6a59f52d616b5260cb776eafd40ef05e pcf50633_introduce_charging_restart_interval.patch Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-01-28Subject: pcf50633_remove_set_charger_status.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=94808ce02deeb78bb3728db416fd4b7544b6d232 pcf50633_remove_set_charger_status.patch
2009-01-28Subject: pcf50606_rebase_changes,patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=938eddf17625cce0307f7612a3ea2560384e2384 pcf50606_rebase_changes,patch This patch brings into andy-tracking all changes related to pcf50606 from old balaji-tracking.
2009-01-28From: Sean McNeil <sean@mcneil.com>Andy Green
fix-ac-redefinition.patch
2009-01-27fix-pcf50633-from-balaji-tree.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-27fix-kconfig-stray-endif.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-22MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-MERGE-via-mokopatc ↵merge
hes-tracking-fix-stray-endmenu-patch-1232632040-1232632141 pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040-1232632141 / fdf777a63bcb59e0dfd78bfe2c6242e01f6d4eb9 ... parent commitmessage: From: merge <null@invalid> MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 stable-tracking-hist top was MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 / 90463bfd2d5a3c8b52f6e6d71024a00e052b0ced ... parent commitmessage: From: merge <null@invalid> MERGE-via-mokopatches-tracking-hist-fix-stray-endmenu-patch mokopatches-tracking-hist top was fix-stray-endmenu-patch / 3630e0be570de8057e7f8d2fe501ed353cdf34e6 ... parent commitmessage: From: Andy Green <andy@openmoko.com> fix-stray-endmenu.patch Signed-off-by: Andy Green <andy@openmoko.com>
2008-12-29Move charger initialization from core to mbc driver.Balaji Rao
When irq_handler is called from core, the irqs might not have been yet registered - which means, the initial charger state was not being set properly. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2008-12-29Kill automatic charging restart to retain manual control.Balaji Rao
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2008-12-29Manually restart charger periodicallyBalaji Rao
This avoids excessive discharges seen in case of Li-ion batteries even when charger is connected. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2008-12-29Start charging when the usb current limit is changed.Balaji Rao
This makes sure that charging status remains correct when currrent limit is altered from userspace. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2008-12-08MERGE-andy-tracking-patchset-edits-revert-power-patchesmerge
Whoops this is just reverting a couple of patches that were not ready to be committed yet.
2008-12-08MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-fix-s3c2410_ts-fif ↵merge
o-allocation-1228776491 pending-tracking-hist top was MERGE-via-stable-tracking-fix-s3c2410_ts-fifo-allocation-1228776491 / a85a8a282939b4f6800081f67e1d568e0b97bd7a ... parent commitmessage: From: merge <null@invalid> MERGE-via-stable-tracking-hist-fix-s3c2410_ts-fifo-allocation stable-tracking-hist top was fix-s3c2410_ts-fifo-allocation / 56a57ba0d4c1d60869250d5f89fae61544f01012 ... parent commitmessage: From: Nelson Castillo <nelsoneci@gmail.com> Fix s3c2410_ts FIFO allocation When I added the FIFO improving the interrupts handlers I introduced a bug. The FIFO is allocated after the interrupts are requested. This makes the kernel crash if the touchscreen generates activity before the allocation takes place. This patch fixes the bug. I reproduced it and tested the fix in a GTA02. - Fix bug - Fix a typo Reported-by: Andy Green <andy@openmoko.com> Signed-off-by: Nelson Castillo <nelsoneci@gmail.com>
2008-12-02PATCH-add-ac-charger-power_supply.emlSean McNeil
This adds an appropriate ac power_supply class and shows usb only when at the appropriate current limit. Signed-off-by: Sean McNeil <sean@mcneil.com>
2008-11-26MERGE-via-balaji-tracking-hist-MERGE-via-stable-tracking-hist-MERGE-via-moko ↵merging other branches
patches-tracking-via-master-s3c-hsmmc-clean balaji-tracking-hist top was efb2d57c0e0ed62324d79d6c5793fe797c157266
2008-11-21fix-merge-add-new-file.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-21MERGE-via-balaji-tracking-balaji-updatesAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-20pcf50633_mdc_related_changes.patchBalaji Rao
Changes related to pcf50633_mfd.patch
2008-11-19fix-hdq-fiq-interface.patchSean McNeil
Try to make sure about no compiler malarky by volatile. Change hdq busy detect. Change error handling path in hdq interface to fiq. Signed-off-by: Sean McNeil <sean@mcneil.com>
2008-11-19fix-hdq-child-attach-callback.patchAndy Green
Along the same lines as FIQ, HDQ can have children in device tree terms too. Allow the same kind of callback in machine-specific code Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19Move asm/arch/fiq_ipc_gta02.h to mach/fiq_ipc_gta02.hJonas Bonn
Signed-off-by: Jonas Bonn <jonas.bonn@gmail.com>
2008-11-19Move asm/arch/gta02.h to mach/gta02.hJonas Bonn
Signed-off-by: Jonas Bonn <jonas.bonn@gmail.com>
2008-11-19fix-stable-tracking-build-without-symlink.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19add-powersupply-ac-usb-automonitor.patchSean McNeil
Adds AC and USB powersupply objects, and a workqueue to automonitor changes in battery state and fire change events on any change to selected registers. Signed-off-by: Sean McNeil <sean@mcneil.com>
2008-11-19tracking-2.6.27-rc9-hdq-ordering.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19tracking-2.6.27-rc2-fix-fiq.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19tracking-2.6.27-rc2-include-path-changes.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-no-discharging.patchAndy Green
We failed to report status of "discharging", instead reporting "not charging" even if we knew that the charger was not present. This patch corrects it and reports "discharging" when charger is absent. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-pcf50633-usbrem-charging-led.patchAndy Green
If the charger was removed, we fell through back to old hdq-driven code with normally wrong but slightly random results for charging LED behaviour in that circumstance This patch makes us use the tracked charger status callbacks alone if they are defined in the platform data. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-bq27000-charger-state-tracking.patchAndy Green
Charger trigger stuff goes and asks for POWER_SUPPLY_PROP_STATUS to figure out what the charger state is. But until now, we only reported there what we found out from HDQ, and the HDQ registers are not updated very often in the coulomb counter, it can be 4 or more second lag before it tells us about what it experiences. When we react to USB insertion and only after 500ms debounce tell power_supply stuff that something changed, it most times will see old pre-USB-insertion state from bq27000 over HDQ at that time and will report it ain't charging, buggering up the LED trigger tracking. This patch maintains distance between bq27000 and pcf50633 by having platform callbacks in bq27000 that it can use to ask about definitive charger "online" presence and "activity", whether the charger says it is charging. If these callbacks are implemented (and we implement them in this patch up in mach_gta02.c) then this information is used in preference to what is found from HDQ. Result is if you set the LED trigger like this: echo bat-charging > /sys/devices/platform/gta02-led.0/leds/gta02-aux:red/trigger then it lights up properly on USB insertion now, goes away on removal properly, as as far as I saw, when charging stops too. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19From 5718bde77ed1a75e0fd2cdf5e099e66121d10c0a Mon Sep 17 00:00:00 2001Holger Freyther
Subject: [PATCH] [battery] Make the bq27000 send an uevent when the charging state possible changed Remove the todo entries from the pcf50633, make the mach-gta02 call the bq27000 driver from the pmu callback.
2008-11-19From ae3f72fc608fcd0a98a980a335ac4dc7ad95b221 Mon Sep 17 00:00:00 2001Holger Freyther
Subject: [PATCH] [bq27000] Make the checkpatch.pl happy
2008-11-19fix-remove-unused-model-name-bq27000.patchAndy Green
Model name isn't in the bq27000 register set, remove the claim that we can deliver it Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19OpenMoko => OpenmokoHolger Freyther
Signed-Off-By: Holger Freyther <zecke@openmoko.org>
2008-11-19introduce-bq27000-battery-driver.patchAndy Green
This is a driver for the bq27000 found in the Highcell A5 battery, and the platform device stuff for it for GTA02. It is a Power Supply Class battery device. The driver doesn't contain an HDQ engine but accepts pointers from the platform data to the HDQ action routines; our platform data plugs it into the FIQ HDQ engine stuff. The Power Supply class exposes the battery down /sys so you can find out battery status by doing the equivalent of this bash command for i in capacity charge_full current_now present status technology temp time_to_empty_now time_to_full_now type voltage_now ; do echo -n "$i " ; cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/$i ; done Here is the kind of result you get from a battery discharging capacity 0 charge_full 1215585 current_now 183375 present 1 status Discharging technology Li-ion temp 276 time_to_empty_now 0 time_to_full_now 3932100 type Battery voltage_now 2761000 Note that temp is in 1/10 degrees C, other values are in uV, uA, uW. The time_to_* reported are bogus, but that is what the battery actually reports. We can make more mappings to entries in power_supply class but this is enough to get started with. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19introduce-fiq-hdq.patchAndy Green
This adds a platform driver and device which performs HDQ battery protocol using a single GPIO pin which is set through platform data. HDQ has some hard latency requirements which can't be met if interrupts are enabled, so normally using a GPIO for this will require blocking out all other interrupts and processes for several milliseconds per register being read or written. This HDQ protocol engine is a FSM implemented inside the the FIQ ISR and regulated by timer interrupts happening at 20us intervals. The path through the FSM on any "clock" is very short and should be over with in ~ 1us. Because FIQ has guaranteed latencies of <1us, it means we can service the HDQ protocol without blocking interrupts or any other process other than the caller that is waiting for the result. It's pretty cool performance from 1 GPIO ;-) Due to it being hard to do locking from the FIQ ISR the code simply sleeps 10ms or whatever the scheduler gives it and checks if the transfer took place yet. This platform driver doesn't have any knowledge about the device it is talking to, it just knows it is a HDQ device. It exports three functions for read, write and confirming HDQ is initialized. It also exports two /sys nodes that are usable by humans, one dumps the whole 127 register HDQ register space # cat /sys/devices/platform/gta02-hdq.0/hdq/dump 00 44 55 00 00 00 ba 04 a2 0d 50 00 00 00 00 00 00 00 9a 1a 00 00 ff ff ff ff 29 00 00 00 80 2b 00 00 00 00 00 00 ff ff 00 00 00 00 00 32 af 06 a0 d8 37 4e 00 00 00 00 00 00 00 34 2e 03 b4 e7 00 00 06 00 41 00 4c 02 00 00 00 00 00 00 00 00 83 02 00 00 94 09 59 b9 a5 0d 7f 21 00 00 7a ff df ff 62 ff a7 04 2e 05 00 00 00 01 00 07 00 00 2a 78 36 67 7b b5 1b a9 af 19 38 89 63 57 42 7c # and the other allows to set one register # echo 2 170 > /sys/devices/platform/gta02-hdq.0/hdq/write writes 0xAA into register 2. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19bq27000-battery-driver.patchmokopatches
2008-11-19fiq-hdq.patchmokopatches
2008-10-20Merge git://git.infradead.org/battery-2.6Linus Torvalds
* git://git.infradead.org/battery-2.6: bq27x00_battery: use unaligned access helper power_supply: fix dependency of tosa_battery power_supply: Support for Texas Instruments BQ27200 battery managers power_supply: Add function to return system-wide power state pda_power: Check and handle return value of set_irq_wake
2008-10-20x86: sysfs: kill owner field from attributeParag Warudkar
Tejun's commit 7b595756ec1f49e0049a9e01a1298d53a7faaa15 made sysfs attribute->owner unnecessary. But the field was left in the structure to ease the merge. It's been over a year since that change and it is now time to start killing attribute->owner along with its users - one arch at a time! This patch is attempt #1 to get rid of attribute->owner only for CONFIG_X86_64 or CONFIG_X86_32 . We will deal with other arches later on as and when possible - avr32 will be the next since that is something I can test. Compile (make allyesconfig / make allmodconfig / custom config) and boot tested. akpm: the idea is that we put the declaration of sttribute.owner inside `#ifndef CONFIG_X86'. But that proved to be too ambitious for now because new usages kept on turning up in subsystem trees. [akpm: remove the ifdef for now] Signed-off-by: Parag Warudkar <parag.lkml@gmail.com> Cc: Greg KH <greg@kroah.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Tejun Heo <htejun@gmail.com> Cc: Len Brown <lenb@kernel.org> Cc: Jens Axboe <jens.axboe@oracle.com> Cc: Jean Delvare <khali@linux-fr.org> Cc: Roland Dreier <rolandd@cisco.com> Cc: David Brownell <david-b@pacbell.net> Cc: Alessandro Zummo <a.zummo@towertech.it> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-28 12:11:06 +0000