[PATCH 0/2] Add rfkill for WLAN

Andy Green andy at openmoko.com
Fri Jan 16 12:59:47 CET 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> So to be clear we have rfkill as RF kill and pull the module as power
|> management.
|
| Or unbind, see the other thread.
|
| If we turned off the clock, rfkill would probably be indistinguishable
| from unbind (btw, it was actually within something like 50uA, but the
| measurement itself has about 1.5mA of noise :)
|
| However, turning off the clock has other constraints, e.g., overcoming
| the fear of breaking oddball hardware that needs a permanent clock, so
| I'm not sure if this route is easily accessible. I'll ask around.

There's a flags field on MMC host platform stuff that lets you describe
what the host controller can handle, for example 4-bit or high speed
etc.  Adding a flag there that comes somehow from mach-gta02.c will
leave everyone else as they are.

I agree though in this case we are meddling with platform code and need
to take some care.

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

iEYEARECAAYFAklwdrMACgkQOjLpvpq7dMo0KQCfWGwTuG3MzB1nBy3EqPrNt7f2
tY8AoIJbZ0kan6dOW+F+HsY/F0JCa/bF
=h6HR
-----END PGP SIGNATURE-----



More information about the openmoko-kernel mailing list