2009/5/7 Joerg Reisenweber jo...@openmoko.org
A
So you think the STANDARD kernel should care about this rather exotic case
which isn't specified properly (how long would this charger see the 1A
sometimes?) and needs massive care from userland anyway? I mean, there's
some reason PCF50633 is
On Thu, May 07, 2009 at 12:42:42AM +0200, Joerg Reisenweber wrote:
So taking in account your comments above this means the problem case
is intentionally shutting down the device during charging from solarpanel.
1) I don't see why anybody should do this
To save energy for later.
2) this
2009/5/7 Joerg Reisenweber jo...@openmoko.org
Correct - usbdevstat allows 100mA, 500mA, 1A, and suspend (Tbl. 98, MBCC7),
anyway...
Setting chg_curlim won't help whatsoever, as you can set it only during
device
powered up and system running, and during this time the system consumption
Am Do 7. Mai 2009 schrieb Cédric Berger:
2009/5/7 Joerg Reisenweber jo...@openmoko.org
Correct - usbdevstat allows 100mA, 500mA, 1A, and suspend (Tbl. 98,
MBCC7),
anyway...
Setting chg_curlim won't help whatsoever, as you can set it only during
device
powered up and system
Am So 3. Mai 2009 schrieb Rask Ingemann Lambertsen:
On Sat, May 02, 2009 at 03:30:10AM +0200, Joerg Reisenweber wrote:
Am Mi 29. April 2009 schrieb Cédric Berger:
On Tue, Apr 28, 2009 at 15:36, Joerg Reisenweber jo...@openmoko.org
wrote:
That's nonsense as there is no dumb charger
Am Mo 4. Mai 2009 schrieb Cédric Berger:
Sorry, my mail was not really clear.
Rask already answered questions.
But just about usb_limit :
2009/5/2 Joerg Reisenweber jo...@openmoko.org
No you have to push USB_CURLIM to 500mA, if you want 500mA.
[... ]
This way I have about
Sorry, my mail was not really clear.
Rask already answered questions.
But just about usb_limit :
2009/5/2 Joerg Reisenweber jo...@openmoko.org
No you have to push USB_CURLIM to 500mA, if you want 500mA.
[... ]
This way I have about 700-750mA pulled from my charger (though it can
peak
to
On Sat, May 02, 2009 at 03:30:10AM +0200, Joerg Reisenweber wrote:
Am Mi 29. April 2009 schrieb Cédric Berger:
On Tue, Apr 28, 2009 at 15:36, Joerg Reisenweber jo...@openmoko.org wrote:
That's nonsense as there is no dumb charger out there not being capable of
supplying 500mA. OTOH
Am Mi 29. April 2009 schrieb Cédric Berger:
On Tue, Apr 28, 2009 at 15:36, Joerg Reisenweber jo...@openmoko.org wrote:
That's nonsense as there is no dumb charger out there not being capable of
supplying 500mA. OTOH any management of maximum ingress current to USB by
whatever means
On Tue, Apr 28, 2009 at 15:36, Joerg Reisenweber jo...@openmoko.org wrote:
That's nonsense as there is no dumb charger out there not being capable of
supplying 500mA. OTOH any management of maximum ingress current to USB by
whatever means will inevitably fail when unplugging the charger
Am So 26. April 2009 schrieb Rask Ingemann Lambertsen:
On Sat, Apr 25, 2009 at 01:16:17PM +0100, Joerg Reisenweber wrote:
Am Di 21. April 2009 schrieb Paul Fertser:
drivers/power/pcf50633-charger.c:
/*
* We limit the charging current to be the USB current limit.
* The
On Sat, Apr 25, 2009 at 01:16:17PM +0100, Joerg Reisenweber wrote:
Am Di 21. April 2009 schrieb Paul Fertser:
drivers/power/pcf50633-charger.c:
/*
* We limit the charging current to be the USB current limit.
* The reason is that on pcf50633, when it enters PMU Standby mode,
*
Am Di 21. April 2009 schrieb Paul Fertser:
Joerg Reisenweber jo...@openmoko.org writes:
Am So 19. April 2009 schrieb Rask Ingemann Lambertsen:
On Sat, Apr 18, 2009 at 05:11:36PM -0700, Mike Montour wrote:
chg_curlim controls the battery charger, while usb_curlim controls the
total
Joerg Reisenweber jo...@openmoko.org writes:
Am So 19. April 2009 schrieb Rask Ingemann Lambertsen:
On Sat, Apr 18, 2009 at 05:11:36PM -0700, Mike Montour wrote:
chg_curlim controls the battery charger, while usb_curlim controls the
total current that can be drawn from the USB port
On Tue, Apr 21, 2009 at 02:19:04AM +0100, Joerg Reisenweber wrote:
Am So 19. April 2009 schrieb Rask Ingemann Lambertsen:
usb_curlim can be 0, 100, 500 or 1000 while chg_curlim is between 0
and 996 (in steps of about 4).
checked 8.12.6.9, Tbl 95, Tbl94, and it's mentioning :
Am So 19. April 2009 schrieb Rask Ingemann Lambertsen:
On Sat, Apr 18, 2009 at 05:11:36PM -0700, Mike Montour wrote:
chg_curlim controls the battery charger, while usb_curlim controls the
total current that can be drawn from the USB port (charging + the
current used by the
On Sat, Apr 18, 2009 at 05:11:36PM -0700, Mike Montour wrote:
chg_curlim controls the battery charger, while usb_curlim controls the
total current that can be drawn from the USB port (charging + the
current used by the Freerunner).
Note that whenever you set usb_curlim (directly or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Frazier ha scritto:
I'm trying to get my FR to force fast-charging (500mA) using my generic
usb car adaptor. However /sys/ seems to have been shuffled about a bit
and the wiki is no longer accurate.
Does anyone know what the current
Cameron Frazier wrote:
Does anyone know what the current means are to force fast charging at
500mA and could they share it with the list?
I don't know if there's a dbus/frameworkd way to do it, but the direct
method is:
echo 500 /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-mbc/usb_curlim
On Sat, Apr 18, 2009 at 16:35, Francesco de Virgilio
fradev...@gmail.com wrote:
I think this is the *greatest* fault of OM/SHR since the introduction of
2.6.28 kernel.
It's only one change in path. Nothing more has changed. I'm going to
add functionality of battery.py in SHR Settings.
On Sat, 2009-04-18 at 20:14 +0200, Johny Tenfinger wrote:
On Sat, Apr 18, 2009 at 16:35, Francesco de Virgilio
fradev...@gmail.com wrote:
I think this is the *greatest* fault of OM/SHR since the introduction of
2.6.28 kernel.
It's only one change in path. Nothing more has changed. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Frazier ha scritto:
On Sat, 2009-04-18 at 20:14 +0200, Johny Tenfinger wrote:
On Sat, Apr 18, 2009 at 16:35, Francesco de Virgilio
fradev...@gmail.com wrote:
I think this is the *greatest* fault of OM/SHR since the introduction of
2.6.28
On Sat, 2009-04-18 at 10:50 -0700, Mike Montour wrote:
Cameron Frazier wrote:
Does anyone know what the current means are to force fast charging at
500mA and could they share it with the list?
I don't know if there's a dbus/frameworkd way to do it, but the direct
method is:
echo 500
Cameron Frazier wrote:
Ahh, ok. Now things seem to be working correctly. One question though
what are the differences between usb_curlim and chg_curlim? I'm not
sure I fully understand what chg_curlim represents.
chg_curlim controls the battery charger, while usb_curlim controls the
On Sat, 2009-04-18 at 17:11 -0700, Mike Montour wrote:
Cameron Frazier wrote:
Ahh, ok. Now things seem to be working correctly. One question though
what are the differences between usb_curlim and chg_curlim? I'm not
sure I fully understand what chg_curlim represents.
chg_curlim
Am So 19. April 2009 schrieb Cameron Frazier:
On Sat, 2009-04-18 at 17:11 -0700, Mike Montour wrote:
Cameron Frazier wrote:
Ahh, ok. Now things seem to be working correctly. One question though
what are the differences between usb_curlim and chg_curlim? I'm not
sure I fully
26 matches
Mail list logo
