From: Mark Brown <broonie@kernel.org>
To: Wenyou Yang <wenyou.yang@atmel.com>
Cc: lgirdwood@gmail.com, grant.likely@linaro.org,
rob.herring@calxeda.com, vpalatin@chromium.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
plagnioj@jcrosoft.com, nicolas.ferre@atmel.com
Subject: Re: [PATCH 1/3] regulator: act8865: add PMIC(Power Management IC) driver
Date: Thu, 12 Dec 2013 16:51:49 +0000 [thread overview]
Message-ID: <20131212165149.GO11044@sirena.org.uk> (raw)
In-Reply-To: <1386811131-2720-2-git-send-email-wenyou.yang@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
On Thu, Dec 12, 2013 at 09:18:49AM +0800, Wenyou Yang wrote:
The main thing with this driver seems to be that it needs a bit of
modernisation to use current kernel features and APIs - there's nothing
terribly wrong from a quick glance through but it needs an update.
Details below.
> --- a/drivers/regulator/Kconfig
> +++ b/drivers/regulator/Kconfig
> @@ -577,5 +577,12 @@ config REGULATOR_WM8994
> This driver provides support for the voltage regulators on the
> WM8994 CODEC.
>
> +config REGULATOR_ACT8865
> + tristate "Active-semi act8865 voltage regulator"
> + depends on I2C
> + help
> + This driver controls a active-semi act8865 voltage output
> + regulator via I2C bus.
> +
Please keep this and the Makefile sorted.
> +static int act8865_read_reg(struct act8865_data *act8865, u8 reg)
> +{
> + int ret = i2c_smbus_read_byte_data(act8865->client, reg);
> + if (ret > 0)
> + ret &= 0xff;
> +
> + return ret;
> +}
Use regmap for register I/O and use the helpers provided by the core.
> +static int act8865_set_voltage_sel(struct regulator_dev *rdev, u32 selector)
> +{
> + struct act8865_data *act8865 = rdev_get_drvdata(rdev);
> + int id = rdev_get_id(rdev);
> + u32 reg = act8865_vset_reg_addr(act8865, id);
Throughout the file the indentation is a really strange mix of the first
two lines (which are the normal kernel style) and the bottom line (which
isn't).
> + pr_info("%s: suspend voltage %dmV\n", rdev->desc->name, uV / 1000);
Remove noisy logging like this.
> + rdev[i] = regulator_register(&act8865_reg[id], &config);
devm_regulator_register().
> +static int __init act8865_pmu_init(void)
> +{
> + return i2c_add_driver(&act8865_pmu_driver);
> +}
> +subsys_initcall(act8865_pmu_init);
module_i2c_driver().
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-12 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 1:18 [PATCH 0/3] regulator: act8865: add PMIC driver Wenyou Yang
2013-12-12 1:18 ` [PATCH 1/3] regulator: act8865: add PMIC(Power Management IC) driver Wenyou Yang
2013-12-12 16:51 ` Mark Brown [this message]
2013-12-13 7:10 ` Yang, Wenyou
2013-12-13 10:45 ` Mark Brown
2013-12-12 1:18 ` [PATCH 2/3] regulator: act8865: add device tree binding doc Wenyou Yang
2013-12-12 16:52 ` Mark Brown
2013-12-12 1:18 ` [PATCH 3/3] ARM: dts: sama5d3xcm: add the regulator device node Wenyou Yang
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=20131212165149.GO11044@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=rob.herring@calxeda.com \
--cc=vpalatin@chromium.org \
--cc=wenyou.yang@atmel.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).