Skip to content

L
linux-davinci
Switch branch/tag
  1. 04 Jan, 2009 5 commits
    • Jiri Kosina's avatar
      HID: add phys and name ioctls to hidraw · 9188e79e
      Jiri Kosina authored 
      The hiddev interface provides ioctl() calls which can be used
to obtain phys and raw name of the underlying device.

Add the corresponding support also into hidraw.
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      9188e79e
    • Kay Sievers's avatar
      HID: struct device - replace bus_id with dev_name(), dev_set_name() · 6bbe586f
      Kay Sievers authored 
      This patch is part of a larger patch series which will remove
the "char bus_id[20]" name string from struct device. The device
name is managed in the kobject anyway, and without any size
limitation, and just needlessly copied into "struct device".

To set and read the device name dev_name(dev) and dev_set_name(dev)
must be used. If your code uses static kobjects, which it shouldn't
do, "const char *init_name" can be used to statically provide the
name the registered device should have. At registration time, the
init_name field is cleared, to enforce the use of dev_name(dev) to
access the device name at a later time.

We need to get rid of all occurrences of bus_id in the entire tree
to be able to enable the new interface. Please apply this patch,
and possibly convert any remaining remaining occurrences of bus_id.

We want to submit a patch to -next, which will remove bus_id from
"struct device", to find the remaining pieces to convert, and finally
switch over to the new api, which will remove the 20 bytes array
and does no longer have a size limitation.

CC: Jiri Kosina <jkosina@suse.cz>
Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: default avatarKay Sievers <kay.sievers@vrfy.org>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      6bbe586f
    • Alan Stern's avatar
      HID: automatically call usbhid_set_leds in usbhid driver · 08ef08ee
      Alan Stern authored 
      This patch (as1146c) makes usbhid automatically call usbhid_set_leds()
for any device that supports the keyboard boot protocol.

In theory this should be perfectly safe.  BIOSes send the LED output
report as part of their normal device initialization, so any keyboard
device supporting the boot protocol has to be able to handle it.

As a side effect, the hid-dell and hid-bright drivers are no longer
needed, and the Logitech keyboard driver can be removed from hid-lg.

CC: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      08ef08ee
    • Jiri Kosina's avatar
      HID: non-input reports can also be numbered · efc7ce18
      Jiri Kosina authored 
      When computing the maximal buffer size needed, we must take into
account that not only input reports can be numbered.

Pointed out in bugzilla #10467
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      efc7ce18
    • Jiri Kosina's avatar
      HID: ignore mouse interface for unibody macbooks · ac26fca3
      Jiri Kosina authored 
      The mouse interface on unibody macbooks is going to be handled by
bcm59743 driver in 2.6.29.
Reported-by: default avatarHenrik Rydberg <rydberg@euromail.se>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      ac26fca3
  3. 03 Jan, 2009 35 commits