regulator: improved mode error checks
authorDavid Brownell <dbrownell@users.sourceforge.net>
Sun, 16 Nov 2008 19:46:56 +0000 (11:46 -0800)
committerLiam Girdwood <lrg@slimlogic.co.uk>
Thu, 8 Jan 2009 20:10:30 +0000 (20:10 +0000)
commite573520b171095c106ffbbbf4f9cbed6d9bff576
treeab0d3b0e4adadcf6fc68915f7703048b4aea2a76
parent412aec610559bdb602a0a21ce149ba8ffbb6f983
regulator: improved mode error checks

Minor bugfixes in handling of regulator modes:

 - have the routine verifying regulator modes check against
   the set of legal modes (!);

 - have regulator_set_optimum_mode() verify the return value
   of regulator_ops.get_optimum_mode(), like drms_uA_update();

 - one call to regulator_ops.set_mode() treated zero as a
   failure code; make this consistent with other callers.

Both regulator_set_mode() and regulator_set_optimum_mode() now
require valid_ops_mask to include REGULATOR_CHANGE_MODE; that
seems like a bugfix too.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
drivers/regulator/core.c