On 29/08/2018 17:44, Chris Brandt wrote: > On Wednesday, August 29, 2018 1, Daniel Lezcano wrote: >> Can the boot constraints [1] solve this issue instead of the changes you >> are proposing ? >> >> [1] https://lwn.net/Articles/747250/ > > Thanks for the suggestion, but... > > I grepped for "boot_constraint" and it shows up nowhere in the current > kernel. > > Also, this article was written Feb 16, 2018, and I can see that the > patch series was still being submitted (V7) as of Feb 23, 2018. Ah ok, fair enough, I thought it was merged. In any case, after thinking about it, it wouldn't have helped. My concern is if we can avoid changing the TIMER_OF_DECLARE because of the boot order, it would be better. Can returning EPROBE_DEFER fix this issue? Or use the 'complex dependencies' [1]? I'm pretty busy ATM, so I can not investigate now if the suggestions above are fine or just stupid. I will have a look as soon as I can. -- Daniel [1] https://www.kernel.org/doc/html/v4.15/driver-api/device_link.html -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
