public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: kaustav.majumdar@wipro.com
Cc: linux-pm@lists.osdl.org
Subject: Re: Query regarding behavior of PCMCIA devices with respect to suspend and resume
Date: Tue, 17 Jan 2006 09:57:31 +0100	[thread overview]
Message-ID: <20060117085731.GA4726@isilmar.linta.de> (raw)
In-Reply-To: <05B7784238A51247A0A9FB4B348CECAE014CEACE@PNE-HJN-MBX01.wipro.com>

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

Hi,

On Tue, Jan 17, 2006 at 02:12:20PM +0530, kaustav.majumdar@wipro.com wrote:
> I am new to linux power management.... I had seen some PCMCIA client
> drivers, where in the event handler for events CARD_SUSPEND and
> CARD_RESUME nothing generic had been done but those events ultimately
> causes release and get configuration only.....

Exactly; and that's why this even gets moved into the upper layer for
2.6.17:
http://kernel.org/git/?p=linux/kernel/git/brodo/pcmcia-2.6.git;a=commit;h=66b91eb48d18d4781bddcf8f0ac872e2405903fc

> So does that mean the expected behavior from any PCMCIA device in case
> of suspend/resume activity is to release its configurations on
> suspension and getting new configuration without actually resuming the
> task the device was performing at the time of suspension???

Well, most PCMCIA drivers are "dumb" in this regard -- but, for example, the
net drivers do stop the queue and restart it on suspend and resume. To do it
properly, you do need to stop all activity in the .suspend() callback and
continue processing it in or after .resume()

	Dominik

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-01-17  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  8:42 Query regarding behavior of PCMCIA devices with respect to suspend and resume kaustav.majumdar
2006-01-17  8:57 ` Dominik Brodowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-17 13:19 kaustav.majumdar
2006-01-17 19:40 ` Dominik Brodowski
2006-01-18  3:39 kaustav.majumdar
2006-01-18 15:20 ` Alan Stern

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=20060117085731.GA4726@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=kaustav.majumdar@wipro.com \
    --cc=linux-pm@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox