accessing SD_3V3 in drivers/mmc/host/s3cmci.c
andy at openmoko.com
Thu Feb 5 14:24:41 CET 2009
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
|> I suggest dealing with this by providing a standard regulator API
|> set_power() in the s3cmci driver that platforms which use regulators can
|> assign in their platform data. This avoids people rewriting the
|> standard regulator API implementation.
| That sounds good to me. It would also remove the above discomfort,
| because you'd only call it if you're sure there is a regulator.
| Thanks a lot for explaining !
Mmm, as I said but without the mugging: ''we can migrate regulator stuff
entirely out of that file using the existing callback.''.
It's kind of Mark to bother to answer but I think we can probably take a
pee ourselves without involving someone upstream.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-kernel