From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sundar Iyer <sundar.iyer@stericsson.com>
Cc: lrg@slimlogic.co.uk, sameo@linux.intel.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
STEricsson_nomadik_linux@list.st.com,
Linus Walleij <linus.walleij@stericsson.com>,
"Acked-By: Bengt JONSSON" <bengt.g.jonsson@stericsson.com>
Subject: Re: [PATCH 3/3] ux500: add ab8500-regulators machine specific data
Date: Tue, 13 Jul 2010 11:00:12 +0100 [thread overview]
Message-ID: <20100713100012.GC12686@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1279002090-11234-4-git-send-email-sundar.iyer@stericsson.com>
On Tue, Jul 13, 2010 at 11:51:30AM +0530, Sundar Iyer wrote:
> +static struct regulator_consumer_supply ab8500_vaux1_consumers[] = {
> + { .dev = NULL, .supply = "vaux1", },
> +};
All these supplies with NULL devices are bogus, supplies are in terms of
the device being supplied not the labels on the board. If you've got a
supply with no device and the name of the supply on either the regulator
or the board you're most likely doing it wrong. The only exception is
for supplies used in cpufreq since we don't have a struct device we can
use there.
> +struct regulator_init_data ab8500_vaux2_regulator = {
> + .supply_regulator_dev = NULL,
> + .constraints = {
> + .name = "ab8500-vaux2",
> + .min_uV = AB8500_VAUXN_LDO_MIN_VOLTAGE,
> + .max_uV = AB8500_VAUXN_LDO_MAX_VOLTAGE,
I'm not convinced that these #defines help anything, they're used in
exactly one place so don't add much to either legibility or ease of
maintinance.
prev parent reply other threads:[~2010-07-13 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 6:21 [PATCH 0/3] ab8500-mfd: add regulator support Sundar Iyer
2010-07-13 6:21 ` [PATCH 1/3] ab8500-mfd: add regulator support to ab8500 mfd device Sundar Iyer
2010-07-13 9:49 ` Mark Brown
2010-07-14 10:13 ` Samuel Ortiz
2010-07-15 10:29 ` Liam Girdwood
2010-07-13 6:21 ` [PATCH 2/3] regulator: add support for regulators on the ab8500 MFD Sundar Iyer
2010-07-13 9:55 ` Mark Brown
2010-07-13 6:21 ` [PATCH 3/3] ux500: add ab8500-regulators machine specific data Sundar Iyer
2010-07-13 10:00 ` 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=20100713100012.GC12686@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=bengt.g.jonsson@stericsson.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--cc=sundar.iyer@stericsson.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