From: Hans de Goede <hdegoede@redhat.com>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: [PATCH v2 3/3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot
Date: Wed, 27 Apr 2016 15:59:28 +0200 [thread overview]
Message-ID: <1461765568-15828-4-git-send-email-hdegoede@redhat.com> (raw)
In-Reply-To: <1461765568-15828-1-git-send-email-hdegoede@redhat.com>
The maximum supported voltage for ldo_io# is 3.3V, but on cold
boot the selector comes up at 0x1f, which maps to 3.8V.
This causes _regulator_get_voltage() to fail with -EINVAL which
causes regulator registration to fail when constrains are used:
[ 1.467788] vcc-touchscreen: failed to get the current voltage(-22)
[ 1.474209] axp20x-regulator axp20x-regulator: Failed to register ldo_io1
[ 1.483363] axp20x-regulator: probe of axp20x-regulator failed with error -22
This commits makes axp20x_probe fix-up the selector values in
the chip before registering regulators avoiding the above errors.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
drivers/regulator/axp20x-regulator.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/drivers/regulator/axp20x-regulator.c b/drivers/regulator/axp20x-regulator.c
index 89f6842..5ddaa82 100644
--- a/drivers/regulator/axp20x-regulator.c
+++ b/drivers/regulator/axp20x-regulator.c
@@ -347,6 +347,7 @@ static int axp20x_regulator_probe(struct platform_device *pdev)
.driver_data = axp20x,
};
int ret, i, nregulators;
+ unsigned int reg, sel;
u32 workmode;
const char *axp22x_dc1_name = axp22x_regulators[AXP22X_DCDC1].name;
const char *axp22x_dc5_name = axp22x_regulators[AXP22X_DCDC5].name;
@@ -361,6 +362,24 @@ static int axp20x_regulator_probe(struct platform_device *pdev)
case AXP223_ID:
regulators = axp22x_regulators;
nregulators = AXP22X_REG_ID_MAX;
+ /*
+ * On cold boot ldo_io# sel is 0x1f which is out of spec,
+ * fix this up here to avoid _regulator_get_voltage returning
+ * -EINVAL when applying constraints.
+ */
+ for (reg = AXP22X_LDO_IO0_V_OUT;
+ reg <= AXP22X_LDO_IO1_V_OUT; reg += 2) {
+ ret = regmap_read(axp20x->regmap, reg, &sel);
+ if (ret)
+ return ret;
+ sel &= 0x1f;
+ if (sel > 0x1a) {
+ ret = regmap_update_bits(axp20x->regmap, reg,
+ 0x1f, 0x1a);
+ if (ret)
+ return ret;
+ }
+ }
break;
default:
dev_err(&pdev->dev, "Unsupported AXP variant: %ld\n",
--
2.7.4
next prev parent reply other threads:[~2016-04-27 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 13:59 [PATCH v2 resend 0/3] regulator: axp20x: 3 bugfixes Hans de Goede
2016-04-27 13:59 ` [PATCH v2 1/3] regulator: axp20x: Fix axp209 ldo4 ranges Hans de Goede
2016-04-27 13:59 ` [PATCH v2 2/3] regulator: axp20x: Fix axp22x ldo_io voltage ranges Hans de Goede
2016-04-27 16:35 ` Applied "regulator: axp20x: Fix axp22x ldo_io voltage ranges" to the regulator tree Mark Brown
2016-04-27 16:35 ` Mark Brown
2016-04-27 13:59 ` Hans de Goede [this message]
2016-04-27 15:12 ` [PATCH v2 3/3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot Mark Brown
2016-04-27 15:35 ` Hans de Goede
2016-04-27 15:48 ` Mark Brown
2016-04-27 16:04 ` Hans de Goede
2016-04-27 16:30 ` Mark Brown
2016-04-27 18:35 ` Hans de Goede
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=1461765568-15828-4-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.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).