Re: [PATCH] driver core: add wait event for deferred probe

From: Haojian Zhuang
Date: Thu Feb 14 2013 - 11:04:35 EST

On 14 February 2013 23:57, Arnd Bergmann <arnd@xxxxxxxx> wrote:
> On Thursday 14 February 2013, Haojian Zhuang wrote:
>> If you can change it into code in below, it could work. Otherwise, it
>> always fails.
>> driver_deferred_probe_enable = true;
>> driver_deferred_probe_trigger();
>> + deferred_probe_work_func(NULL);
>> return 0;
>> Because deferred_probe_work_func() depends on that deferred_probe is added
>> into deferred_probe_active_list. If driver_deferred_probe_trigger() isn't called
>> first, the deferred uart probe can't be added into active list. So even you call
>> work_func at here, it doesn't help.
> Would that not cause two instances of the work function to run at the same time?
> That sounds like a source for a lot of problems.
> Arnd

Two instances of the work function? I'm sorry that I don't
understanding your meaning.
Could you help explain your question?

Best Regards
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at