The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Jaffer Kapasi <jkapasi@linear.com>
Subject: Re: [PATCH] regulator: Add LTC3676 support
Date: Wed, 10 Aug 2016 12:41:40 +0100	[thread overview]
Message-ID: <20160810114140.GJ9347@sirena.org.uk> (raw)
In-Reply-To: <1470785767-4426-1-git-send-email-tharvey@gateworks.com>

[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]

On Tue, Aug 09, 2016 at 04:36:07PM -0700, Tim Harvey wrote:

Mostly looks good but quite a few issues with not using framework
features here, a lot of the code can be factored out into the core:

> +	/* DVB reference select is bit5 of DVBA reg */
> +	mask = 1 << 5;
> +
> +	if (mode != REGULATOR_MODE_STANDBY)
> +		bit = mask;	/* Select DVBB */

This will silently treat any mode other than standby identically which
is buggy, it should reject any mode not supported.

> +/* LDO1 always on fixed 0.8V-3.3V via scalar via R1/R2 feeback res */
> +static struct regulator_ops ltc3676_fixed_standby_regulator_ops = {
> +};

Remove this, it's pointless.

> +	node = of_get_child_by_name(dev->of_node, "regulators");
> +	if (!node) {
> +		dev_err(dev, "regulators node not found\n");
> +		return -EINVAL;
> +	}
> +
> +	ret = of_regulator_match(dev, node, ltc3676_matches,
> +				 ARRAY_SIZE(ltc3676_matches));

Use the core support for parsing regulators from OF, don't open code it.

> +	/* parse feedback voltage deviders: LDO3 doesn't have them */
> +	for (i = 0; i < LTC3676_NUM_REGULATORS; i++) {
> +		struct ltc3676_regulator *desc = &ltc3676->regulator_descs[i];
> +		struct device_node *np = ltc3676_matches[i].of_node;
> +		u32 vdiv[2];

There's a callback for parsing additional properties out of the
subnodes, of_parse_cb.

> +static bool ltc3676_readable_reg(struct device *dev, unsigned int reg)
> +{
> +	switch (reg) {
> +		case LTC3676_IRQSTAT:
> +		case LTC3676_BUCK1:

Please follow the kernel coding style.

> +	dev_dbg(dev, "irq%d irqstat=0x%02x\n", irq, irqstat);
> +	if (irqstat & LTC3676_IRQSTAT_THERMAL_WARN) {
> +		dev_info(dev, "Over-temperature Warning\n");

dev_warn()

> +static void ltc3676_apply_fb_voltage_divider(struct ltc3676_regulator *rdesc)
> +{
> +	struct regulator_desc *desc = &rdesc->desc;
> +
> +	if (!rdesc->r1 || !rdesc->r2)
> +		return;

This is a bug if we ever get here, we should be complaining loudly.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-08-10 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 23:36 [PATCH] regulator: Add LTC3676 support Tim Harvey
2016-08-10 11:41 ` Mark Brown [this message]
2016-08-11  0:44   ` Tim Harvey
2016-08-11  9:45     ` Mark Brown
2016-08-11 20:48       ` Tim Harvey
2016-08-12  9:21         ` Mark Brown
2016-08-10 22:28 ` Rob Herring
2016-08-11  0:46   ` Tim Harvey
2016-08-15 19:40 ` [PATCH v2] " Tim Harvey
2016-08-16 11:30   ` Applied "regulator: Add LTC3676 support" to the regulator tree Mark Brown

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=20160810114140.GJ9347@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jkapasi@linear.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tharvey@gateworks.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