From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Martin <oliver.martin@student.tuwien.ac.at>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Oliver Neukum <oliver@neukum.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: USB_SUSPEND needs SUSPEND?
Date: Sun, 28 Oct 2007 19:48:36 +0100 [thread overview]
Message-ID: <200710281948.37588.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0710281245130.28311-100000@netrider.rowland.org>
On Sunday, 28 October 2007 17:50, Alan Stern wrote:
> On Sun, 28 Oct 2007, Rafael J. Wysocki wrote:
>
> > On Sunday, 28 October 2007 02:00, Oliver Martin wrote:
> > > Hello,
> > >
> > > it seems that there is some dependency missing for CONFIG_USB_SUSPEND.
> > > When I compile a kernel without CONFIG_SUSPEND, USB suspend doesn't work
> > > (or at least doesn't expose its interface to userspace).
> > > /sys/bus/usb/devices/.../power doesn't exist, but it is there when I
> > > enable CONFIG_SUSPEND. So should CONFIG_USB_SUSPEND depend on
> > > CONFIG_SUSPEND (or something selected by CONFIG_SUSPEND)?
> > >
> > > diff between the two configs follows, full config and dmesg for both
> > > kernels is available at http://stud4.tuwien.ac.at/~e0626486/usb_suspend/
> > > (though the dmesg diff doesn't seem to be all that interesting).
>
> Actually I think the problem is the other way around. /sys/.../power
> should exist whenever CONFIG_PM is defined, not just when
> CONFIG_SUSPEND is enabled.
Agreed.
prev parent reply other threads:[~2007-10-28 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 0:00 USB_SUSPEND needs SUSPEND? Oliver Martin
2007-10-28 13:35 ` Rafael J. Wysocki
2007-10-28 16:50 ` Alan Stern
2007-10-28 18:48 ` Rafael J. Wysocki [this message]
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=200710281948.37588.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver.martin@student.tuwien.ac.at \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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