From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: device model documentation 2/3
Date: Wed, 05 Jun 2002 12:41:21 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102328207605579@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102338823505348@msgid-missing>
> Whether suspend is called with a given level is a policy of the
> platform. Some levels may be omitted; drivers must not assume the
> reception of any level. However, all levels must be called in the
> order above; i.e. notification will always come before disabling;
> disabling the device will come before suspending the device.
>
> All calls are made with interrupts enabled, except for the
> SUSPEND_POWER_DOWN level.
This is a slight problem for USB. We need to switch on interupts
to send a message to the device. Is this provided for ?
Regards
Oliver
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-06-05 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 4:49 device model documentation 2/3 Pavel Machek
2002-06-05 12:41 ` Oliver Neukum [this message]
2002-06-05 12:51 ` Oliver Neukum
2002-06-05 19:04 ` Patrick Mochel
2002-06-05 19:11 ` Patrick Mochel
2002-06-05 21:52 ` Oliver Neukum
2002-06-05 21:54 ` Oliver Neukum
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 16:25 Patrick Mochel
2002-06-02 2:00 ` Pavel Machek
2002-06-04 15:50 ` Martin Dalecki
2002-06-04 17:49 ` Greg KH
2002-06-05 12:51 ` Oliver Neukum
2002-06-05 19:11 ` Patrick Mochel
2002-06-02 4:49 ` Pavel Machek
2002-06-05 21:54 ` Oliver Neukum
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=marc-linux-hotplug-102328207605579@msgid-missing \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=linux-hotplug@vger.kernel.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.