From: Sascha Hauer <s.hauer@pengutronix.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Handle probe deferral from DT when resolving supplies
Date: Thu, 1 Oct 2015 07:51:57 +0200 [thread overview]
Message-ID: <20151001055157.GF7858@pengutronix.de> (raw)
In-Reply-To: <1443641452-21824-1-git-send-email-broonie@kernel.org>
On Wed, Sep 30, 2015 at 08:30:52PM +0100, Mark Brown wrote:
> When resolving regulator-regulator supplies we ignore probe deferral
> returns from regulator_dev_lookup() (such as are generated for DT when
> we can see a supply is registered) and just fall back to the dummy
> regulator if there are full constraints (as is the case for DT). This
> means that probe deferral is broken for DT systems, fix that by paying
> attention to -EPROBE_DEFER return codes like we do -ENODEV.
>
> A further patch will simplify this further, this is a minimal fix for
> the specific issue.
>
> Reported-by: Sascha Hauer <s.hauer@pengutronix.de>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>
> Tested with my famous "I need to leave the house right now so haven't
> even tried building this yet" test plan - please let me know how this
> works for you.
Yes, this works as expected.
Tested-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2015-10-01 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 19:30 [PATCH] regulator: core: Handle probe deferral from DT when resolving supplies Mark Brown
2015-10-01 5:51 ` Sascha Hauer [this message]
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=20151001055157.GF7858@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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).