From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Myungjoo Ham <myungjoo.ham@samsung.com>,
Ben Dooks <ben-linux@fluff.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 3/3] ARM: S5PV210: Add voltage consumer of WM8994 to the regulator framework
Date: Fri, 1 Oct 2010 06:31:39 +0100 [thread overview]
Message-ID: <20101001053139.GE30949@sirena.org.uk> (raw)
In-Reply-To: <4CA5623D.3000002@samsung.com>
On Fri, Oct 01, 2010 at 01:23:25PM +0900, Chanwoo Choi wrote:
> Additionally, I explain the constraints of the regulator of WM8994 codec.
> All these consumer supply of WM8994 codec connected the regulator(VCC_1.8V)
> on a circuit diagram. "VCC_1.8V" regulator is always enabled, because it is
> used to many devices on Goni/Aquila board. This is required especially
It would be nicer to connect this to the regulator on the PMIC (I'm
assuming there is one), even if it is always enabled. That said, is the
PMIC on these boards supported by Linux yet?
> when there are many devices physically attached to "VCC_1.8V" and some of
> they did not "register" as consumers to "VCC_1.8V". "VCC_1.8V" might be
> turned off by those who are registered while "unregistered" are still active
You can set the always_on flag in the regulator constraints to prevent
this happening - if that flag is set the supply will be kept active even
if all consumers are disabled.
next prev parent reply other threads:[~2010-10-01 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 4:23 [PATCH 3/3] ARM: S5PV210: Add voltage consumer of WM8994 to the regulator framework Chanwoo Choi
2010-10-01 5:31 ` Mark Brown [this message]
2010-10-01 5:40 ` Kyungmin Park
2010-10-01 7:24 ` Mark Brown
2010-10-01 8:25 ` Kyungmin Park
2010-10-01 18:27 ` Mark Brown
2010-10-04 12:50 ` Chanwoo Choi
2010-10-04 15:17 ` Mark Brown
2010-10-14 0:37 ` Kukjin Kim
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=20101001053139.GE30949@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ben-linux@fluff.org \
--cc=cw00.choi@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=myungjoo.ham@samsung.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