All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC][PATCH] PM: Print a warning if firmware is requested when tasks are frozen
Date: Tue, 3 May 2011 07:05:25 -0700	[thread overview]
Message-ID: <20110503140525.GA7944@suse.de> (raw)
In-Reply-To: <BANLkTimwmC=ckj4g_ct4EhOSLD7NDgxdng@mail.gmail.com>

On Mon, May 02, 2011 at 05:59:22PM -0700, Linus Torvalds wrote:
> On Mon, May 2, 2011 at 4:28 PM, Greg KH <gregkh@suse.de> wrote:
> >
> > A driver that does not rely on the firmware being built in would be
> > correct in calling request_firmware_nowait() on resume, then when
> > userspace is properly woken up, the firmware would be sent to the
> > device, then the driver would be notified, load it, and handle things
> > as part of its resume sequence from that notification.
> >
> > Isn't that ideally what we want to have happen?
> 
> No. Absolutely not.
> 
> What we ideally want to happen is for the driver to not be a stupid
> piece of sh*t.

Well, we all want that :)

> A driver that needs firmware loading at resume time IS A BROKEN DRIVER.
> 
> It really is that simple.

Ok, fair enough, then I have no objection to this patch.  It will let us
catch those shitty drivers and fix them up to not do this.

thanks,

greg k-h

  parent reply	other threads:[~2011-05-03 14:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 22:44 [RFC][PATCH] PM: Print a warning if firmware is requested when tasks are frozen Rafael J. Wysocki
2011-05-02 23:12 ` Greg KH
2011-05-02 23:21   ` Linus Torvalds
2011-05-02 23:21     ` Linus Torvalds
2011-05-02 23:28     ` Greg KH
2011-05-02 23:28     ` Greg KH
2011-05-03  0:59       ` Linus Torvalds
2011-05-03  0:59       ` Linus Torvalds
2011-05-03 14:05         ` Greg KH
2011-05-03 14:05         ` Greg KH [this message]
2011-05-02 23:12 ` Greg KH
2011-05-02 23:30 ` Valdis.Kletnieks
2011-05-03 11:02   ` Rafael J. Wysocki
2011-05-03 14:06     ` Greg KH
2011-05-03 14:06     ` Greg KH
2011-05-03 17:12       ` Rafael J. Wysocki
2011-05-03 17:12       ` Rafael J. Wysocki
2011-05-03 15:47     ` Valdis.Kletnieks
2011-05-03 15:56       ` Joe Perches
2011-05-03 15:56       ` Joe Perches
2011-05-03 17:14         ` Rafael J. Wysocki
2011-05-03 17:14         ` Rafael J. Wysocki
     [not found]       ` <201105031914.18160.rjw@sisk.pl>
2011-05-03 18:03         ` Valdis.Kletnieks
2011-05-03 15:47     ` Valdis.Kletnieks
2011-05-03 11:02   ` Rafael J. Wysocki
2011-05-02 23:30 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2011-05-02 22:44 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=20110503140525.GA7944@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.