<br><br><div class="gmail_quote">2009/5/7 Joerg Reisenweber <span dir="ltr"><<a href="mailto:joerg@openmoko.org">joerg@openmoko.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="h5"><br>
</div>Correct - usbdevstat allows 100mA, 500mA, 1A, and suspend (Tbl. 98, MBCC7),<br>
anyway...<br>
Setting chg_curlim won't help whatsoever, as you can set it only during device<br>
powered up and system running, and during this time the system consumption<br>
USB-to-SYS will add to the chg_curlim you set. So you exceed intended USB<br>
current by setting chg_curlim to the value you intend for USB current, just<br>
to shutdown device after that and hope to reach 'correct' USB current then<br>
eventually - that's silly.<br>
<font color="#888888"></font><br></blockquote></div><br>In my case I used setting chg_curlim also for when phone is on.<br>Yes chg_curlim does not help to force usb real current to ie. 750m exactly.<br>But ! This way I could have my phone use approx 750mA when on (by setting chg_curlim to 500mA). <br>
<br>Of course it may sometimes consume up to 1A if needed (the peaks I was talking about...).<br>But this is ok in my case for my weak dumb charger.<br>What would not be ok is having chg_curlim not forced and phone pulling 1A for 30 minutes continuously while charging the battery faster than I need...<br>
(And usb_curlim to 500mA would on the other hand not charge quickly enough (about 300mA).)<br>