Re: input.c: start on release
From: Dmitry Torokhov
Date: Fri Feb 23 2007 - 10:06:34 EST
On 2/23/07, Pete Zaitcev <zaitcev@xxxxxxxxxx> wrote:
Here's a curious code I found in drivers/input/input.c (2.6.21-rc1):
void input_release_device(struct input_handle *handle)
Is the above supposed to be this way, or you meant ->stop here?
It should be ->start(). You are probably confused a little by the name
of the function. input_release_device() is called when userspace
issues ioctl(fd, EVIOCGRAB, 0) releasing (or ungrabbing) the device
(as opposed to xxx_release(file, inode) type functions that are called
when last user of a file drops off). In our case we want to give
handlers a chance to resume their control over device. Right now
standard keyboard driver uses start method do bring back in sync LED
state of a keyborad-like device after it was released (ungrabbed).
The commit comment says:
Input: fix list iteration in input_release_device()
It says me precisely nothing about the way it's supposed ot be, sorry...
It reason for ->start was explained in the patch it was introduced in,
the changeset you are referring to literally fixes issue with
iteration through list in this function.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/