Thread (39 messages) 39 messages, 8 authors, 2015-06-23

Re: [PATCH 00/21] On-demand device registration

From: Linus Walleij <hidden>
Date: 2015-06-11 08:12:32
Also in: linux-devicetree, linux-fbdev, linux-i2c, linux-pm, linux-pwm, linux-samsung-soc, linux-tegra, lkml

On Wed, Jun 10, 2015 at 10:28 AM, Alexander Holler [off-list ref] wrote:
Am 10.06.2015 um 09:30 schrieb Linus Walleij:
quoted
i2c host comes out, probes the regulator driver, regulator driver
probes and then the regulator_get() call returns.

This requires instrumentation on anything providing a resource
to another driver like those I mentioned and a lot of overhead
infrastructure, but I think it's the right approach. However I don't
know if I would ever be able to pull that off myself, I know talk
is cheap and I should show the code instead.
You would end up with the same problem of deadlocks as currently, and you
would still need something ugly like the defered probe brutforce to avoid
them.
Sorry I don't get that. Care to elaborate on why?

Yours,
Linus Walleij
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help