lkml.org 
[lkml]   [2014]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2/2] async: Allow to group the asynced device probings
On Sat, Feb 08, 2014 at 07:05:39PM +0800, falcon@meizu.com wrote:
> From: Wu Zhangjin <falcon@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


\
 
 \ /
  Last update: 2014-02-08 20:01    [W:0.125 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site