[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <7ede83e8d78414d8618e1044fd8fd11e8ed7a09f.1604544767.git.mirq-linux@rere.qmqm.pl>
Date: Thu, 05 Nov 2020 03:54:07 +0100
From: Michał Mirosław <mirq-linux@...e.qmqm.pl>
To: Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: Corentin Labbe <clabbe.montjoie@...il.com>, lgirdwood@...il.com,
mripard@...nel.org, linux-kernel@...r.kernel.org, wens@...e.org,
broonie@...nel.org, linux-arm-kernel@...ts.infradead.org,
<linux-stm32@...md-mailman.stormreply.com>,
Pengutronix Kernel Team <kernel@...gutronix.de>
Subject: [PATCH] regulator: debug early supply resolving
Help debugging the case when set_machine_constraints() needs to be
repeated.
Signed-off-by: Michał Mirosław <mirq-linux@...e.qmqm.pl>
---
drivers/regulator/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 402a72a70eb1..c84e3b0b63de 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -5271,6 +5271,8 @@ regulator_register(const struct regulator_desc *regulator_desc,
/* FIXME: this currently triggers a chicken-and-egg problem
* when creating -SUPPLY symlink in sysfs to a regulator
* that is just being created */
+ rdev_dbg(rdev, "will resolve supply early: %s\n",
+ rdev->supply_name);
ret = regulator_resolve_supply(rdev);
if (!ret)
ret = set_machine_constraints(rdev);
--
2.20.1
Powered by blists - more mailing lists