Issue 1084013: Added check to ensure LID is in a closed state before proceeding

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 1084013: Added check to ensure LID is in a closed state before proceeding (Closed)

Created:
10 years, 9 months ago by Sameer Nanda

Modified:
9 years, 5 months ago

Reviewers:
sosa

CC:
chromium-os-reviews_chromium.org

Visibility:
Public.

Description

Added check to ensure LID is in a closed state before proceeding with suspend-to-RAM. This is to fix a race condition where if the LID is reopened instantaneously after being closed, two LID events get generated (first for LID close and second for LID open). The second event makes the system go back to sleep since the LID state is not being checked. BUG=1961 TEST=manual testing on x200 to make system go to suspend on closing LID

Patch Set 1 #

Created: 10 years, 9 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+6 lines, -0 lines)			Patch
	M	src/platform/acpi/action_lid.sh	View		1 chunk	+6 lines, -0 lines	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

lgtm!

Expand Messages | Collapse Messages