From: Laxman Dewangan <ldewangan@nvidia.com>
To: broonie@opensource.wolfsonmicro.com, gregkh@linuxfoundation.org,
lrg@ti.com, linux-kernel@vger.kernel.org
Cc: Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V1 0/4] regulator: tps62360: add cache support and settling time.
Date: Mon, 7 May 2012 13:05:35 +0530 [thread overview]
Message-ID: <1336376139-1048-1-git-send-email-ldewangan@nvidia.com> (raw)
This patch series is for improving the regulator tps62360 by enabling
caching, using efficient functions for reducing code size and provide
settling time.
Laxman Dewangan (4):
regmap: add function for set/clear bits
This add the regmap_set_bits()/regmap_clear_bits() functionlity.
regulator: tps62360: enable register cache
Enable the caching of register to have faster update_bits as it
will avoid one more i2c read every time.
regulator: tps62360: use efficient function
This reduces code size and have better readability in the code.
regulator: tps62360: Provide settling time for voltage change
This will provide settlling delay when voltage output changes.
drivers/base/regmap/regmap.c | 32 ++++++++++
drivers/regulator/tps62360-regulator.c | 106 +++++++++++++++++++-------------
include/linux/regmap.h | 15 +++++
3 files changed, 110 insertions(+), 43 deletions(-)
next reply other threads:[~2012-05-07 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 7:35 Laxman Dewangan [this message]
2012-05-07 7:35 ` [PATCH V1 1/4] regmap: add function for set/clear bits Laxman Dewangan
2012-05-07 10:55 ` Mark Brown
2012-05-07 7:35 ` [PATCH V1 2/4] regulator: tps62360: enable register cache Laxman Dewangan
2012-05-07 11:13 ` Mark Brown
2012-05-07 7:35 ` [PATCH V1 3/4] regulator: tps62360: use efficient function Laxman Dewangan
2012-05-07 7:35 ` [PATCH V1 4/4] regulator: tps62360: Provide settling time for voltage change Laxman Dewangan
2012-05-07 11:23 ` Mark Brown
2012-05-07 12:42 ` Laxman Dewangan
2012-05-07 14:22 ` Mark Brown
2012-05-07 14:45 ` Laxman Dewangan
2012-05-07 14:51 ` Mark Brown
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=1336376139-1048-1-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@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
all inboxes | Powered by JetHome®