On Mon, May 27, 2013 at 6:52 PM, Ming Lei <ming....@canonical.com> wrote: > On Mon, May 27, 2013 at 8:40 PM, anish singh > <anish198519851...@gmail.com> wrote: >> On Mon, May 27, 2013 at 5:53 PM, Takashi Iwai <ti...@suse.de> wrote: >>> At Mon, 27 May 2013 17:26:22 +0530, >>> anish singh wrote: >>>> >>>> On Mon, May 27, 2013 at 4:00 PM, Ming Lei <ming....@canonical.com> wrote: >>>> > Generally there are only two drivers which don't need uevent to >>>> > handle firmware loading, so don't cache these firmwares during >> Sorry but it confuses me further, > > Please put one blank line before your reply, otherwise it is a bit > difficult to find your reply in email.
sorry. > >> If driver doesn't have information about these firmware then how >> does it cache it? > > Driver only needs firmware's name for caching it, but driver can choose > if it generates uevent to let userspace handle it. Without one uevent, the > user space still can handle the request by waiting for the firmware sysfs > device in advance. But if there is no one user space to handle the request, > the request in kernel won't be completed and there is no timeout for this > case, so will block suspend. Now makes sense.Thanks!! > > > Thanks, > -- > Ming Lei -- 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/