public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	robfitz@273k.net, akpm@osdl.org, jikos@jikos.cz, vojtech@suse.cz,
	dmonakhov@openvz.org, johannes@sipsolutions.net
Subject: Re: [PATCH] linux-input: bcm5974-0.57: mode-switch to atp_open, cleanup bug fixed
Date: Tue, 22 Jul 2008 02:55:42 +0200	[thread overview]
Message-ID: <1216688142.4768.26.camel@alnilam> (raw)
In-Reply-To: <20080720051016.GA7853@anvil.corenet.prv>

Hi Dmitri,

Regarding open/close and suspend/resume, I have difficulties finding out
what the proper behavior is for the various error states that can
appear. I also wonder whether open should commute with suspend or not.
It would be of great help to get answers to the scenarios below.

1. From the state (!opened,!suspended), calling open followed by
suspend, or suspend followed by open, are we in the same state?

2. From the state (!opened,!suspended), calling open fails. What state
are we in?

3. From the state (!opened,suspended), calling open gets us to what
state?

4. From the state (!opened,suspended), calling open fails. Where are we?

5. From the state (opened,suspended), calling resume fails. What state
are we in?

Best regards,
Henrik Rydberg



  parent reply	other threads:[~2008-07-22  0:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 11:03 [PATCH] linux-input: bcm5974-0.57: mode-switch to atp_open, cleanup bug fixed Henrik Rydberg
2008-07-20  5:10 ` Dmitry Torokhov
2008-07-21 12:24   ` Henrik Rydberg
2008-07-22  0:55   ` Henrik Rydberg [this message]
2008-07-22 13:52     ` Dmitry Torokhov
2008-07-22 22:19       ` Henrik Rydberg
2008-07-23 11:37       ` Henrik Rydberg
2008-07-23 13:38       ` 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=1216688142.4768.26.camel@alnilam \
    --to=rydberg@euromail.se \
    --cc=akpm@osdl.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=jikos@jikos.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robfitz@273k.net \
    --cc=vojtech@suse.cz \
    /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