From: rask@formelder.dk (Rask Ingemann Lambertsen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: axp20x: AXP806: Fix dcdcb being set instead of dcdce
Date: Sat, 21 Jan 2017 17:11:43 +0100 [thread overview]
Message-ID: <20170121161142.g4zslhohb6vvcvwd@localhost> (raw)
A typo or copy-paste bug means that the register access intended for
regulator dcdce goes to dcdcb instead. This patch corrects it.
Signed-off-by: Rask Ingemann Lambertsen <rask@formelder.dk>
Fixes: 2ca342d391e3 (regulator: axp20x: Support AXP806 variant)
---
I have a board where dcdcb powers the DRAM, which I found running at 2.05 V
rather than 1.50 V. The bug was introduced nearly five months ago. Thanks
must go to Samsung for making DRAM chips which tolerate that sort of abuse.
drivers/regulator/axp20x-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/axp20x-regulator.c b/drivers/regulator/axp20x-regulator.c
index e6a512e..a3ade9e 100644
--- a/drivers/regulator/axp20x-regulator.c
+++ b/drivers/regulator/axp20x-regulator.c
@@ -272,7 +272,7 @@ static const struct regulator_desc axp806_regulators[] = {
64, AXP806_DCDCD_V_CTRL, 0x3f, AXP806_PWR_OUT_CTRL1,
BIT(3)),
AXP_DESC(AXP806, DCDCE, "dcdce", "vine", 1100, 3400, 100,
- AXP806_DCDCB_V_CTRL, 0x1f, AXP806_PWR_OUT_CTRL1, BIT(4)),
+ AXP806_DCDCE_V_CTRL, 0x1f, AXP806_PWR_OUT_CTRL1, BIT(4)),
AXP_DESC(AXP806, ALDO1, "aldo1", "aldoin", 700, 3300, 100,
AXP806_ALDO1_V_CTRL, 0x1f, AXP806_PWR_OUT_CTRL1, BIT(5)),
AXP_DESC(AXP806, ALDO2, "aldo2", "aldoin", 700, 3400, 100,
--
2.10.2
--
Rask Ingemann Lambertsen
next reply other threads:[~2017-01-21 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 16:11 Rask Ingemann Lambertsen [this message]
2017-01-23 8:04 ` [PATCH] regulator: axp20x: AXP806: Fix dcdcb being set instead of dcdce Chen-Yu Tsai
2017-01-24 18:39 ` Applied "regulator: axp20x: AXP806: Fix dcdcb being set instead of dcdce" to the regulator tree 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=20170121161142.g4zslhohb6vvcvwd@localhost \
--to=rask@formelder.dk \
--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).