[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD6h2NS_eR7zJjwAuBJPRrCb9=-4r=y-QJt7Lvg5U+yBf-e=kw@mail.gmail.com>
Date: Fri, 15 Feb 2013 00:04:18 +0800
From: Haojian Zhuang <haojian.zhuang@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Grant Likely <grant.likely@...retlab.ca>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
viro@...iv.linux.org.uk, Rusty Russell <rusty@...tcorp.com.au>,
hpa@...ux.intel.com, Jim Cromie <jim.cromie@...il.com>,
linux-kernel@...r.kernel.org,
Russell King - ARM Linux <linux@....linux.org.uk>,
Linus Walleij <linus.walleij@...aro.org>,
broonie@...nsource.wolfsonmicro.com,
Patch Tracking <patches@...aro.org>
Subject: Re: [PATCH] driver core: add wait event for deferred probe
On 14 February 2013 23:57, Arnd Bergmann <arnd@...db.de> 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
Haojian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists