Re: imx8qxp-lpcg-clk: probe of 5a4a0000.clock-controller failed with error -110

[Oliver Graute <oliver.graute@gmail.com>]

On 23/04/20, Aisheng Dong wrote:
> > From: Oliver Graute <oliver.graute@gmail.com>
> > Sent: Tuesday, April 21, 2020 10:24 PM
> > 
> > Hello,
> > 
> > I run into below clock probing issue, after upgrading from next-20200214 to
> > next-20200420. I use the following patches series ontop:
> > > 
> > Some ideas what's the reason for this behavior? or how to fix this?
> > 
> 
> I will check it tomorrow.
> Before that, I need rebase my patch series to last kernel to reproduce this issue.

ok fine, I have some bisect results for you I think this change is
causing the issue.

e2cec7d6853712295cef5377762165a489b2957f is the first bad commit
commit e2cec7d6853712295cef5377762165a489b2957f
Author: John Stultz <john.stultz@linaro.org>
Date:   Tue Feb 25 05:08:24 2020 +0000

    driver core: Set deferred_probe_timeout to a longer default if CONFIG_MODULES is set
    
    When using modules, its common for the modules not to be loaded
    until quite late by userland. With the current code,
    driver_deferred_probe_check_state() will stop returning
    EPROBE_DEFER after late_initcall, which can cause module
    dependency resolution to fail after that.
    
    So allow a longer window of 30 seconds (picked somewhat
    arbitrarily, but influenced by the similar regulator core
    timeout value) in the case where modules are enabled.

 drivers/base/dd.c | 9 +++++++++
 1 file changed, 9 insertions(+)

Best regards,

Oliver