From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] regulator: axp20x: resolve self dependency issue
Date: Mon, 26 May 2014 16:43:56 +0100 [thread overview]
Message-ID: <20140526154356.GZ22111@sirena.org.uk> (raw)
In-Reply-To: <1401116292-24066-6-git-send-email-boris.brezillon@free-electrons.com>
On Mon, May 26, 2014 at 04:58:12PM +0200, Boris BREZILLON wrote:
> Some regulators might take their power supply from other regulators defined
> by the same PMIC.
>
> Retry regulators registration until all regulators are registered or the
> last iteration didn't manage to register any new regulator (which means
> there's an external dependency missing and we can thus return
> EPROBE_DEFER).
This is going to apply to most PMICs - we should factor this out into
the core rather than implementing it individual drivers. It works
normally because typically the dependency is from DCDCs to LDOs and so
with common naming schemes alphabetic sorting saves us.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140526/de651b6f/attachment.sig>
next prev parent reply other threads:[~2014-05-26 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 14:58 [PATCH v2 0/5] mfd: axp20x: add AXP221 PMIC support Boris BREZILLON
2014-05-26 14:58 ` [PATCH v2 1/5] " Boris BREZILLON
2014-05-26 15:29 ` Boris BREZILLON
2014-05-26 14:58 ` [PATCH v2 2/5] regulator: axp20x: prepare support for multiple AXP chip families Boris BREZILLON
2014-05-26 14:58 ` [PATCH v2 3/5] regulator: axp20x: add support for AXP221 regulators Boris BREZILLON
2014-05-26 14:58 ` [PATCH v2 4/5] regulator: axp20x: reset probe data before each probe Boris BREZILLON
2014-05-26 14:58 ` [PATCH v2 5/5] regulator: axp20x: resolve self dependency issue Boris BREZILLON
2014-05-26 15:43 ` Mark Brown [this message]
2014-05-26 16:58 ` Boris BREZILLON
2014-05-26 18:17 ` 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=20140526154356.GZ22111@sirena.org.uk \
--to=broonie@kernel.org \
--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