From: Mark Brown <broonie@sirena.org.uk>
To: Manikandan Pillai <mani.pillai@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] Include TPS6235x based Power regulator support
Date: Tue, 13 Jan 2009 21:15:25 +0000 [thread overview]
Message-ID: <20090113211523.GA8670@sirena.org.uk> (raw)
In-Reply-To: <1231832468-7132-1-git-send-email-mani.pillai@ti.com>
On Tue, Jan 13, 2009 at 01:11:08PM +0530, Manikandan Pillai wrote:
> +config REGULATOR_TPS6235X
> + bool "TPS6235X Power regulator for OMAP3EVM"
> + depends on I2C=y
This driver should not be OMAP3EVM specific, I'd expect.
> +extern struct regulator_consumer_supply tps62352_core_consumers;
> +extern struct regulator_consumer_supply tps62352_mpu_consumers;
These should not be required.
> + /* Register the regulators */
> + dev_child = device_find_child(client->adapter->dev.parent,
> + (void *)regulator_consumer_name[id->driver_data],
> + omap_i2c_match_child);
> + rdev = regulator_register(®ulators[id->driver_data],
> + dev_child, client);
I'm not 100% sure what this is intended to do but apart from anything
else it depends on specific consumer names which means that dependency
on the specific board hasn't been removed. This is also OMAP-specific.
You should be using a device which is specific to the regulator as the
device that is being registered.
next prev parent reply other threads:[~2009-01-13 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 7:41 [PATCH 1/2] Include TPS6235x based Power regulator support Manikandan Pillai
2009-01-13 21:15 ` Mark Brown [this message]
2009-01-13 22:07 ` Mark Brown
2009-01-14 10:02 ` Pillai, Manikandan
2009-01-14 11:01 ` Mark Brown
2009-01-14 11:04 ` Pillai, Manikandan
2009-01-14 11:57 ` Mark Brown
2009-01-14 18:21 ` David Brownell
2009-01-14 18:16 ` David Brownell
2009-01-14 0:19 ` David Brownell
2009-01-14 10:39 ` Pillai, Manikandan
2009-01-14 11:48 ` Mark Brown
2009-01-14 17:55 ` David Brownell
2009-01-14 18:10 ` Mark Brown
2009-01-14 18:40 ` David Brownell
[not found] ` <200901201106.00914.david-b@pacbell.net>
2009-01-20 20:28 ` 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=20090113211523.GA8670@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=mani.pillai@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.