From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: dahuang@nvidia.com
Cc: lrg@ti.com, mike@compulab.co.il, sameo@linux.intel.com,
xxie@nvidia.com, gking@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: tps6586x: add SMx slew rate setting
Date: Thu, 4 Aug 2011 21:12:39 +0900 [thread overview]
Message-ID: <20110804121237.GA9959@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1312457662-4490-1-git-send-email-dahuang@nvidia.com>
On Thu, Aug 04, 2011 at 07:34:22PM +0800, dahuang@nvidia.com wrote:
> From: Danny Huang <dahuang@nvidia.com>
>
> Add output vlotage slew rate setting for SM0/SM1
>
> From: Xin Xie <xxie@nvidia.com>
Looks like you messed up here, I rather suspect Xin Xie rather than you
should be the author?
> +static int tps6586x_regulator_set_slew_rate(struct platform_device *pdev)
> +{
> + struct device *parent = pdev->dev.parent;
> + struct regulator_init_data *p = pdev->dev.platform_data;
> + struct tps6586x_settings *setting = p->driver_data;
If this is system configured data (which is what one would expect for
this) it should be coming in as platform data not driver data - what's
happened here?
> + default:
> + dev_err(&pdev->dev, "invalid regulator ID\n");
> + return -EINVAL;
> + }
Should say what data is invalid here, otherwise it's not going to be at
all obvious what's invalid.
> +enum {
> + TPS6586x_SLEW_RATE_INSTANTLY,
> + TPS6586x_SLEW_RATE_110UV,
> + TPS6586x_SLEW_RATE_220UV,
> + TPS6586x_SLEW_RATE_440UV,
> + TPS6586x_SLEW_RATE_880UV,
> + TPS6586x_SLEW_RATE_1760UV,
> + TPS6586x_SLEW_RATE_3520UV,
> + TPS6586x_SLEW_RATE_7040UV,
> +};
If the values are being written directly to the chip you should probably
explicitly specify the values that are being set.
next prev parent reply other threads:[~2011-08-04 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 11:34 [PATCH] regulator: tps6586x: add SMx slew rate setting dahuang
2011-08-04 12:12 ` Mark Brown [this message]
2011-08-05 11:51 ` Danny Huang
2011-08-08 9:37 ` Mark Brown
2011-08-08 12:28 ` Danny Huang
2011-08-08 13:32 ` Mark Brown
2011-08-04 12:42 ` Mark Brown
2011-08-05 11:53 ` Danny Huang
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 10:47 dahuang
2011-08-09 16:06 ` Mark Brown
2011-08-22 9:35 ` Samuel Ortiz
2011-08-22 9:41 ` Liam Girdwood
2011-08-28 16:49 ` 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=20110804121237.GA9959@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dahuang@nvidia.com \
--cc=gking@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mike@compulab.co.il \
--cc=sameo@linux.intel.com \
--cc=xxie@nvidia.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.