[RFC PATCH 0/9] dt: dependencies (for deterministic driver initialization order based on the DT)
Mark Rutland
mark.rutland at arm.com
Fri Aug 22 06:19:19 PDT 2014
On Thu, Aug 21, 2014 at 08:19:00PM +0100, Alexander Holler wrote:
> Am 21.08.2014 16:02, schrieb Thierry Reding:
>
> > Anyway, those are all fairly standard reasons for where deferred probe
> > triggers, and since I do like deferred probe for it's simplicity and
> > reliability I'd rather not try to work around it if boot time is all
> > that people are concerned about.
>
> It's neither simple nor reliable. It's non deterministic brutforcing
> while making it almost impossible to identify real errors.
It's horrible, yes.
> In my humble opinion the worst way to solve something. I'm pretty sure
> if I would have suggest such a solution, the maintainer crowd would have
> eaten me without cooking.
We didn't have a better workable solution at the time. Having a hack
that got boards booting was considered better than not having them boot.
I don't remember people being particularly enthralled by the idea.
Thanks,
Mark.
More information about the linux-arm-kernel
mailing list