From: "André Draszik" <andre.draszik@linaro.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Jon Hunter <jonathanh@nvidia.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Will McVicker" <willmcvicker@google.com>,
"Juan Yescas" <jyescas@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>
Subject: [PATCH v2 0/8] regulator: core: allow regulator_register() with missing required supply
Date: Fri, 09 Jan 2026 08:38:36 +0000 [thread overview]
Message-ID: <20260109-regulators-defer-v2-0-1a25dc968e60@linaro.org> (raw)
Hi,
With these attached patches it becomes possible again to support
hardware designs with multiple PMICs where individual rails of each act
as required supplies for rails of the other (due to the latter being
e.g. always-on), and vice-versa.
Google Pixel 6 and 6 Pro (oriole and raven) are examples of such
designs.
Rather than returning -EPORBE_DEFER in regulator_register() when
set_machine_constraints() fails with -EPROBE_DEFER (due to missing
required supplies), we still allow rail registration and try to
reresolve supplies each time a new rail gets registered.
This is implemented using a bus (regulator bus), which allows the core
to reresolve supplies for regulators that still need them whenever new
regulators (i.e. devices) are added.
Using a bus also solves existing problems around late resolution of
supplies as mentioned in the commit message introducing that bus.
The series starts with a few bug fixes and the last two commits
implement the changes mentioned above, but do depend on the bug fixes.
Cheers,
Andre'
Signed-off-by: André Draszik <andre.draszik@linaro.org>
---
Changes in v2:
- drop fixes tag from patch 5
- Link to v1: https://lore.kernel.org/r/20251227-regulators-defer-v1-0-3104b22d84cb@linaro.org
---
André Draszik (8):
regulator: core: update two debug messages
regulator: core: fix locking in regulator_resolve_supply() error path
regulator: core: move supply check earlier in set_machine_constraints()
regulator: core: streamline supply resolution for always-on/boot-on regulators
regulator: core: remove dead code in regulator_resolve_supply()
regulator: core: don't ignore errors from event forwarding setup
regulator: core: reresolve unresolved supplies when available
regulator: core: don't fail regulator_register() with missing required supply
drivers/regulator/core.c | 351 ++++++++++++++++++++++++++++-----------
include/linux/regulator/driver.h | 2 +
2 files changed, 254 insertions(+), 99 deletions(-)
---
base-commit: f8f97927abf7c12382dddc93a144fc9df7919b77
change-id: 20251224-regulators-defer-f5ffa668a3f6
Best regards,
--
André Draszik <andre.draszik@linaro.org>
next reply other threads:[~2026-01-09 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 8:38 André Draszik [this message]
2026-01-09 8:38 ` [PATCH v2 1/8] regulator: core: update two debug messages André Draszik
2026-01-09 8:38 ` [PATCH v2 2/8] regulator: core: fix locking in regulator_resolve_supply() error path André Draszik
2026-01-09 8:38 ` [PATCH v2 3/8] regulator: core: move supply check earlier in set_machine_constraints() André Draszik
2026-01-09 8:38 ` [PATCH v2 4/8] regulator: core: streamline supply resolution for always-on/boot-on regulators André Draszik
2026-01-09 8:38 ` [PATCH v2 5/8] regulator: core: remove dead code in regulator_resolve_supply() André Draszik
2026-01-09 8:38 ` [PATCH v2 6/8] regulator: core: don't ignore errors from event forwarding setup André Draszik
2026-01-09 8:38 ` [PATCH v2 7/8] regulator: core: reresolve unresolved supplies when available André Draszik
2026-01-09 8:38 ` [PATCH v2 8/8] regulator: core: don't fail regulator_register() with missing required supply André Draszik
2026-01-12 14:31 ` [PATCH v2 0/8] regulator: core: allow " 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=20260109-regulators-defer-v2-0-1a25dc968e60@linaro.org \
--to=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=javier@osg.samsung.com \
--cc=jonathanh@nvidia.com \
--cc=jyescas@google.com \
--cc=kernel-team@android.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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
all inboxes | Powered by JetHome®