From: Greg KH <greg@kroah.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: nigel@nigel.suspend2.net, linux-pm@lists.osdl.org, pavel@ucw.cz
Subject: Re: [RFC/PATCH 2/2] driver core: power management debugging
Date: Fri, 27 Apr 2007 08:40:20 -0700 [thread overview]
Message-ID: <20070427154020.GA11190@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704271525071.11149@sbz-30.cs.Helsinki.FI>
On Fri, Apr 27, 2007 at 03:25:46PM +0300, 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.
>
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> drivers/base/core.c | 13 +++++++++++++
> drivers/pci/pci-driver.c | 6 ++++++
> drivers/usb/core/driver.c | 6 ++++++
> include/linux/device.h | 1 +
> 4 files changed, 26 insertions(+)
>
> Index: 2.6/drivers/base/core.c
> ===================================================================
> --- 2.6.orig/drivers/base/core.c 2007-04-27 14:42:13.000000000 +0300
> +++ 2.6/drivers/base/core.c 2007-04-27 14:43:14.000000000 +0300
> @@ -652,6 +652,18 @@ int device_add(struct device *dev)
> class_intf->add_dev(dev, class_intf);
> up(&dev->class->sem);
> }
> +
> +#ifdef CONFIG_PM
> + if (!((dev->class && dev->class->resume) ||
> + (dev->bus && (dev->bus->resume || dev->bus->resume_early))) &&
> + !dev->pm_safe) {
> + printk(KERN_WARNING "Device driver %s lacks bus and class "
> + "support for being resumed.\n",
> + kobject_name(&dev->kobj));
> + dump_stack();
> + }
> +#endif
I think you are reporting the wrong thing here, we want to know about
the busses and classes without suspend support, not the individual
devices, right?
And dumping stuff like this to the log for every bus/class isn't the
nicest :(
> +
> Done:
> kfree(class_name);
> put_device(dev);
> @@ -989,6 +1001,7 @@ struct device *device_create(struct clas
> dev->class = class;
> dev->parent = parent;
> dev->release = device_create_release;
> + dev->pm_safe = 1;
I don't understand the use of this flag, it looks like it is only being
set, which doesn't really make it very useful.
So NAK on this patch.
Oh, and please CC: me on driver core and USB and PCI core changes
please...
thanks,
greg k-h
next prev parent reply other threads:[~2007-04-27 15:40 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
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 [this message]
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=20070427154020.GA11190@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