<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/bluetooth/hidp/core.c, branch linux-2.6.23.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-07-17T17:23:02Z</updated>
<entry>
<title>Freezer: make kernel threads nonfreezable by default</title>
<updated>2007-07-17T17:23:02Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-07-17T11:03:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=831441862956fffa17b9801db37e6ea1650b0f69'/>
<id>urn:sha1:831441862956fffa17b9801db37e6ea1650b0f69</id>
<content type='text'>
Currently, the freezer treats all tasks as freezable, except for the kernel
threads that explicitly set the PF_NOFREEZE flag for themselves.  This
approach is problematic, since it requires every kernel thread to either
set PF_NOFREEZE explicitly, or call try_to_freeze(), even if it doesn't
care for the freezing of tasks at all.

It seems better to only require the kernel threads that want to or need to
be frozen to use some freezer-related code and to remove any
freezer-related code from the other (nonfreezable) kernel threads, which is
done in this patch.

The patch causes all kernel threads to be nonfreezable by default (ie.  to
have PF_NOFREEZE set by default) and introduces the set_freezable()
function that should be called by the freezable kernel threads in order to
unset PF_NOFREEZE.  It also makes all of the currently freezable kernel
threads call set_freezable(), so it shouldn't cause any (intentional)
change of behaviour to appear.  Additionally, it updates documentation to
describe the freezing of tasks more accurately.

[akpm@linux-foundation.org: build fixes]
Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Acked-by: Nigel Cunningham &lt;nigel@nigel.suspend2.net&gt;
Cc: Pavel Machek &lt;pavel@ucw.cz&gt;
Cc: Oleg Nesterov &lt;oleg@tv-sign.ru&gt;
Cc: Gautham R Shenoy &lt;ego@in.ibm.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Fix use-after-free oops in Bluetooth HID.</title>
<updated>2007-07-07T19:22:37Z</updated>
<author>
<name>David Woodhouse</name>
</author>
<published>2007-07-07T18:58:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1c39858b5dd46004b12c5acd26d8df346bef8a10'/>
<id>urn:sha1:1c39858b5dd46004b12c5acd26d8df346bef8a10</id>
<content type='text'>
When cleaning up HIDP sessions, we currently close the ACL connection
before deregistering the input device. Closing the ACL connection
schedules a workqueue to remove the associated objects from sysfs, but
the input device still refers to them -- and if the workqueue happens to
run before the input device removal, the kernel will oops when trying to
look up PHYSDEVPATH for the removed input device.

Fix this by deregistering the input device before closing the
connections.

Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'upstream-fixes' of master.kernel.org:/pub/scm/linux/kernel/git/jikos/hid</title>
<updated>2007-05-11T16:56:05Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2007-05-11T16:56:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5884c40668a928bba017eaf54e2eb3c01c8a98e6'/>
<id>urn:sha1:5884c40668a928bba017eaf54e2eb3c01c8a98e6</id>
<content type='text'>
* 'upstream-fixes' of master.kernel.org:/pub/scm/linux/kernel/git/jikos/hid:
  USB HID: hiddev - fix race between hiddev_send_event() and hiddev_release()
  HID: add hooks for getkeycode() and setkeycode() methods
  HID: switch to using input_dev-&gt;dev.parent
  USB HID: Logitech wheel 0x046d/0xc294 needs HID_QUIRK_NOGET quirk
  USB HID: usb_buffer_free() cleanup
  USB HID: report descriptor of Cypress USB barcode readers needs fixup
  Bluetooth HID: HIDP - don't initialize force feedback
  USB HID: update CONFIG_USB_HIDINPUT_POWERBOOK description
  HID: add input mappings for non-working keys on Logitech S510 remote
</content>
</entry>
<entry>
<title>[Bluetooth] Switch to using input_dev-&gt;dev.parent</title>
<updated>2007-05-11T06:45:03Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2007-05-09T07:15:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5be3946647424b08db0f62c545215cf506af8a52'/>
<id>urn:sha1:5be3946647424b08db0f62c545215cf506af8a52</id>
<content type='text'>
In preparation for struct class_device -&gt; struct device input core
conversion, switch to using input_dev-&gt;dev.parent when specifying
device position in sysfs tree.

Also, do not access input_dev-&gt;private directly, use helpers and
do not use kfree() on input device, use input_free_device() instead.

Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>Bluetooth HID: HIDP - don't initialize force feedback</title>
<updated>2007-05-09T00:52:51Z</updated>
<author>
<name>Jiri Kosina</name>
</author>
<published>2007-05-08T17:51:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3b180bff4c606b2596c40b26f85af6bc7d8cc50b'/>
<id>urn:sha1:3b180bff4c606b2596c40b26f85af6bc7d8cc50b</id>
<content type='text'>
The current implementation of force feedback for HID devices is
USB-transport only and therefore calling hid_ff_init() from hidp code is
not going to work (plus it creates unwanted dependency of hidp on usbhid).
Remove the hid_ff_init() until either the hid-ff is made
transport-independent, or at least support for bluetooth transport is
added.

Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bluetooth hid quirks: mightymouse quirk</title>
<updated>2007-03-29T15:22:24Z</updated>
<author>
<name>Jiri Kosina</name>
</author>
<published>2007-03-29T08:20:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cb3fecc2f29056e89658e7eb371e7f9be66cda6d'/>
<id>urn:sha1:cb3fecc2f29056e89658e7eb371e7f9be66cda6d</id>
<content type='text'>
I have a bugreport that scrollwheel of bluetooth version of apple
mightymouse doesn't work.  The USB version of mightymouse works, as there
is a quirk for handling scrollwheel in hid/usbhid for it.

Now that bluetooth git tree is hooked to generic hid layer, it could easily
use the quirks which are already present in generic hid parser, hid-input,
etc.

Below is a simple patch against bluetooth git tree, which adds quirk
handling to current bluetooth hidp code, and sets quirk flags for device
0x05ac/0x030c, which is the bluetooth version of the apple mightymouse.

Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[NET]: fix up misplaced inlines.</title>
<updated>2007-03-22T19:27:49Z</updated>
<author>
<name>Dave Jones</name>
</author>
<published>2007-03-22T19:27:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b6f99a211957910a07437f46ce54dcfb1755cf84'/>
<id>urn:sha1:b6f99a211957910a07437f46ce54dcfb1755cf84</id>
<content type='text'>
Turning up the warnings on gcc makes it emit warnings
about the placement of 'inline' in function declarations.
Here's everything that was under net/

Signed-off-by: Dave Jones &lt;davej@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[Bluetooth] Add open and close callbacks for HID device</title>
<updated>2007-02-26T19:42:39Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2007-02-17T22:58:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5ffd4620aba9e55656483ae1ef5c79ba81f5403'/>
<id>urn:sha1:f5ffd4620aba9e55656483ae1ef5c79ba81f5403</id>
<content type='text'>
The open and close callbacks for the HID device are not optional, but
for the Bluetooth HID report mode support it is enough to add empty
dummy callbacks.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>[Bluetooth] Add support for using the HID subsystem</title>
<updated>2007-02-26T19:42:38Z</updated>
<author>
<name>Marcel Holtmann</name>
</author>
<published>2007-02-17T22:58:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e1aaadd4d8162a2c33e41dd5a72234ea4d3b014f'/>
<id>urn:sha1:e1aaadd4d8162a2c33e41dd5a72234ea4d3b014f</id>
<content type='text'>
This patch extends the current Bluetooth HID support to use the new
HID subsystem and adds full report mode support.

Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
</content>
</entry>
<entry>
<title>[NET] BLUETOOTH: Fix whitespace errors.</title>
<updated>2007-02-11T07:19:20Z</updated>
<author>
<name>YOSHIFUJI Hideaki</name>
</author>
<published>2007-02-09T14:24:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8e87d14255acffeee36873de226dc25c11b5f46d'/>
<id>urn:sha1:8e87d14255acffeee36873de226dc25c11b5f46d</id>
<content type='text'>
Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
