From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 7/7] MFD: TWL6040: Add regulator support for VIO, V2V1 supplies
Date: Mon, 20 Feb 2012 20:55:54 +0100 [thread overview]
Message-ID: <20120220195554.GQ5387@sortiz-mobl> (raw)
In-Reply-To: <1328619678-26080-8-git-send-email-peter.ujfalusi@ti.com>
Hi Peter,
On Tue, Feb 07, 2012 at 03:01:18PM +0200, Peter Ujfalusi wrote:
> twl6040 has three power supply source:
> VBAT needs to be connected to VBAT, VIO, and V2V1.
> Add regulator support for the VIO, V2V1 supplies.
> Initially handle the two supply together with bulk commands.
I applied this one.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-02-20 19:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 13:01 [PATCH v2 0/7] MFD: twl6040: Conversion to i2c driver Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 1/7] MFD: twl-core: Detach twl6040 from the pmic mfd driver Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 2/7] MFD: twl6040: Convert to i2c driver, and separate it from twl core Peter Ujfalusi
2012-02-07 13:29 ` Mark Brown
2012-02-07 13:39 ` Peter Ujfalusi
2012-02-07 13:43 ` Mark Brown
2012-02-07 13:52 ` Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 3/7] ASoC: twl6040: Remove dependency on twl4030 from Kconfig Peter Ujfalusi
2012-02-07 13:37 ` Mark Brown
2012-02-07 13:01 ` [PATCH v2 4/7] OMAP: 4430sdp: Correct fixed regulator device ID Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 5/7] OMAP: sdp4430: Add fixed regulator for twl6040 needs Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 6/7] OMAP: omap4panda: " Peter Ujfalusi
2012-02-07 13:01 ` [PATCH v2 7/7] MFD: TWL6040: Add regulator support for VIO, V2V1 supplies Peter Ujfalusi
2012-02-07 13:16 ` Mark Brown
2012-02-07 13:30 ` Peter Ujfalusi
2012-02-20 19:55 ` Samuel Ortiz [this message]
2012-02-09 7:47 ` [PATCH v2 0/7] MFD: twl6040: Conversion to i2c driver 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=20120220195554.GQ5387@sortiz-mobl \
--to=sameo@linux.intel.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).