linux-stable.git/drivers/input/keyboard, branch linux-2.6.20.y

[SUNKBD]: Fix sunkbd_enable(sunkbd, 0); obvious.

2006-12-17T22:06:58+00:00

"sunkbd_enable(sunkbd, 0);" has no effect. Adding "sunkbd->enabled =
enable" in sunkbd_enable (obvious)

Signed-off-by: Fabrice Knevez 
Signed-off-by: David S. Miller

[PATCH] m68k trivial build fixes

2006-12-17T18:21:53+00:00

amikbd: missing declaration
sun3_NCR5380: more work_struct mess
sun3_NCR5380: cast is not an lvalue

Signed-off-by: Al Viro

[PATCH] missing includes in hilkbd

2006-12-13T17:05:52+00:00

Now that it's built on m68k too...

Signed-off-by: Al Viro 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Input: kill maple_keyb.c driver

2006-12-08T06:36:44+00:00

The bus for this was removed entirely some time ago, as well as most
of the drivers that referenced it. maple_keyb seems to have been the
odd one out, and was still sitting in the source tree (though not
actually part of the build system). Kill off the rest of it..

Signed-off-by: Paul Mundt 
Signed-off-by: Dmitry Torokhov

Merge rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6

2006-12-08T06:07:56+00:00

Conflicts:

	drivers/usb/input/hid.h

Input: add driver for keyboard on AAED-2000 development board (ARM)

2006-11-24T05:42:50+00:00

The keyboard is connected via GPIOs to the processor, and scanned
using a column sample register. The hardware provides no debouncing
mechanism, so the state of the keys is read KBDSCAN_STABLE_COUNT
times before being reported to the input layer.

The status of the keys needs to be polled because there is no
interrupt hooked to the lines. A workqueue is used for this.

Signed-off-by: Nicolas Bellido Y Ortega 
Signed-off-by: Dmitry Torokhov

Input: handle serio_register_driver() errors

2006-11-24T04:35:10+00:00

Signed-off-by: Akinobu Mita 
Signed-off-by: Dmitry Torokhov

WorkStruct: make allyesconfig

2006-11-22T14:57:56+00:00

Fix up for make allyesconfig.

Signed-Off-By: David Howells

WorkStruct: Pass the work_struct pointer instead of context data

2006-11-22T14:55:48+00:00

Pass the work_struct pointer to the work function rather than context data.
The work function can use container_of() to work out the data.

For the cases where the container of the work_struct may go away the moment the
pending bit is cleared, it is made possible to defer the release of the
structure by deferring the clearing of the pending bit.

To make this work, an extra flag is introduced into the management side of the
work_struct.  This governs auto-release of the structure upon execution.

Ordinarily, the work queue executor would release the work_struct for further
scheduling or deallocation by clearing the pending bit prior to jumping to the
work function.  This means that, unless the driver makes some guarantee itself
that the work_struct won't go away, the work function may not access anything
else in the work_struct or its container lest they be deallocated..  This is a
problem if the auxiliary data is taken away (as done by the last patch).

However, if the pending bit is *not* cleared before jumping to the work
function, then the work function *may* access the work_struct and its container
with no problems.  But then the work function must itself release the
work_struct by calling work_release().

In most cases, automatic release is fine, so this is the default.  Special
initiators exist for the non-auto-release case (ending in _NAR).


Signed-Off-By: David Howells

lkkbd: Remove my old snail-mail address

2006-11-17T09:32:04+00:00

I moved to a different town and my old snail-mail address is invalid
now.  Also, there's no need at all to have any address like that in
the sources, so remove it completely.

Signed-off-by: Jan-Benedict Glaw