<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/hid-sensor-ids.h, branch linux-3.8.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.8.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.8.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-12-12T15:49:10Z</updated>
<entry>
<title>HID: sensors: autodetect USB HID sensor hubs</title>
<updated>2012-12-12T15:49:10Z</updated>
<author>
<name>Alexander Holler</name>
</author>
<published>2012-12-09T11:44:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=83499b52c61f50292f0aae36499de8a8fc3e37c3'/>
<id>urn:sha1:83499b52c61f50292f0aae36499de8a8fc3e37c3</id>
<content type='text'>
It should not be necessary to add IDs for HID sensor hubs to lists in
hid-core.c and hid-sensor-hub.c. So instead of a whitelist, autodetect such USB
HID sensor hubs, based on a collection of type physical inside a useage page of
type sensor. If some sensor hubs stil must be usable as raw devices, a
blacklist might be created.

Signed-off-by: Alexander Holler &lt;holler@ahsoftware.de&gt;
Acked-by: "Pandruvada, Srinivas" &lt;srinivas.pandruvada@intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>HID: sensors: introduce sensor framework</title>
<updated>2012-09-06T18:13:13Z</updated>
<author>
<name>srinivas pandruvada</name>
</author>
<published>2012-09-05T12:56:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=401ca24fb34aee0cedf9c4fef361e533224f15a1'/>
<id>urn:sha1:401ca24fb34aee0cedf9c4fef361e533224f15a1</id>
<content type='text'>
Adding processing for HID Sensor usage table as defined by
HID 1.12, Request #: HUTRR39, dated 05 May, 2011.
This driver uses HID driver framework to register, send and
receive events.
This uses MFD framework, so that actual processing for a
specific usage id can be done in a different driver. For
example an accelerometer driver can be a separate driver and
use the interface provided by this driver to register for
events.

Signed-off-by: srinivas pandruvada &lt;srinivas.pandruvada@intel.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;
</content>
</entry>
</feed>
