From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ux500: add ab8500-regulators machine specific data
Date: Wed, 1 Sep 2010 18:56:08 +0100 [thread overview]
Message-ID: <20100901175608.GF22444@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1283330411-3784-1-git-send-email-sundar.iyer@stericsson.com>
On Wed, Sep 01, 2010 at 02:10:11PM +0530, Sundar Iyer wrote:
> +#define AB8500_VAUXN_LDO_MIN_VOLTAGE (1100000)
> +#define AB8500_VAUXN_LDO_MAX_VOLTAGE (3300000)
> +struct regulator_init_data ab8500_vaux1_regulator = {
All these should be static.
> + .supply_regulator_dev = NULL,
No need to assign to NULL, that's the default value.
> + .constraints = {
> + .name = "ab8500-vaux1",
> + .min_uV = AB8500_VAUXN_LDO_MIN_VOLTAGE,
> + .max_uV = AB8500_VAUXN_LDO_MAX_VOLTAGE,
> + .valid_ops_mask = REGULATOR_CHANGE_VOLTAGE|
> + REGULATOR_CHANGE_STATUS,
> + },
> +};
Having operations for regulators with no consumers seems a bit strange.
> +/* supply for tvout, gpadc, TVOUT LDO */
> +#define AB8500_VTVOUT_LDO_MIN_VOLTAGE (1900000)
> +#define AB8500_VTVOUT_LDO_MAX_VOLTAGE (2100000)
> +
> +struct regulator_init_data ab8500_vtvout_init = {
> + .supply_regulator_dev = NULL,
> + .constraints = {
> + .name = "ab8500-vtvout",
> + .min_uV = AB8500_VTVOUT_LDO_MIN_VOLTAGE,
> + .max_uV = AB8500_VTVOUT_LDO_MAX_VOLTAGE,
> + .valid_ops_mask = REGULATOR_CHANGE_STATUS,
> + },
> +};
As does having voltage ranges for regulators without voltage change
permission. Given that half the #defines you're using are only used for
one regulator it'd probably also be better to just use the values
directly.
prev parent reply other threads:[~2010-09-01 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 8:40 [PATCH v3] ux500: add ab8500-regulators machine specific data Sundar Iyer
2010-09-01 17:56 ` Mark Brown [this message]
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=20100901175608.GF22444@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).