Am Mi 20. August 2008 schrieb Andy Green: > Somebody in the thread at some point said: > | Am Di 19. August 2008 schrieb Andy Green: > |> So kernel gets stuck with the clock situation that was handed to us by > |> the bootloader -- the kernel doesn't "deal with" it at all. All it does > |> is turn off charging if it sees it has 100mA USB connection, but it > |> happily will try to turn on more than 500mW can deal with and die. > | > | still don't get it - why are we turning off charging? > > Charging enable somehow gives GTA02 a chance to die in a way we never > tracked down. So we keep it disabled unless it is going to do something > useful. As I understand, you are not "keeping it" disabled, you are intentionally disabling it. So there comes the chance of sudden death when re-enabling it later. I think we should set max usb current, and don't care at all about setting of charging (at least, if not even enabling it)
> Let's save this discussion for when we come at the kernel side solutions > needed when Qi is working, because this isn't any issue for Qi. I don't think so. When Qi is tampering with bat chg, it should do it right. Otherwise better keep fingers off charging setting, hoping for the default settings of PMU to be not completely silly. cheers jOERG
signature.asc
Description: This is a digitally signed message part.
