From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org,
Igor Grinberg <grinberg@compulab.co.il>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Walleij <linus.ml.walleij@gmail.com>
Subject: Re: [PATCH] regulator: Add option for machine drivers to enable the dummy regulator
Date: Wed, 6 Oct 2010 06:09:17 +0200 [thread overview]
Message-ID: <201010060609.17412.marek.vasut@gmail.com> (raw)
In-Reply-To: <1286331512-4608-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Dne St 6. října 2010 04:18:32 Mark Brown napsal(a):
> Allow machine drivers to explicitly enable the use of the dummy regulator,
> enabling simpler support for systems with only a few specific supplies
> visible to software.
>
> It is strongly recommended that this is not used on systems with
> substantial software control over their PMICs, for maximum functionality
> constrints should be as fully specified as possible.
This still solves nothing ... This leaves boards broken and the granularity is
too big. Consider there are boards that use regulator for MMC, but not for
ADS7846 for example.
Cheers
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/regulator/Makefile | 3 +--
> drivers/regulator/core.c | 22 ++++++++++++++++++++++
> include/linux/regulator/machine.h | 5 +++++
> 3 files changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/regulator/Makefile b/drivers/regulator/Makefile
> index 8285fd8..f58bfdb 100644
> --- a/drivers/regulator/Makefile
> +++ b/drivers/regulator/Makefile
> @@ -3,14 +3,13 @@
> #
>
>
> -obj-$(CONFIG_REGULATOR) += core.o
> +obj-$(CONFIG_REGULATOR) += core.o dummy.o
> obj-$(CONFIG_REGULATOR_FIXED_VOLTAGE) += fixed.o
> obj-$(CONFIG_REGULATOR_VIRTUAL_CONSUMER) += virtual.o
> obj-$(CONFIG_REGULATOR_USERSPACE_CONSUMER) += userspace-consumer.o
>
> obj-$(CONFIG_REGULATOR_AD5398) += ad5398.o
> obj-$(CONFIG_REGULATOR_BQ24022) += bq24022.o
> -obj-$(CONFIG_REGULATOR_DUMMY) += dummy.o
> obj-$(CONFIG_REGULATOR_LP3971) += lp3971.o
> obj-$(CONFIG_REGULATOR_MAX1586) += max1586.o
> obj-$(CONFIG_REGULATOR_TWL4030) += twl-regulator.o
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index 422a709..bf82d01 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -33,6 +33,7 @@ static DEFINE_MUTEX(regulator_list_mutex);
> static LIST_HEAD(regulator_list);
> static LIST_HEAD(regulator_map_list);
> static int has_full_constraints;
> +static bool board_wants_dummy_regulator;
>
> /*
> * struct regulator_map
> @@ -1108,6 +1109,11 @@ static struct regulator *_regulator_get(struct
> device *dev, const char *id, }
> }
>
> + if (board_wants_dummy_regulator) {
> + rdev = dummy_regulator_rdev;
> + goto found;
> + }
> +
> #ifdef CONFIG_REGULATOR_DUMMY
> if (!devname)
> devname = "deviceless";
> @@ -2461,6 +2467,22 @@ void regulator_has_full_constraints(void)
> EXPORT_SYMBOL_GPL(regulator_has_full_constraints);
>
> /**
> + * regulator_use_dummy_regulator - Provide a dummy regulator when none is
> found + *
> + * Calling this function will cause the regulator API to provide a
> + * dummy regulator to consumers if no physical regulator is found,
> + * allowing most consumers to proceed as though a regulator were
> + * configured. This allows systems such as those with software
> + * controllable regulators for the CPU core only to be brought up more
> + * readily.
> + */
> +void regulator_use_dummy_regulator(void)
> +{
> + board_wants_dummy_regulator = true;
> +}
> +EXPORT_SYMBOL_GPL(regulator_use_dummy_regulator);
> +
> +/**
> * rdev_get_drvdata - get rdev regulator driver data
> * @rdev: regulator
> *
> diff --git a/include/linux/regulator/machine.h
> b/include/linux/regulator/machine.h index e298028..761c745 100644
> --- a/include/linux/regulator/machine.h
> +++ b/include/linux/regulator/machine.h
> @@ -189,10 +189,15 @@ int regulator_suspend_prepare(suspend_state_t state);
>
> #ifdef CONFIG_REGULATOR
> void regulator_has_full_constraints(void);
> +void regulator_use_dummy_regulator(void);
> #else
> static inline void regulator_has_full_constraints(void)
> {
> }
> +
> +static inline void regulator_use_dummy_regulator(void)
> +{
> +}
> #endif
>
> #endif
next prev parent reply other threads:[~2010-10-06 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 2:18 [PATCH] regulator: Add option for machine drivers to enable the dummy regulator Mark Brown
2010-10-06 4:09 ` Marek Vasut [this message]
2010-10-06 5:08 ` Mark Brown
2010-10-10 10:14 ` Liam Girdwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010060609.17412.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=grinberg@compulab.co.il \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox