regulator-core has_full_constraints set too late for dt using boards ?

Hi,

On 12/11/2013 05:02 PM, Mark Brown wrote:

On Wed, Dec 11, 2013 at 04:43:01PM +0100, Hans de Goede wrote:

quoted

While looking into making regulator_get_optional not print
an error when no regulator is found, I've noticed that
for dt enabled boards, has_full_constraints is not set
until regulator_init_complete() runs, which is a
late_initcall.

quoted

This means that it gets set after it has already been checked
from calls like regulator_get which are likely done by init
functions running earlier.

quoted

This seems wrong ...

Please look at the current code, that's not how this works any more.

More current then 3.13-rc3 ? Because that is what I've been looking at.

I could be completely wrong of course. Either way could you give a few
hints as to how my interpretation of how this works is wrong ?

Thanks & Regards,

Hans