From: Mark Brown <broonie@kernel.org>
To: James Ban <james.ban.opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Support Opensource <support.opensource@diasemi.com>,
LKML <linux-kernel@vger.kernel.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [RESEND PATCH V1] regulator: DA9211 : new regulator driver
Date: Wed, 14 May 2014 21:20:29 +0100 [thread overview]
Message-ID: <20140514202029.GL12304@sirena.org.uk> (raw)
In-Reply-To: <201405140306.s4E36COM023118@swsrvapps-01.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Wed, May 14, 2014 at 04:02:34AM +0100, James Ban wrote:
> This is the driver for the Dialog DA9211 Multi-phase 12A DC-DC Buck
> Converter regulator. It communicates via an I2C bus to the device.
This looks a lot like the DA9210 driver, is there really no opportunity
for code sharing here?
> + /*
> + * There are two voltage register set A & B for voltage ramping but
> + * either one of then can be active therefore we first determine
> + * the active register set.
> + */
I see this but...
> + /* Select register set B for suspend voltage ramping. */
> + if (regulator->reg_rselect == DA9211_RSEL_NO_GPIO) {
> + ret = regmap_update_bits(chip->regmap, info->conf.reg,
> + info->conf.sel_mask,
> + DA9211_VBUCKA_SEL_B);
> + if (ret < 0)
> + return ret;
> + }
..this fairly clearly says that suspend mode is set B and normal mode is
set A.
> +static int da9211_suspend_enable(struct regulator_dev *rdev)
> +{
> + struct da9211_regulator *regulator = rdev_get_drvdata(rdev);
> + struct da9211_regulator_info *info = regulator->info;
> + struct da9211 *chip = regulator->da9211;
> +
> + /* Select register set B for voltage ramping. */
> + if (regulator->reg_rselect == DA9211_RSEL_NO_GPIO)
> + return regmap_update_bits(chip->regmap, info->conf.reg,
> + info->conf.sel_mask,
> + DA9211_VBUCKA_SEL_B);
> + else
> + return 0;
> +}
This looks like it will immediately shift to the suspend voltage but
what this should do is set the voltage which will be set in suspend
mode - something else (usually a hardware signal during suspend) should
actually enter it.
> +int da9211_enable_irq(struct da9211 *chip, int irq)
> +{
> + enable_irq(irq);
> +
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(da9211_enable_irq);
> +int da9211_disable_irq(struct da9211 *chip, int irq)
> +int da9211_mask_irq(struct da9211 *chip, int irq)
> +int da9211_unmask_irq(struct da9211 *chip, int irq)
This looks bad... similarly most of the rest of the interrupt code.
What is it supposed to be doing?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-14 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 3:02 James Ban
2014-05-14 20:20 ` Mark Brown [this message]
2014-05-16 1:52 ` Opensource [James Seong-Won Ban]
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=20140514202029.GL12304@sirena.org.uk \
--to=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=g.liakhovetski@gmx.de \
--cc=james.ban.opensource@diasemi.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.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
all inboxes | Powered by JetHome®