提交 · 693508df9824ecc2bf308a35b58159aa2fecf91f · openanolis / cloud-kernel

21 10月, 2010 40 次提交

V4L/DVB: IR/imon: protect ictx's kc and last_keycode w/spinlock · 693508df

由 Jarod Wilson 提交于 9月 15, 2010

Lest we get our keycodes wrong... Thus far, in practice, I've not found
it to actually matter, but its one of the issues raised in
https://bugzilla.kernel.org/show_bug.cgi?id=16351 that wasn't addressed
by converting to using native IR keydown/up functions.
Signed-off-by: NJarod Wilson <jarod@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

693508df

V4L/DVB: imon: split mouse events to a separate input dev · eaf2bcc9

由 David Härdeman 提交于 9月 15, 2010

This is a stab at separating the mouse (and front panel/knob) events
out to a separate input device. This is necessary in preparation for
the next patch which makes the rc-core input dev opaque to rc
drivers.

I can't verify the correctness of the patch beyond the fact that it
compiles without warnings. The driver has resisted most of my
attempts at understanding it properly...for example, the double calls
to le64_to_cpu() and be64_to_cpu() which are applied in
imon_incoming_packet() and imon_panel_key_lookup() would amount
to a bswab64() call, irregardless of the cpu endianness, and I think
the code wouldn't have worked on a big-endian machine...

- Minor alterations to apply with minimal core IR changes
- Use timer for imon keys too, since its entirely possible for the
  receiver to miss release codes (either by way of another key being
  pressed while the first is held or by the remote pointing away from
  the recevier when the key is release. yes, I know, its ugly).
- Bump driver version number, since this is a fairly significant change
  (for the much much better).
Tested successfully w/an imon knob receiver.
Signed-off-by: NDavid Härdeman <david@hardeman.nu>
Signed-off-by: NJarod Wilson <jarod@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

eaf2bcc9

V4L/DVB: IR: export ir_keyup so imon driver can use it directly · ee089405

由 Jarod Wilson 提交于 9月 15, 2010

The imon driver currently reimplements its own version of ir_keyup
(along with key release timer functionality also already present in the
core IR code). A follow-up imon patch will make use of ir_keyup and the
IR stack's key release code.

Trivial extraction from David Härdeman's pending rc-core merge and
device interface abstraction patchset to facilitate merging a patch
based on his imon input dev split patch ahead of the larger churn, which
is slated for post-2.6.37-rc1 (after Dmitry's large keycode patches are
merged in mainline).
Signed-off-by: NJarod Wilson <jarod@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

ee089405

V4L/DVB: saa7134: get rid of I2C_HW_SAA7134 · c72ba8e6

由 Mauro Carvalho Chehab 提交于 9月 23, 2010

The only reason for keeping I2C_HW_SAA7134 is to allow setting a
per-device polling interval. Just move this info to the platform
data, allowing drivers to change it per device, where needed.
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

c72ba8e6

V4L/DVB: Remove the usage of I2C_HW_B_CX2388x on ir-kbd-i2c.c · 44243fc2

由 Mauro Carvalho Chehab 提交于 9月 23, 2010

Move the cx88 specific initialization for Hauppauge XVR remotes
into cx88-input, removing the need for test it inside ir-kbd-i2c.

The reference at cx88 for this symbol, at:

drivers/media/video/cx88/cx88-i2c.c: core->i2c_adap.id = I2C_HW_B_CX2388x;
drivers/media/video/cx88/cx88-vp3054-i2c.c: vp3054_i2c->adap.id = I2C_HW_B_CX2388x;

Can't be removed yet, since lirc-i2c still uses it.
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

44243fc2

M
V4L/DVB: bttv: Move PV951 IR to the right driver · c0c46826
由 Mauro Carvalho Chehab 提交于 9月 22, 2010
```
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
```
c0c46826

V4L/DVB: usbvision: remove BKL from usbvision · 8403472f

由 Hans Verkuil 提交于 9月 17, 2010

Removed the BKL from usbvision.

There was an initialization bug as well where the i2c bus was registered twice.

Although when the BKL was present no oops was generated, I did run into
other i2c problems. Now that I protect against duplicate i2c registration
that bug is now gone as well.

But trying to disconnect the USB cable while someone is still using the device
still leads to a crash.
Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>

8403472f

V4L/DVB: v4l: remove obsolete include/media/v4l2-i2c-drv.h file · 1f205253