archive mirror
 help / color / mirror / Atom feed
From: Marek Szyprowski <>
	Mark Brown <>,
	Dmitry Osipenko <>
Cc: Marek Szyprowski <>,
	Liam Girdwood <>,
	Lucas Stach <>,
	Bartlomiej Zolnierkiewicz <>,
	Krzysztof Kozlowski <>,
	Viresh Kumar <>,, Nishanth Menon <>,
	Stephen Boyd <>,
	Vincent Guittot <>,
	Rafael Wysocki <>,,
	Chanwoo Choi <>
Subject: [PATCH] regulator: do not balance regulators without constraints
Date: Thu, 28 May 2020 15:11:30 +0200	[thread overview]
Message-ID: <> (raw)

Balancing coupled regulators must wait until the clients for all of the
coupled regualtors set their constraints, otherwise the balancing code
might change the voltage of the not-yet-constrained regulator to the
value below the bootloader-configured operation point, what might cause a
system crash.

Signed-off-by: Marek Szyprowski <>

This is probably a generalization of the issue aleady observed and
reported here:

The problem is with "vdd_int" regulator coupled with "vdd_arm" on Odroid
XU3/XU4 boards family. "vdd_arm" is handled by CPUfreq. "vdd_int" is
handled by devfreq. CPUfreq initialized quite early during boot and it
starts changing OPPs and "vdd_arm" value. Sometimes CPU activity during
boot goes down and some low-frequency OPPs are selected, what in turn
causes lowering "vdd_arm". This happens before devfreq applies its
requirements on "vdd_int". Regulator balancing code reduces "vdd_arm"
voltage value, what in turn causes lowering "vdd_int" value to the lowest
possible value. This is much below the operation point of the wcore bus,
which still runs at the highest frequency.

The issue was hard to notice because in the most cases the board managed
to boot properly, even when the regulator was set to lowest value allowed
by the regulator constraints. However, it caused some random issues,
which can be observed as "Unhandled prefetch abort" or low USB stability.

I know that adding more and more special cases to the generic code is not
the best idea, but so far I see no other way to fix this issue. The only
other solution that comes to my mind is admiting that it is not possible
to have generic regulator coupler and this needs board-specific code in
all cases. Such code might take care of those corner cases if they are

Best regards,
Marek Szyprowski
 drivers/regulator/core.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 941783a14b45..c1d77d44186b 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -3697,10 +3697,21 @@ static int regulator_balance_voltage(struct regulator_dev *rdev,
 			 * the coupled voltages.
 			int optimal_uV = 0, optimal_max_uV = 0, current_uV = 0;
+			int cons_uV = 0, cons_max_uV = INT_MAX;
 			if (test_bit(i, &c_rdev_done))
+			ret = regulator_check_consumers(c_rdevs[i],
+						&cons_uV,
+						&cons_max_uV, state);
+			if (ret < 0)
+				goto out;
+			/* no constraints set - ignore */
+			if (cons_uV == 0)
+				continue;
 			ret = regulator_get_optimal_voltage(c_rdevs[i],

       reply	other threads:[~2020-05-28 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-05-28 13:11 ` Marek Szyprowski [this message]
2020-05-28 13:43   ` [PATCH] regulator: do not balance regulators without constraints Mark Brown
2020-05-29  5:45     ` Marek Szyprowski
2020-05-29 11:10       ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).