From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752145Ab2GUVOS (ORCPT ); Sat, 21 Jul 2012 17:14:18 -0400 Received: from violet.fr.zoreil.com ([92.243.8.30]:59002 "EHLO violet.fr.zoreil.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754Ab2GUVOR (ORCPT ); Sat, 21 Jul 2012 17:14:17 -0400 Date: Sat, 21 Jul 2012 23:01:06 +0200 From: Francois Romieu To: Ming Lei Cc: Linus Torvalds , Linux Kernel Mailing List , linux-usb , Alan Stern , Greg Kroah-Hartman , Oliver Neukum , "Rafael J. Wysocki" Subject: Re: [RFC] firmware load: defer request_firmware during early boot and resume Message-ID: <20120721210106.GA6111@electric-eye.fr.zoreil.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-Organisation: Land of Sunshine Inc. Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ming Lei : > On Sun, Jul 22, 2012 at 1:31 AM, Linus Torvalds > wrote: > > On Fri, Jul 20, 2012 at 5:33 AM, Ming Lei wrote: > >> The RFC patch is just for discussing if the idea of deferring > >> request_firmware is doable for addressing the issue of > >> request_firmware in resume path, which is caused by driver > >> unbind/rebind during resume. > > > > NAK. > > Suppose it is not good for resume case, I think it still makes sense > for early boot > situation, at least the patch will support to request firmware inside > init call, and > allow drivers to be built in kernel in case of requesting firmware from probe(). Could there be a simple, static and inefficient way to link firmware and code together ? -- Ueimor