Isn't Wifi supposed to be off by default?

Andy Green andy at
Fri Jan 16 12:11:16 CET 2009

Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> Which clock, SDIO external clock?  We can gate it to only operate during
|> pending access like we did Glamo.
| Yes, it's something that's probably safe to implement in the S3C MCI
| driver. Nothing else in the system needs to know about it.
|>  It won't hurt GPS and it will block bulk of this 17mW I guess.
| Yes, when I stopped the clock by just forcing the pin low, I got
| the same current reduction (within measurement tolerances, i.e.,
| about +/-1.5mA in this case) as when shutting down the driver
| completely.

I guess some of that 1.5mA was the P-channel driver of the clock passing
fault current when it was high, so it'll be at least as good by the
sound of it.

|> So we explain the kernel policy for "turning off" WLAN is to either not
|> insert the modules, or modprobe -r them.
| For now, yes. Or to unbind it, if you want to avoid module
| insertion/removal overhead and make things work in a monolithic
| kernel as well.

OK, good point.

|> We can take out the /sys if that claims to impact this then, and
we're done?
| Yeah, I'll send you a patch that drops it from sysfs. We still
| need the internal mechanism to reset the module, but that can
| be a lot simpler.


- -Andy

Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the openmoko-kernel mailing list