Occasional fail to initiate resume by incoming call, easy workaround proposed

Andy Green andy at openmoko.com
Mon Feb 9 15:00:15 CET 2009

Hash: SHA1

Somebody in the thread at some point said:
| Andy Green <andy at openmoko.com> writes:
|> Maybe what we should do there is deprecate the reset control thing, bind
|> the sequencing for reset into the power_on thing along with toggling the
|> flowcontrolled state.  That's what we did for GTA03, sort of one stop
|> shop for powering it on with minimal knowledge about the device needed
|> then on rootfs.
| I fully agree and i was going to do that for quite some time (do not
| forget about the nasty "push-button" as well, that should be depressed
| after the modem is powered on, unlike what is done now), but i was
| distracted by other issues and somewhat lost motivation. It's still on
| my todo list though. (it was already discussed in details here)
| Anyway, what maximum msleep() in the power_on sysfs node do you find
| acceptable?

Whatever's needed is needed, whether we put it in there or the rootfs,
so we don't make matters worse.  I guess 2 - 3 seconds won't be too
crazy since it's a sleep and the echo can be &-ed or otherwise made
parallel, it's not inherently blocking the whole machine.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list