From: Mark Brown <broonie@kernel.org>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
mripard@kernel.org, heiko@sntech.de, shawnguo@kernel.org,
laurent.pinchart@ideasonboard.com, icenowy@aosc.io,
mchehab+samsung@kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] regulator: mpq7920: add mpq7920 regulator driver
Date: Thu, 19 Dec 2019 12:44:02 +0000 [thread overview]
Message-ID: <20191219124402.GC5047@sirena.org.uk> (raw)
In-Reply-To: <20191219103721.10935-4-sravanhome@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Thu, Dec 19, 2019 at 11:37:20AM +0100, Saravanan Sekar wrote:
This looks pretty good, a few small issues below:
> @@ -0,0 +1,376 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * mpq7920.c - mps mpq7920
> + *
> + * Copyright 2019 Monolithic Power Systems, Inc
Please keep the entire comment a C++ one so things look more
intentional.
> +static int mpq7920_set_ramp_delay(struct regulator_dev *rdev, int ramp_delay)
> +{
> + unsigned int ramp_val = (ramp_delay <= 4000) ? 3 : 2;
> +
> + return regmap_update_bits(rdev->regmap, MPQ7920_REG_CTL0,
> + MPQ7920_MASK_DVS_SLEWRATE, ramp_val << 6);
> +}
This should validate the input. Please also avoid abusing the ternery
operator like this, just write normal logic statements to make the code
more readable.
> + struct regulator_desc *rdesc;
> + struct regulator_ops *ops;
> +
> + for (i = 0; i < MPQ7920_MAX_REGULATORS; i++) {
> + rdesc = &info->rdesc[i];
> + ops = rdesc->ops;
> + if (rdesc->curr_table) {
> + ops->get_current_limit =
> + regulator_get_current_limit_regmap;
> + ops->set_current_limit =
> + regulator_set_current_limit_regmap;
> + }
It would be better to make these constant at build time rather than
patching at runtime, that lets things like static checkers do their
thing more easily.
> + ret = mpq7920_regulator_register(info, &config);
> + if (ret < 0)
> + dev_err(dev, "Failed to register regulator!\n");
This function has one caller, just inline it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-19 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:37 [PATCH 0/4] Add regulator support for mpq7920 Saravanan Sekar
2019-12-19 10:37 ` [PATCH 1/4] dt-bindings: Add an entry for Monolithic Power System, MPS Saravanan Sekar
2019-12-19 10:37 ` [PATCH 2/4] dt-bindings: regulator: add document bindings for mpq7920 Saravanan Sekar
2019-12-19 11:18 ` Maxime Ripard
2019-12-19 10:37 ` [PATCH 3/4] regulator: mpq7920: add mpq7920 regulator driver Saravanan Sekar
2019-12-19 12:44 ` Mark Brown [this message]
2019-12-19 10:37 ` [PATCH 4/4] MAINTAINERS: Add entry for mpq7920 PMIC driver Saravanan Sekar
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=20191219124402.GC5047@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=icenowy@aosc.io \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sravanhome@gmail.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