• Saravana Kannan's avatar
    driver core: Extend deferred probe timeout on driver registration · 2b28a1a8
    Saravana Kannan authored
    The deferred probe timer that's used for this currently starts at
    late_initcall and runs for driver_deferred_probe_timeout seconds. The
    assumption being that all available drivers would be loaded and
    registered before the timer expires. This means, the
    driver_deferred_probe_timeout has to be pretty large for it to cover the
    worst case. But if we set the default value for it to cover the worst
    case, it would significantly slow down the average case. For this
    reason, the default value is set to 0.
    
    Also, with CONFIG_MODULES=y and the current default values of
    driver_deferred_probe_timeout=0 and fw_devlink=on, devices with missing
    drivers will cause their consumer devices to always defer their probes.
    This is because device links created by fw_devlink defer the probe even
    before the consumer driver's probe() is called.
    
    Instead of a fixed timeout, if we extend an unexpired deferred probe
    timer on every successful driver registration, with the ...
    2b28a1a8
kernel-parameters.txt 233 KB