All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Benenati, Chris J" <chris.j.benenati@intel.com>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>
Subject: Re: uio: power management of user-space drivers
Date: Tue, 15 Feb 2011 17:40:36 -0800	[thread overview]
Message-ID: <20110216014036.GA29534@kroah.com> (raw)
In-Reply-To: <0635488208022A4F82521A04A4772E15C555EF7B@orsmsx503.amr.corp.intel.com>


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Tue, Feb 15, 2011 at 04:35:16PM -0800, Benenati, Chris J wrote:
> Well, for example, a device may have complex application-driven hardware state,
> which in turn in turn can be driven by user inputs. That state will be lost when
> the system powers down.  It might be necessary to invoke the driver suspend()
> function before power is dropped, to read registers and preserve that state.
> It is definitely necessary to call the resume function to reprogram the registers
> when the power is restored.

Then write a real driver for your device if this type of "complex"
hardware state must be controlled.  Don't use UIO for things it was not
ment to be used for.

thanks,

greg k-h

  reply	other threads:[~2011-02-16  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0635488208022A4F82521A04A4772E15C555EC7E@orsmsx503.amr.corp.intel.com>
     [not found] ` <20110215231236.GE2785@local>
2011-02-15 23:27   ` power management of user-space drivers Benenati, Chris J
2011-02-16  0:21     ` uio: " Hans J. Koch
2011-02-16  0:35       ` Benenati, Chris J
2011-02-16  1:40         ` Greg KH [this message]
2011-02-16  1:17       ` Greg KH
2011-02-16 18:15         ` Hans J. Koch
2011-02-16  0:20   ` Benenati, Chris J

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=20110216014036.GA29534@kroah.com \
    --to=greg@kroah.com \
    --cc=chris.j.benenati@intel.com \
    --cc=gregkh@suse.de \
    --cc=hjk@hansjkoch.de \
    --cc=linux-kernel@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.