On Sat, Feb 08, 2014 at 07:05:39PM +0800, fal...@meizu.com wrote:
> From: Wu Zhangjin <fal...@meizu.com>
>
> [*Note*: NOT applicable, only for comments.]
>
> This allows to schedule a group of probings in order.
>
> Usage:
>
> If the probing of driver2 depends on the probing of driver1, we can put them
> into a group, here put them into a group named domain 1, they will be probed
> in
> the linking order.
>
> ...
>
> static struct platform_driver first_driver = {
> .probe = first_driver_probe,
> .driver = {
> .name = "first driver",
> + .async_probe = 1,
> + .async_domain = 1,
> },
> };
>
> ...
>
> static struct platform_driver second_driver = {
> .probe = second_driver_probe,
> .driver = {
> .name = "second_driver",
> + .async_probe = 1,
> + .async_domain = 1,
> },
> };
>
> ...
>
> With this feature, it is possible to async different class of drivers, for
> example, put all sound drivers into domain 2, put all display/video drivers
> into domain 3, and sensors domain 4, network drivers domain 5 and so forth.
That sounds like a recipie for massive confusion.
Again, what problem is this trying to solve?
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
