From: Rhyland Klein <rklein@nvidia.com>
To: Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Rhyland Klein <rklein@nvidia.com>
Subject: [PATCH 1/4] regulator: tps65910: update type for regmap
Date: Tue, 17 Apr 2012 18:00:26 -0700 [thread overview]
Message-ID: <1334710829-22777-2-git-send-email-rklein@nvidia.com> (raw)
In-Reply-To: <1334710829-22777-1-git-send-email-rklein@nvidia.com>
When accessing the regmap via the read/write functions, we need to use a
unsigned int * instead of a u8 * otherwise corruption will occur.
Signed-off-by: Rhyland Klein <rklein@nvidia.com>
---
drivers/regulator/tps65910-regulator.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/regulator/tps65910-regulator.c b/drivers/regulator/tps65910-regulator.c
index 747bf57..9fd0fe1 100644
--- a/drivers/regulator/tps65910-regulator.c
+++ b/drivers/regulator/tps65910-regulator.c
@@ -331,7 +331,7 @@ struct tps65910_reg {
static inline int tps65910_read(struct tps65910_reg *pmic, u8 reg)
{
- u8 val;
+ unsigned int val;
int err;
err = pmic->mfd->read(pmic->mfd, reg, 1, &val);
--
1.7.0.4
next prev parent reply other threads:[~2012-04-18 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 1:00 [PATCH 0/4] Update TPS65910 to boot using devicetree Rhyland Klein
2012-04-18 1:00 ` Rhyland Klein [this message]
[not found] ` <1334710829-22777-2-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-04-18 9:25 ` [PATCH 1/4] regulator: tps65910: update type for regmap Mark Brown
[not found] ` <20120418092547.GE3021-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-04-18 20:03 ` Rhyland Klein
2012-04-18 20:19 ` Rhyland Klein
2012-04-19 12:54 ` Mark Brown
2012-04-18 1:00 ` [PATCH 2/4] regulator: tps65910: Add device tree bindings Rhyland Klein
[not found] ` <1334710829-22777-3-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-04-18 8:35 ` Mark Brown
2012-04-18 1:00 ` [PATCH 3/4] mfd: tps65910: Add device-tree support Rhyland Klein
[not found] ` <1334710829-22777-4-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-04-18 9:01 ` Mark Brown
[not found] ` <20120418090133.GC3021-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-04-18 19:35 ` Rhyland Klein
2012-04-19 12:50 ` Mark Brown
[not found] ` <20120419125041.GH3046-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-04-19 15:35 ` Stephen Warren
[not found] ` <4F9030D5.2050601-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-19 16:34 ` Mark Brown
[not found] ` <1334710829-22777-1-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-04-18 1:00 ` [PATCH 4/4] ARM: Tegra: Add support for TPS65910 PMIC Rhyland Klein
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=1334710829-22777-2-git-send-email-rklein@nvidia.com \
--to=rklein@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).