Date: Wed, 16 Feb 2011 19:15:26 +0100
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Greg KH <gregkh@suse.de>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
        "Benenati, Chris J" <chris.j.benenati@intel.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: uio: power management of user-space drivers
Message-ID: <20110216181526.GA2800@local>
References: <0635488208022A4F82521A04A4772E15C555EC7E@orsmsx503.amr.corp.intel.com>
 <20110215231236.GE2785@local>
 <0635488208022A4F82521A04A4772E15C555EE4E@orsmsx503.amr.corp.intel.com>
 <20110216001847.GF2785@local>
 <20110216011754.GA11181@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110216011754.GA11181@suse.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1045
Lines: 23

On Tue, Feb 15, 2011 at 05:17:54PM -0800, Greg KH wrote:
> On Wed, Feb 16, 2011 at 01:21:04AM +0100, Hans J. Koch wrote:
> > Let me guess: suspend/resume functions are supposed to leave your hardware in
> > a consistent state and you don't know the state if the suspend() catches you
> > in the middle of your userspace processing?
> > I remember the Android guys had problems like that and invented some
> > "suspend blockers". However, I don't remember what the final answer in that
> > discussion was. Greg?
> 
> It's all in the kernel today.  See:
> 	http://lwn.net/Articles/416690/
> for all of the details you will ever need.

Interesting. After reading that, I've got the impression that this could be
used by UIO drivers and maybe solve Chris' problem. Or did I miss something?

Thanks,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/