29 Oct, 2010

1 commit

  • Commit f03f91826 (regulator: Add option for machine drivers
    to enable the dummy regulator) in the regulators tree
    seems to have introduced the following build break when
    CONFIG_REGULATOR_DUMMY is disabled. Fix this.

    CC drivers/regulator/dummy.o
    drivers/regulator/dummy.c:41: error: redefinition of 'regulator_dummy_init'
    drivers/regulator/dummy.h:28: note: previous definition of 'regulator_dummy_init' was here
    make[2]: *** [drivers/regulator/dummy.o] Error 1
    make[1]: *** [drivers/regulator] Error 2
    make: *** [drivers] Error 2

    Signed-off-by: Anand Gadiyar
    Cc: Liam Girdwood
    Cc: Mark Brown
    Acked-by: Randy Dunlap
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Anand Gadiyar
     

03 Mar, 2010

1 commit

  • In order to ease transitions with drivers are boards start using regulators
    provide an option to cause all regulator_get() calls to succeed, with a
    dummy always on regulator being supplied where one has not been configured.
    A warning is printed whenever the dummy regulator is used to aid system
    development.

    This regulator does not implement any regulator operations but will allow
    simple consumers which only do enable() and disable() calls to run. It
    is kept separate from the fixed voltage regulator to avoid Kconfig
    confusion on the part of users when it is extended to allow boards to
    explicitly use the dummy regulator to simplify cases where the majority
    of supplies are from fixed regulators without software control.

    This option is currently only effective for systems which do not specify
    full constriants. If required an override could also be provided to allow
    these systems to use the dummy regulator, though it is likely that
    unconfigured supplies on such systems will lead to error due to
    regulators being powered down more aggressively when not in use.

    Signed-off-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Mark Brown