From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] OMAP4: twl-common: Add twl6030 V1V8, V2V1 SMPS common configuration
Date: Wed, 22 Feb 2012 15:02:04 -0800 [thread overview]
Message-ID: <20120222230204.GR18185@atomide.com> (raw)
In-Reply-To: <1328868316-24749-5-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [120210 01:34]:
> V1V8 supply from twl6030 commonly used as VIO for the machine.
> V2V1 is adviced to supply the twl6040, and also to feed the twl6030's
> VCXIO_IN, and VDAC_IN inputs.
> Create the common regulator configurations for these regulators:
> Make the V2V1 as supply_regulator for VCXIO, VDAC.
> Add twl6040 (1-004b) as consumer for V1V8, and V2V1.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2012-02-22 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 10:05 [PATCH 0/7] TWL6040: Regulator support Peter Ujfalusi
2012-02-10 10:05 ` [PATCH 1/7] OMAP: 4430SDP: Correct fixed regulator device ID Peter Ujfalusi
2012-02-22 23:01 ` Tony Lindgren
2012-02-10 10:05 ` [PATCH 2/7] regulator: twl-regulator: Add fixed LDO for V1V8, V2V1 supply Peter Ujfalusi
2012-02-10 11:24 ` Mark Brown
2012-02-10 10:05 ` [PATCH 3/7] MFD: twl-core: regulator configuration for twl6030 V1V8, V2V1 SMPS Peter Ujfalusi
2012-02-23 15:22 ` Samuel Ortiz
2012-02-10 10:05 ` [PATCH 4/7] OMAP4: twl-common: Add twl6030 V1V8, V2V1 SMPS common configuration Peter Ujfalusi
2012-02-22 23:02 ` Tony Lindgren [this message]
2012-02-10 10:05 ` [PATCH 5/7] OMAP: 4430SDP: Use common configuration for V1V8, V2V1 supplies Peter Ujfalusi
2012-02-22 23:02 ` Tony Lindgren
2012-02-10 10:05 ` [PATCH 6/7] OMAP: omap4panda: " Peter Ujfalusi
2012-02-22 23:02 ` Tony Lindgren
2012-02-10 10:05 ` [PATCH 7/7] MFD: TWL6040: Add regulator support for VIO, " Peter Ujfalusi
2012-02-17 11:48 ` [PATCH 0/7] TWL6040: Regulator support Peter Ujfalusi
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=20120222230204.GR18185@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).