From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, nsekhar@ti.com
Subject: Re: [PATCH V3 2/2] regulator: tps65217: Add tps65217 regulator driver
Date: Sun, 8 Jan 2012 23:19:31 -0800 [thread overview]
Message-ID: <20120109071930.GC22134@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325670747-31429-1-git-send-email-anilkumar@ti.com>
On Wed, Jan 04, 2012 at 03:22:27PM +0530, AnilKumar Ch wrote:
This looks pretty good. A couple of small issues.
> +static int tps65217_vsel_to_uv_range1(unsigned int vsel)
> +{
> + int uV = 0;
> +
> + if (vsel > 15)
> + return -EINVAL;
> +
> + if (vsel <= 2)
> + uV = vsel * 100000 + 1000000;
> + else if (vsel <= 6)
> + uV = (vsel - 2) * 50000 + 1200000;
> + else if (vsel <= 9)
> + uV = (vsel - 6) * 100000 + 1400000;
> + else if (vsel == 10)
> + uV = 2500000;
> + else if (vsel == 11)
> + uV = 2750000;
> + else if (vsel == 12)
> + uV = 2800000;
> + else if (vsel == 13)
> + uV = 3000000;
> + else if (vsel == 14)
> + uV = 3100000;
> + else
> + uV = 3300000;
This looks like it should actually be a table - there's far too many
irregular steps here. The other regulators looked to be benefiting from
the use of calculations.
> +static int tps65217_pmic_dcdc_get_voltage(struct regulator_dev *dev)
> +{
> + int ret;
> + struct tps65217 *tps = rdev_get_drvdata(dev);
> + unsigned int data, dcdc = rdev_get_id(dev);
> +
> + if (dcdc < TPS65217_DCDC_1 || dcdc > TPS65217_DCDC_3)
> + return -EINVAL;
> +
> + ret = tps65217_reg_read(tps, tps->info[dcdc]->set_vout_reg, &data);
> + if (ret)
> + return ret;
> +
> + data &= tps->info[dcdc]->set_vout_mask;
> +
> + ret = tps->info[dcdc]->tps_range(data);
> + if (ret < 0)
> + dev_err(&dev->dev, "Failed to get voltage\n");
> +
> + return ret;
It seems odd to implement this as a vanilla get_voltage()
> +static int tps65217_pmic_dcdc_set_voltage(struct regulator_dev *dev,
> + unsigned selector)
> +{
but this as set_voltage_sel(). For non table based regulators plain
set_voltage() usually makes a bit more sense as we don't have to iterate
through the selectors looking for a match.
next prev parent reply other threads:[~2012-01-09 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:52 [PATCH V3 2/2] regulator: tps65217: Add tps65217 regulator driver AnilKumar Ch
2012-01-04 9:52 ` AnilKumar Ch
2012-01-09 7:19 ` Mark Brown [this message]
2012-01-11 8:22 ` AnilKumar, Chimata
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=20120109071930.GC22134@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=nsekhar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.