dev_info vs. dev_dbg
Andy Green
andy at openmoko.com
Sun Jul 20 22:13:54 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
| Can we replace most of the dev_info calls in places like pcf60533.c with
| dev_dbg? This would allow us to turn them on or off with a #define
| DEBUG. I am convinced that console output during suspend/resume is
| contributing to lockups. I had an 8 hour run without lockups recently
| when I removed all the chatter in pcf60533.c
OK, we'll give it a go, I'll make a patch. But... it makes it sound
like a tight and ugly race somewhere...
I assume the lockups are resume lockups?
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkiDnH0ACgkQOjLpvpq7dMoK9wCfWWwhZH4wz+dqBvSzQH/wHPG/
sP0An0Bc9LczVic4hHR2Md96gliNfr8p
=7KeE
-----END PGP SIGNATURE-----
More information about the openmoko-kernel
mailing list