mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: david@lang.hm
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ming Lei <tom.leiming@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-usb <linux-usb@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Oliver Neukum <oneukum@suse.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [RFC] firmware load: defer request_firmware during early boot and resume
Date: Sat, 21 Jul 2012 13:46:30 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1207211344390.20176@asgard.lang.hm> (raw)
In-Reply-To: <CA+55aFwte5bc-4FC758pBN3FbrtKQfwm_Mv_banekhL=kSF8kg@mail.gmail.com>

On Sat, 21 Jul 2012, Linus Torvalds wrote:

>> In my opinion,  we should cache firmware data for all hotplug
>> devices or devices which may experience power loss automatically
>> in kernel during suspend-resume cycle because all such devices may be
>> disconnected and connected again during suspend-resume cycle.
>
> Yes. *THAT* is absolutely the kind of change I'd love to see. The core
> device layer doesn't really make it easy to handle firmware sanely
> over suspend/resume, which is kind of sad. Why does every driver have
> to have its own "let me remember my firmware over the suspend/resume
> event" and have extra code in suspend/resume, when it's really a
> pretty generic situation: if the device has firmware, wouldn't it be
> really nice if the core driver layer just knew about that and kept
> track of it?

firmware can be added to the kernel image at compile time. would it make 
sense for there to be some mechanism that can add firmware to the kernel 
image after the fact so that it can create a 'cache' of the firmware 
needed for the particular system as part of that systems kernel image?

David Lang

  reply	other threads:[~2012-07-21 20:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 12:33 Ming Lei
2012-07-20 12:52 ` Borislav Petkov
2012-07-20 12:57   ` Ming Lei
2012-07-20 13:03     ` Borislav Petkov
2012-07-20 13:09       ` Ming Lei
2012-07-20 13:13         ` Borislav Petkov
2012-07-20 13:54 ` Oliver Neukum
2012-07-20 15:53   ` Ming Lei
2012-07-21  4:13 ` Ming Lei
2012-07-21  9:56   ` Rafael J. Wysocki
2012-07-21 13:25     ` Ming Lei
2012-07-21 17:35       ` Rafael J. Wysocki
2012-07-21 17:31 ` Linus Torvalds
2012-07-21 17:53   ` Rafael J. Wysocki
2012-07-21 19:55   ` Ming Lei
2012-07-21 20:38     ` Linus Torvalds
2012-07-21 20:46       ` david [this message]
2012-07-21 23:24       ` Ming Lei
2012-07-22 12:58       ` Borislav Petkov
2012-07-22 19:46         ` Linus Torvalds
2012-07-23  8:12           ` Borislav Petkov
2012-07-21 21:01     ` Francois Romieu
2012-07-21 17:49 ` Rafael J. Wysocki
2012-07-21 20:09   ` Ming Lei
2012-07-21 21:33     ` Rafael J. Wysocki

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=alpine.DEB.2.02.1207211344390.20176@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=tom.leiming@gmail.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®