From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix amba_get_enable_vcore()'s handling of probe deferral
Date: Tue, 10 Apr 2012 11:13:13 +0200 [thread overview]
Message-ID: <20120410091313.GA14117@glitch> (raw)
In-Reply-To: <20120410090928.GB24465@sirena.org.uk>
On Tue, Apr 10, 2012 at 10:09:28AM +0100, Mark Brown wrote:
> On Tue, Apr 10, 2012 at 10:48:33AM +0200, Domenico Andreoli wrote:
> > From: Domenico Andreoli <domenico.andreoli@linux.com>
>
> > With v3.4-rc1 my board's console started to have problems. earlyprintk
> > revealed that the PL011 serial driver deferred the initialization and
> > never attempted it again. This resulted in console not being bound to
> > any physical device.
>
> > The error in probing the serial was due to amba_get_enable_vcore()
> > not ignoring the -EPROBE_DEFER got from regulator_get(), which has
> > been recently updated to ask for probe deferral in case the regulator
> > is not available (yet).
>
> > This fix makes amba_get_enable_vcore() consistently handle the new
> > -EPROBE_DEFER error case.
>
> As discussed in the other thread where Shawn proposed the same fix this
> is not a good fix (and the original code is not a good idea either), it
> makes things very dependant on probe ordering which is fragile and prone
> to error. With the code as-is platforms not using this feature really
> should be stubbing out the regulator rather than ignoring failures to
> acquire the regulator.
>
> Russell just applied a patch removing this feature entirely (in favour
> of implementing it in power domains on platforms that want it) which
> avoids these issues.
Yes, I should have spent few minutes reading the ml instead of digging
for a night into the code - but my board had also other issues ;)
thanks,
Domenico
prev parent reply other threads:[~2012-04-10 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 8:48 [PATCH] ARM: fix amba_get_enable_vcore()'s handling of probe deferral Domenico Andreoli
2012-04-10 9:09 ` Mark Brown
2012-04-10 9:13 ` Domenico Andreoli [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=20120410091313.GA14117@glitch \
--to=cavokz@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).