[added line breaks]
Thanks for your reply. I understand (pretty much) the suspend/resume interface and
its registration via the Linux device model.
However, that is a kernel-level interface. Assuming you have a kernel component to
your driver, I suppose it could register a suspend() function and communicate it to
the user space part of the driver.
But in a case like suspend-to-RAM, the kernel freezes user space threads before the
suspend() functions are invoked. By the time the suspend function is called, it is
too late to communicate with user space.
Is there a form of user-space driver notification supported by the kernel? Or does
the kernel portion of the driver have to register for kernel notifications (which
precede thread freezing) and alert the user space portion before it is frozen?
-----Original Message-----
From: Hans J. Koch [mailto:[email protected]]
Sent: Tuesday, February 15, 2011 3:13 PM
To: Benenati, Chris J
Cc: [email protected]
Subject: Re: power management of user-space drivers
On Tue, Feb 15, 2011 at 01:46:03PM -0800, Benenati, Chris J wrote:
> Somebody brought your web page http://www.kernel.org/doc/htmldocs/uio-howto.html
> to my attention.
Hi Chris,
first of all: Please don't send private mail to kernel maintainers unless
you're willing to pay for private consultation. UIO is discussed on the
Linux Kernel Mailing List (LKML), and it's a benefit for everyone if these
discussions are public and can be found in the archives by search engines.
So, please make sure you Cc: LKML ([email protected]) in any
further mails.
>
> How do you handle power management with such a driver? For example, if state
> has to be saved before a suspend-to-RAM, or reinitialized on the subsequent resume.
You need to do that yourself, e.g. for a PCI card by implementing a suspend()
and resume() function and setting the respective pointers in struct pci_driver.
These functions will be called automatically by the driver core, and you can do
whatever you need there.
A way to implement such a thing for platform devices can be found in
drivers/uio/uio_pdrv_genirq.c
Thanks,
Hans