| commit | 7104e2d5a85b4b786d6a63568beffe1e185547bb | |
| author | Pierre Ossman <drzeus@drzeus.cx> | |
| Wed, 4 Oct 2006 09:15:41 +0000 (4 02:15 -0700) | ||
| committer | Linus Torvalds <torvalds@g5.osdl.org> | |
| Wed, 4 Oct 2006 14:55:15 +0000 (4 07:55 -0700) | ||
| tree | 1478b1076a66476a121e687dd9547d5c08d9c3ba | treesnapshot (tar.gz zip) |
| parent | 8a4da1430f7f2a16df3be9c7b5d55ba4e75b708c | commitdiff |
[PATCH] mmc: use own work queue
The MMC layer uses the standard work queue for doing card detection. As this
queue is shared with other crucial subsystems, the effects of a long (and
perhaps buggy) detection can cause the system to be unusable. E.g. the
keyboard stops working while the detection routine is running.
The solution is to add a specific mmc work queue to run the detection code in.
This is similar to how other subsystems handle detection (a full kernel
thread is the most common theme).
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
Cc: Russell King <rmk@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
The MMC layer uses the standard work queue for doing card detection. As this
queue is shared with other crucial subsystems, the effects of a long (and
perhaps buggy) detection can cause the system to be unusable. E.g. the
keyboard stops working while the detection routine is running.
The solution is to add a specific mmc work queue to run the detection code in.
This is similar to how other subsystems handle detection (a full kernel
thread is the most common theme).
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
Cc: Russell King <rmk@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| drivers/mmc/mmc.c | diffblobblamehistory | |
| drivers/mmc/mmc.h | diffblobblamehistory | |
| drivers/mmc/mmc_sysfs.c | diffblobblamehistory |