summaryrefslogtreecommitdiffstats
path: root/drivers/leds/led-triggers.c
diff options
context:
space:
mode:
authorDmitry Torokhov <dmitry.torokhov@gmail.com>2009-09-16 01:06:43 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2009-09-17 23:23:45 -0700
commit181d683d752c432635eda0f182ee71548c1f1820 (patch)
tree1fa397811ea6bcc73001fe1ab5b53525f2b88f74 /drivers/leds/led-triggers.c
parent0cb583fd2862f19ea88b02eb307d11c09e51e2f8 (diff)
downloadlinux-181d683d752c432635eda0f182ee71548c1f1820.tar.gz
linux-181d683d752c432635eda0f182ee71548c1f1820.tar.bz2
linux-181d683d752c432635eda0f182ee71548c1f1820.zip
Input: libps2 - additional locking for i8042 ports
The serio ports on i8042 are not completely isolated; while we provide enough locking to ensure proper serialization when accessing control and data registers AUX and KBD ports can still have an effect on each other on PS/2 protocol level. The most prominent effect is that issuing a command for the device connected to one port may cause abort of the command currently executing by the device connected to another port. Since i8042 nor serio subsystem are not aware of the details of the PS/2 protocol (length of the commands and their replies and so on) the locking should be done on libps2 level by adding special handling when we see that we are dealing with serio port on i8042. Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Diffstat (limited to 'drivers/leds/led-triggers.c')
0 files changed, 0 insertions, 0 deletions