All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: falcon@meizu.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] async: async device driver probing
Date: Sat, 8 Feb 2014 10:27:29 -0800	[thread overview]
Message-ID: <20140208182729.GB10892@kroah.com> (raw)
In-Reply-To: <1391857539-27782-1-git-send-email-falcon@meizu.com>

On Sat, Feb 08, 2014 at 07:05:38PM +0800, falcon@meizu.com wrote:
> From: Wu Zhangjin <wuzhangjin@gmail.com>
> 
> [*Note*: NOT applicable, only for comments.]
> 
> To async the slow driver probing function of some devices, the device probing
> support is modified to support async scheduling.
> 
> In order to async your driver probing function, please mask the async_probe
> flag to 1, and to make sure one asynced probing is executed before an specified
> point, please call async_synchronize_full() in that point..
> 
> Usage:
> 
> 	static struct i2c_driver test_driver = {
> 		.driver = {
> 			.name   = TEST_DEV_NAME,
> 			.owner  = THIS_MODULE,
> 	+               .async_probe = 1,
> 		},

Why is this needed, we have defered probing and the container stuff, so
what problem is this solving?

greg k-h

  parent reply	other threads:[~2014-02-08 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 11:05 [PATCH 1/2] async: async device driver probing falcon
2014-02-08 11:05 ` [PATCH 2/2] async: Allow to group the asynced device probings falcon
2014-02-08 18:28   ` Greg KH
2014-02-08 18:27 ` Greg KH [this message]
2014-08-13 17:20   ` [PATCH 1/2] async: async device driver probing Dmitry Torokhov
2014-08-13 22:02     ` Greg KH
2014-08-13 22:10       ` Dmitry Torokhov
2014-08-14  4:18         ` Greg KH
     [not found] <uovsqced4yboii55ncyjppla.1391933910239@email.android.com>
2014-02-13 23:59 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140208182729.GB10892@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=falcon@meizu.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.