public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Kalle Jokiniemi <kalle.jokiniemi@nokia.com>
Cc: tony@atomide.com, sakari.ailus@nokia.com,
	linux-omap@vger.kernel.org, lrg@slimlogic.co.uk,
	broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions
Date: Fri, 29 Apr 2011 17:04:09 +0300	[thread overview]
Message-ID: <20110429170409.5ad8833b.jhnikula@gmail.com> (raw)
In-Reply-To: <1304081264-4915-2-git-send-email-kalle.jokiniemi@nokia.com>

On Fri, 29 Apr 2011 15:47:44 +0300
Kalle Jokiniemi <kalle.jokiniemi@nokia.com> wrote:

> +static struct regulator_init_data rx51_vintana1 = {
> +	.constraints = {
> +		.name			= "VINTANA1",
> +		.min_uV			= 1500000,
> +		.max_uV			= 1500000,
> +		.always_on		= true,
...
> +static struct regulator_init_data rx51_vintdig = {
> +	.constraints = {
> +		.name			= "VINTDIG",
> +		.min_uV			= 1500000,
> +		.max_uV			= 1500000,
> +		.always_on		= true,

Are these two used at all? According to public schematics they are
connected to just one capasitor. Could be some needed filtering/charge
pump capacitors for TWL though.

I was thinking are all of these regulators really always_on? How about
letting those without any known user to be switched off?

> @@ -838,6 +911,8 @@ static int __init rx51_i2c_init(void)
>  	omap_register_i2c_bus(2, 100, rx51_peripherals_i2c_board_info_2,
>  			      ARRAY_SIZE(rx51_peripherals_i2c_board_info_2));
>  	omap_register_i2c_bus(3, 400, NULL, 0);
> +	regulator_has_full_constraints();
> +
>  	return 0;
>  }
>  
Move this somewhere else than in i2c initialization function :-)

-- 
Jarkko

  reply	other threads:[~2011-04-29 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 12:47 [PATCH 0/1] RX-51: add full regulator definitions Kalle Jokiniemi
2011-04-29 12:47 ` [PATCH 1/1] OMAP3: rx-51: Add " Kalle Jokiniemi
2011-04-29 14:04   ` Jarkko Nikula [this message]
2011-05-02  4:42     ` kalle.jokiniemi
2011-05-02  5:19     ` kalle.jokiniemi
2011-05-02  6:57       ` Jarkko Nikula
2011-05-02  8:48         ` kalle.jokiniemi
2011-04-30 19:23   ` Mark Brown
2011-05-02  4:54     ` kalle.jokiniemi

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=20110429170409.5ad8833b.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kalle.jokiniemi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=sakari.ailus@nokia.com \
    --cc=tony@atomide.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