public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: linux-pm@lists.osdl.org, Pekka J Enberg <penberg@cs.helsinki.fi>,
	pavel@ucw.cz
Subject: Re: [RFC/PATCH 2/2] driver core: power management debugging
Date: Fri, 27 Apr 2007 14:46:48 -0700	[thread overview]
Message-ID: <20070427214648.GB23282@kroah.com> (raw)
In-Reply-To: <1177709159.4737.150.camel@nigel.suspend2.net>

On Sat, Apr 28, 2007 at 07:25:59AM +1000, Nigel Cunningham wrote:
> Hi Alan.
> 
> On Fri, 2007-04-27 at 10:08 -0400, Alan Stern wrote:
> > On Fri, 27 Apr 2007, Pekka J Enberg wrote:
> > 
> > > From: Nigel Cunningham <nigel@nigel.suspend2.net>
> > > 
> > > Add power management related debugging into driver core. Make the
> > > kernel complain if a device driver lacks bus and class support for
> > > resume or if a PCI or USB driver does not have a driver specific
> > > resume function.
> > 
> > > Index: 2.6/drivers/usb/core/driver.c
> > > ===================================================================
> > > --- 2.6.orig/drivers/usb/core/driver.c	2007-04-27 14:42:13.000000000 +0300
> > > +++ 2.6/drivers/usb/core/driver.c	2007-04-27 14:43:14.000000000 +0300
> > > @@ -721,6 +721,12 @@ 	int retval = 0;
> > >  		pr_info("%s: registered new device driver %s\n",
> > >  			usbcore_name, new_udriver->name);
> > >  		usbfs_update_special();
> > > +#ifdef CONFIG_PM
> > > +		if (!new_udriver->resume)
> > > +			printk(KERN_WARNING "USB driver %s lacks driver "
> > > +					    "specific resume support.\n",
> > > +					    new_udriver->name);
> > > +#endif
> > >  	} else {
> > >  		printk(KERN_ERR "%s: error %d registering device "
> > >  			"	driver %s\n",
> > 
> > This part seems unnecessary.  There is only one USB device driver, it is
> > built into the USB core, and it does have the appropriate methods.  
> > Checking isn't needed.
> 
> Sorry. I thought you were wrong for a minute, but then I looked again at
> the messages in my dmesg...
> 
> [   33.944214] Device driver usbdev1.1_ep00 lacks bus and class support for being resumed.
> [   34.051765] Device driver usbdev1.1_ep81 lacks bus and class support for being resumed.
> [   34.113740] Device driver usbdev2.1_ep00 lacks bus and class support for being resumed.
> [   34.221541] Device driver usbdev2.1_ep81 lacks bus and class support for being resumed.
> [   34.251562] Device driver usbdev3.1_ep00 lacks bus and class support for being resumed.
> [   34.361345] Device driver usbdev3.1_ep81 lacks bus and class support for being resumed.

Those are usb endpoints and have NOTHING to do with suspend right now,
so the check is bogus.

> > On the other hand, the drivers' maintainers are probably quite aware of 
> > the missing PM support, so it's not clear that printing out warning 
> > messages will actually help anybody.
> 
> It can help the user, when they're looking for possibilities as to why things aren't working.

You will drown out the valid issues with invalid ones, like the above...

greg k-h

  reply	other threads:[~2007-04-27 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 12:25 [RFC/PATCH 2/2] driver core: power management debugging Pekka J Enberg
2007-04-27 12:37 ` Pavel Machek
2007-04-27 14:08 ` Alan Stern
2007-04-27 14:13   ` Pekka Enberg
2007-04-27 21:25   ` Nigel Cunningham
2007-04-27 21:46     ` Greg KH [this message]
2007-04-28 14:42     ` Alan Stern
2007-04-28 22:55       ` Nigel Cunningham
2007-04-29  6:50         ` Greg KH
2007-04-29  7:47           ` Nigel Cunningham
2007-04-29  7:50             ` Greg KH
2007-04-27 15:40 ` Greg KH
2007-04-27 21:38   ` Nigel Cunningham
2007-04-27 21:45     ` Greg KH

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=20070427214648.GB23282@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-pm@lists.osdl.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=penberg@cs.helsinki.fi \
    /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