Isn't Wifi supposed to be off by default?

Andy Green andy at
Fri Jan 16 10:13:30 CET 2009

Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> but the rfkill + power
|> reduction thing replacing existing alleged power control stuff is also
|> really needed if we didn't know that already.
| I'm afraid rfkill will not be the best choice for this after all.

OK I note we learn this by doing it, and upstream rfkill could not tell
us since it is detail under our responsibility.

|> Module removal should also enforce lowest power mode if it isn't already
|> too I guess.
| If you remove s3cmci.ko, then it does that. If you only remove
| ar6000.ko, then the driver will still keep the bus powered and
| the clock running (it's the latter that makes the difference).
| That's the 17mW again.

Which clock, SDIO external clock?  We can gate it to only operate during
pending access like we did Glamo.  It won't hurt GPS and it will block
bulk of this 17mW I guess.

| Suspend also takes down the MMC driver, so it gets the best power
| saving, no matter what else has been done.

Makes sense.

So we explain the kernel policy for "turning off" WLAN is to either not
insert the modules, or modprobe -r them.

We can take out the /sys if that claims to impact this then, and we're done?

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


More information about the openmoko-kernel mailing list