public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Mahaveer, Vishal" <vishalm@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] OMAP: TWL: set clk32kg regulator on
Date: Mon, 07 Nov 2011 11:26:18 -0800	[thread overview]
Message-ID: <871utju42t.fsf@ti.com> (raw)
In-Reply-To: <59CD7F2B651AD44A9EFE2AFA6166395D083879@DFLE34.ent.ti.com> (Vishal Mahaveer's message of "Fri, 4 Nov 2011 23:20:49 +0000")

"Mahaveer, Vishal" <vishalm@ti.com> writes:

>>> omap4_clk32kg regulator is used by connectivity (WLAN/BT/GPS) chip on
>>> omap4 platforms.
>>> Set always_on flag to true for connectivity chip to operate.
>>
>> The driver/init for the connectivity chip should be using the regulator
>> API to enable/disable the regulator as needed.
>
> The connectivity chip is used for BT, WLAN, FM and GPS. So we want it
> on at all times.

No.

You want it on only

1) if the connectivity chip is present, *and*
2) BT, WLAN, FM or GPS are being used.

The current patch assumes that a connectivity chip is present whenever
the TWL is present, which may be true on the platform you're currently
working on, but is not true in general.

And, even if it were present, for power reasons the regulator should be
enabled only when it's needed, not because it might be needed.  That
means that the device-specific (or board specific) code should be
configuring the regulators used for the various modules so the drivers
can request the regulators when they're needed.

Kevin

  reply	other threads:[~2011-11-07 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 15:40 [PATCH 0/1] OMAP: TWL: set clk32kg regulator on Vishal Mahaveer
2011-11-01 15:40 ` [PATCH 1/1] " Vishal Mahaveer
2011-11-04 23:16   ` Kevin Hilman
2011-11-04 23:20     ` Mahaveer, Vishal
2011-11-07 19:26       ` Kevin Hilman [this message]
2011-11-07 21:03         ` Mahaveer, Vishal
2011-11-07 22:49           ` Kevin Hilman
2011-11-08 14:57             ` Mahaveer, Vishal

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=871utju42t.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishalm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox