diff options
| author | Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> | 2006-02-21 15:45:48 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2006-03-23 14:35:13 -0800 |
| commit | a246fa4e9f0f1b5096a1cad0659d22fb10fb3732 (patch) | |
| tree | 21490f4d1d2794a9ccd64529431fbbd8f4e234e7 /kernel/mutex.c | |
| parent | f7391f5325ea744f0632f7ef39a90085162743ac (diff) | |
| download | op-kernel-dev-a246fa4e9f0f1b5096a1cad0659d22fb10fb3732.zip op-kernel-dev-a246fa4e9f0f1b5096a1cad0659d22fb10fb3732.tar.gz | |
[PATCH] shpchp: Fix slot state handling
Current SHPCHP driver doesn't care about the confliction between
hotplug operation via sysfs and hotplug operation via attention
button. So if those ware conflicted, slot could be an unexpected
state.
This patch changes SHPCHP driver to handle slot state properly. With
this patch, slot events are handled according to the current slot
state as shown at the Table below.
Table. Slot States and Event Handling
=========================================================================
Slot State Event and Action
=========================================================================
STATIC - Go to POWERON state if user initiates
(Slot enabled, insertion request via sysfs
Slot disabled) - Go to POWEROFF state if user initiates removal
request via sysfs
- Go to BLINKINGON state if user presses
attention button when the slot is disabled
- Go to BLINKINGOFF state if user presses
attention button when the slot is enabled
Diffstat (limited to 'kernel/mutex.c')
0 files changed, 0 insertions, 0 deletions
