From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sangbeom Kim <sbkim73@samsung.com>
Cc: "'Liam Girdwood'" <lrg@ti.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Add S5M8767 regulator driver
Date: Sun, 23 Oct 2011 10:30:20 +0100 [thread overview]
Message-ID: <20111023093020.GC3135@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <009501cc915b$809ce880$81d6b980$@com>
On Sun, Oct 23, 2011 at 05:12:27PM +0900, Sangbeom Kim wrote:
This mostly looks good, a few smaller comments below but nothing major.
> +static int s5m8767_reg_enable_suspend(struct regulator_dev *rdev)
> +{
> + return 0;
> +}
> +static int s5m8767_reg_disable_suspend(struct regulator_dev *rdev)
> +{
I guess you need an implementation for enable_suspend() (otherwise you
can't do disable->enable).
> + {
> + .name = "AP 32KHz",
> + .id = S5M8767_32KHZAP_EN,
> + .ops = &s5m8767_others_ops,
> + .type = REGULATOR_VOLTAGE,
> + .owner = THIS_MODULE,
> + }, {
> + .name = "CP 32KHz",
> + .id = S5M8767_32KHZAP_EN,
> + .ops = &s5m8767_others_ops,
> + .type = REGULATOR_VOLTAGE,
> + .owner = THIS_MODULE,
> + },
Do these actually share anything with the other regulators? If not then
I guess it's better to do with the struct clk framework.
> + if (!pdata) {
> + dev_err(pdev->dev.parent, "Platform data not supplied\n");
> + return -ENODEV;
> + }
It should be possible to register without platform data now (giving
readback only support). Older versions of the regulator API required
constraints.
> + dev_warn(&pdev->dev, "Duplicated gpio
> request"
> + " for SET3\n");
Please keep the strings on one line (it makes grepping for errors
easier).
next prev parent reply other threads:[~2011-10-23 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 8:12 [PATCH] regulator: Add S5M8767 regulator driver Sangbeom Kim
2011-10-23 9:30 ` Mark Brown [this message]
2011-10-23 10:59 ` Sangbeom Kim
-- strict thread matches above, loose matches on Subject: below --
2011-10-21 10:45 Sangbeom Kim
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=20111023093020.GC3135@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sbkim73@samsung.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;
as well as URLs for NNTP newsgroup(s).