Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: 'MyungJoo Ham' <myungjoo.ham@samsung.com>,
	linux-arm-kernel@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.org, sameo@linux.intel.com,
	broonie@opensource.wolfsonmicro.com, kyungmin.park@samsung.com,
	myungjoo.ham@gmail.com, lrg@slimlogic.co.uk
Subject: RE: [PATCH] regulator: MAX8998: set_voltage bugfix. ramp_up delay and min/max voltage
Date: Fri, 16 Jul 2010 10:50:53 +0200	[thread overview]
Message-ID: <011801cb24c4$02ef53a0$08cdfae0$%szyprowski@samsung.com> (raw)
In-Reply-To: <1279267760-6971-1-git-send-email-myungjoo.ham@samsung.com>

Hello,

On Friday, July 16, 2010 10:09 AM MyungJoo Ham wrote:

> Two issues are addressed for max8998_set_voltage function.
> 
> 1. Min/Max Voltage.
> 
> 	max8998_set_voltage had been using the voltage value of
> 
> 	min ( voltage[i] >= max_vol , i )
> 
> 	This is corrected to use:
> 
> 	min ( voltage[i] >= min_vol , i )
> 
> 2. Ramp Up Delay.
> 
> 	max8998_set_voltage should provide delay for BUCK1/2
> if ENRAMP is on. It reads RAMP value from ONOFF4 register to determine
> RAMP delay length. However, when max8998_set_voltage's new voltage is
> lower than the previous, we don't care because it does not deteriorate
> the stability.
> 
> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>

Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>

> --
> I've omitted some CC in the previous email, adding them here. Sorry for the
> duplicated submission.
> ---
>  drivers/regulator/max8998.c |   30 ++++++++++++++++++++++++++++--
>  1 files changed, 28 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/regulator/max8998.c b/drivers/regulator/max8998.c
> index 1cca8b5..99c5279 100644
> --- a/drivers/regulator/max8998.c
> +++ b/drivers/regulator/max8998.c
> @@ -28,6 +28,7 @@
>  #include <linux/slab.h>
>  #include <linux/interrupt.h>
>  #include <linux/mutex.h>
> +#include <linux/delay.h>
>  #include <linux/platform_device.h>
>  #include <linux/regulator/driver.h>
>  #include <linux/mfd/max8998.h>
> @@ -302,10 +303,13 @@ static int max8998_set_voltage(struct regulator_dev
> *rdev,
>  	struct max8998_data *max8998 = rdev_get_drvdata(rdev);
>  	struct i2c_client *i2c = max8998->iodev->i2c;
>  	int min_vol = min_uV / 1000, max_vol = max_uV / 1000;
> +	int previous_vol = 0;
>  	const struct voltage_map_desc *desc;
>  	int ldo = max8998_get_ldo(rdev);
>  	int reg, shift = 0, mask, ret;
>  	int i = 0;
> +	u8 val;
> +	bool en_ramp = false;
> 
>  	if (ldo > ARRAY_SIZE(ldo_voltage_map))
>  		return -EINVAL;
> @@ -317,15 +321,37 @@ static int max8998_set_voltage(struct regulator_dev
> *rdev,
>  	if (max_vol < desc->min || min_vol > desc->max)
>  		return -EINVAL;
> 
> -	while (desc->min + desc->step*i < max_vol &&
> +	while (desc->min + desc->step*i < min_vol &&
>  	       desc->min + desc->step*i < desc->max)
>  		i++;
> 
> +	if (desc->min + desc->step*i > max_vol)
> +		return -EINVAL;
> +
>  	ret = max8998_get_voltage_register(rdev, &reg, &shift, &mask);
>  	if (ret)
>  		return ret;
> 
> -	return max8998_update_reg(i2c, reg, i<<shift, mask<<shift);
> +	/* wait for RAMP_UP_DELAY if rdev is BUCK1/2 and
> +	 * ENRAMP is ON */
> +	if (ldo == MAX8998_BUCK1 || ldo == MAX8998_BUCK2) {
> +		max8998_read_reg(i2c, MAX8998_REG_ONOFF4, &val);
> +		if (val & (1 << 4)) {
> +			en_ramp = true;
> +			previous_vol = max8998_get_voltage(rdev);
> +		}
> +	}
> +
> +	ret = max8998_update_reg(i2c, reg, i<<shift, mask<<shift);
> +
> +	if (en_ramp == true) {
> +		int difference = desc->min + desc->step * i
> +			- previous_vol / 1000;
> +		if (difference > 0)
> +			udelay(difference / ((val & 0x0f) + 1));
> +	}
> +
> +	return ret;
>  }
> 
>  static struct regulator_ops max8998_ldo_ops = {
> --
> 1.6.3.3


Best regards
--
Marek Szyprowski
Samsung Poland R&D Center

  parent reply	other threads:[~2010-07-16  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16  8:09 [PATCH] regulator: MAX8998: set_voltage bugfix. ramp_up delay and min/max voltage MyungJoo Ham
2010-07-16  8:20 ` Mark Brown
2010-07-16  8:50 ` Marek Szyprowski [this message]
2010-07-17 18:24 ` Liam Girdwood
2010-07-20  6:07   ` [PATCH v2] " Marek Szyprowski
2010-07-20  8:54     ` Mark Brown
2010-07-22 12:02     ` Liam Girdwood
  -- strict thread matches above, loose matches on Subject: below --
2010-07-16  7:46 [PATCH] " MyungJoo Ham

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='011801cb24c4$02ef53a0$08cdfae0$%szyprowski@samsung.com' \
    --to=m.szyprowski@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=myungjoo.ham@gmail.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sameo@linux.intel.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