From: Liam Girdwood <lrg@slimlogic.co.uk>
To: sundar.iyer@stericsson.com
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
Linus WALLEIJ <linus.walleij@stericsson.com>
Subject: Re: [PATCH 1/1] regulator: return set_mode is same mode is requested
Date: Mon, 17 May 2010 20:44:19 +0100 [thread overview]
Message-ID: <1274125459.3185.18.camel@odin> (raw)
In-Reply-To: <1274111688.20589.54.camel@bnru01>
On Mon, 2010-05-17 at 21:24 +0530, Sundar R Iyer wrote:
> On Mon, 2010-05-17 at 17:34 +0200, Mark Brown wrote:
> > This doesn't seem like the right error handling - if the driver has a
> > set_mode() you'd *expect* it to have a get_mode() but there's no need
> > for it to be a strict requirement.
> True. In such a case, even a valid request would be lost! So now
> in the updated patch:
> - check if get_mode is present to avoid oops;
> - if get_mode is not present, proceed anyways for the request.
>
> Here is the updated patch:
>
> >From bad0d5eb51ef84be5b100e3dd0f5a590ea0529b6 Mon Sep 17 00:00:00 2001
> From: Sundar R Iyer <sundar.iyer@stericsson.com>
> Date: Fri, 14 May 2010 15:14:17 +0530
> Subject: [PATCH 1/1] regulator: return set_mode when same mode is requested
>
> save I/O costs by returning when the same mode is
> requested for the regulator
>
> Cc: Liam Girdwood <lrg@slimlogic.co.uk>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Acked-by: Linus Walleij <linus.walleij@stericsson.com>
> Signed-off-by: Sundar R Iyer <sundar.iyer@stericsson.com>
> ---
> drivers/regulator/core.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index 98e5d14..2248087 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -1745,6 +1745,7 @@ int regulator_set_mode(struct regulator *regulator, unsigned int mode)
> {
> struct regulator_dev *rdev = regulator->rdev;
> int ret;
> + int regulator_curr_mode;
>
> mutex_lock(&rdev->mutex);
>
> @@ -1754,6 +1755,15 @@ int regulator_set_mode(struct regulator *regulator, unsigned int mode)
> goto out;
> }
>
> + /* return if the same mode is requested */
> + if (rdev->desc->ops->get_mode) {
> + regulator_curr_mode = rdev->desc->ops->get_mode(rdev);
> + if (regulator_curr_mode == mode) {
> + ret = 0;
> + goto out;
> + }
> + }
> +
> /* constraints check */
> ret = regulator_check_mode(rdev, mode);
> if (ret < 0)
Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-05-17 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 14:09 [PATCH 1/1] regulator: return set_mode is same mode is requested Sundar Iyer
2010-05-17 14:35 ` Liam Girdwood
2010-05-17 14:44 ` Mark Brown
2010-05-17 14:56 ` Sundar R Iyer
2010-05-17 15:15 ` Sundar R Iyer
2010-05-17 15:34 ` Mark Brown
2010-05-17 15:54 ` Sundar R Iyer
2010-05-17 16:08 ` Mark Brown
2010-05-17 19:44 ` Liam Girdwood [this message]
2010-05-17 15:18 ` Sundar R Iyer
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=1274125459.3185.18.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sundar.iyer@stericsson.com \
/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