Re: [PATCH] linux-input: bcm5974-0.57: mode-switch to atp_open, cleanup bug fixed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux