Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 19 4月, 2012 1 次提交
  3. 13 3月, 2012 1 次提交
  5. 28 2月, 2012 1 次提交
  7. 22 2月, 2012 1 次提交
  9. 21 2月, 2012 2 次提交
  11. 07 2月, 2012 2 次提交
    • J
      HID: tivo: fix broken build · 2701eaab
      由 Jiri Kosina 提交于 
      Fix mismatch between Kconfig name and Makefile expectation.
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      2701eaab
    • J
      HID: add support for tivo slide remote · 44ea35c1
      由 Jarod Wilson 提交于 
      This patch finishes off adding full support for the TiVo Slide remote,
which is a mostly pure HID device from the perspective of the kernel.
There are a few mappings that use a vendor-specific usage page, and a
few keys in the consumer usage page that I think make sense to remap
slightly, to better fit their key labels' intended use. Doing this in a
stand-alone hid-tivo.c makes the modifications only matter for this
specific device.

What's actually connected to the computer is a Broadcom-made usb dongle,
which has an embedded hub, bluetooth adapter, mouse and keyboard
devices. You pair with the dongle, then the remote sends data that its
converted into HID on the keyboard interface (the mouse interface
doesn't do anything interesting, so far as I can tell).

lsusb for this device:
Bus 004 Device 005: ID 0a5c:2190 Broadcom Corp.
Bus 004 Device 004: ID 0a5c:4503 Broadcom Corp.
Bus 004 Device 003: ID 150a:1201
Bus 004 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

Speaking of the keyboard interface, the remote actually does contain a
keyboard as well. The top slides away, revealing a reasonably functional
qwerty keyboard (not unlike many slide cell phones), thus the product
name.

CC: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: NJarod Wilson <jarod@redhat.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      44ea35c1
  13. 06 2月, 2012 2 次提交
  15. 05 1月, 2012 1 次提交
  17. 02 1月, 2012 1 次提交
  19. 19 12月, 2011 1 次提交
  21. 17 12月, 2011 1 次提交
    • J
      HID: introduce proper dependency of HID_BATTERY on POWER_SUPPLY · 7e69ba7c
      由 Jiri Kosina 提交于 
      ppc6xx_defconfig reveals this:

drivers/built-in.o: In function `hidinput_cleanup_battery': drivers/hid/hid-input.c:351: undefined reference to`power_supply_unregister'
drivers/built-in.o: In function `hidinput_setup_battery': drivers/hid/hid-input.c:338: undefined reference to `power_supply_register'
make[1]: *** [.tmp_vmlinux1] Error 1

The defconfig in question doens't mention either option and kbuild is
genertaing

	CONFIG_HID_BATTERY_STRENGTH=y
	CONFIG_POWER_SUPPLY=m

which is wrong. Put a proper dependency in place.
Reported-by: NTony Breeds <tony@bakeyournoodle.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      7e69ba7c
  23. 15 12月, 2011 1 次提交
  25. 12 12月, 2011 1 次提交
  27. 06 12月, 2011 1 次提交
  29. 30 11月, 2011 1 次提交
  31. 28 11月, 2011 1 次提交
    • J
      HID: hid-input: add support for HID devices reporting Battery Strength · 4f5ca836
      由 Jeremy Fitzhardinge 提交于 
      Some HID devices, such as my Bluetooth mouse, report their battery
strength as an event.  Rather than passing it through as a strange
absolute input event, this patch registers it with the power_supply
subsystem as a battery, so that the device's Battery Strength can be
reported to usermode.

The battery appears in sysfs names
/sys/class/power_supply/hid-<UNIQ>-battery, and it is a child of the
battery-containing device, so it should be clear what it's the battery of.

Unfortunately on my current Fedora 16 system, while the battery does
appear in the UI, it is listed as a Laptop Battery with 0% charge (since
it ignores the "capacity" property of the battery and instead computes
it from the "energy*" fields, which we can't supply given the limited
information contained within the HID Report).

Still, this patch is the first step.
Signed-off-by: NJeremy Fitzhardinge <jeremy@goop.org>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      4f5ca836
  33. 23 11月, 2011 3 次提交
    • D
      HID: wiimote: Add extension support stub · cb99221b
      由 David Herrmann 提交于 
      The wiimote supports several extensions. This adds a separate source file which
handles all extensions and can be disabled at compile-time.

The driver reacts on "plug"-events on the extension port and starts a worker
which initializes or deinitializes the extensions.

Currently, the initialization logic is not fully understood and we can only
detect and enable all extensions when all extensions are deactivated. Therefore,
we need to disable all extensions, then detect and activate them again to react
on "plug"-events.
However, deactivating extensions will generate a new "plug"-event and we will
never leave that loop. Hence, we only support extensions if they are plugged
before the wiimote is connected (or before the ext-input device is opened). In
the future we may support full extension hotplug support, but
reverse-engineering this may take a while.
Signed-off-by: NDavid Herrmann <dh.herrmann@googlemail.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      cb99221b
    • J
      HID: hyperv: fixup Kconfig / Makefile entries · 6cf851d8
      由 Jiri Kosina 提交于 
      Rename the Kconfig entry for hyperv mouse driver so that it has
HID_ prefix as all the other drivers; while at it, place the entry
for this driver to properly ordered place in Makefile and Kconfig.
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      6cf851d8
    • K
      HID: Move the hid-hyperv driver out of staging · b95f5bcb
      由 K. Y. Srinivasan 提交于 
      The file  hid-hyperv.c implements a hid compliant mouse driver for use on a
Hyper-V based system. This driver is currently in the staging area and as part
of the effort to move this driver out of staging, I had posted the driver code
for community review a few weeks ago. This current patch addresses all the
review comments I have gotten to date. All the relevant patches have already
been submitted to the staging tree as well.

As per Greg's suggestion, this patch does not get rid of the code from
the staging area. Once the mouse driver lands under the hid directory,
we will cleanup the staging directory.
Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      b95f5bcb
  35. 21 10月, 2011 1 次提交
  37. 17 10月, 2011 2 次提交
    • J
      HID: primax: remove spurious dependency · dfe9a312
      由 Jiri Kosina 提交于 
      Remove Kconfig dependency for hid-primax driver on CONFIG_EXPERT.
Please see changelog of 73d5e8f7 ("HID: fix up 'EMBEDDED' mess in
Kconfig") for reasoning behind this.
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      dfe9a312
    • T
      HID: support primax keyboards violating USB HID spec · f6a04605
      由 Terry Lambert 提交于 
      Primax keyboards with the issue this driver addresses report modifier
keys as in band key events instead of as out of band modifier bits,
resulting in the modifier keys generating key up events immediately
before the keys they are intended to modify.  This driver rewrites
the raw report data from such keyboards into USB HID 1.11 compliant
report data.  It only matches the USB vendor and product IDs for the
keyboard it has been tested on. Since there are several keyboards,
notably a number of laptops and folding USB keyboards known to have
similar unresolved problem reports, the list is expected to grow.
Signed-off-by: NTerry Lambert <tlambert@chromium.org>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      f6a04605
  39. 15 9月, 2011 1 次提交
    • N
      HID: Add full support for Logitech Unifying receivers · 534a7b8e
      由 Nestor Lopez Casado 提交于 
      With this driver, all the devices paired to a single Unifying
receiver are exposed to user processes in separated /input/dev
nodes.

Keyboards with different layouts can be treated differently,
Multiplayer games on single PC (like home theater PC) can
differentiate input coming from different kbds paired to the
same receiver.

Up to now, when Logitech Unifying receivers are connected to a
Linux based system, a single keyboard and a single mouse are
presented to the HID Layer, even if the Unifying receiver can
pair up to six compatible devices. The Unifying receiver by default
multiplexes all incoming events (from multiple keyboards/mice)
into these two.
Signed-off-by: NNestor Lopez Casado <nlopezcasad@logitech.com>
Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@gmail.com>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      534a7b8e
  41. 07 9月, 2011 1 次提交
  43. 23 8月, 2011 1 次提交
  45. 16 8月, 2011 1 次提交
  47. 11 8月, 2011 1 次提交
  49. 04 8月, 2011 2 次提交
  51. 21 7月, 2011 1 次提交
  53. 11 7月, 2011 1 次提交
  55. 27 6月, 2011 1 次提交
  57. 13 6月, 2011 1 次提交
  59. 08 6月, 2011 1 次提交
    • S
      HID: Add driver to fix Speedlink VAD Cezanne support · 74bc6953
      由 Stefan Kriwanek 提交于 
      Speedlink VAD Cezanne have a hardware bug that makes the cursor "jump" from one
place to another every now and then. The issue are relative motion events
erroneously reported by the device, each having a distance value of +256. This
256 can in fact never occur due to real motion, therefore those events can
safely be ignored.  The driver also drops useless EV_REL events with a value of
0, that the device sends every time it sends an "real" EV_REL or EV_KEY event.
Signed-off-by: NStefan Kriwanek <mail@stefankriwanek.de>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      74bc6953
  61. 07 6月, 2011 1 次提交
  63. 23 5月, 2011 1 次提交
  65. 20 5月, 2011 1 次提交