linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	linux-iio@vger.kernel.org, Jonathan Cameron <jic23@cam.ac.uk>,
	Jiri Kosina <jkosina@suse.cz>,
	srinivas pandruvada <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH 1/2] HID: autodetect HID sensor hubs.
Date: Sun, 09 Dec 2012 12:37:53 +0100	[thread overview]
Message-ID: <50C47811.7010503@ahsoftware.de> (raw)
In-Reply-To: <1355015544-31579-1-git-send-email-holler@ahsoftware.de>

Am 09.12.2012 02:12, schrieb Alexander Holler:
> 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 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.

That patch didn't check if the device is a USB device and therfor
blutooth hid sensor hubs wouldn't still be handled as raw devices.

I send another patch 1/2 which checks the bus too.
Patch 2/2 still should be applied.

Regards,

Alexander

  parent reply	other threads:[~2012-12-09 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09  1:12 [PATCH 1/2] HID: autodetect HID sensor hubs Alexander Holler
2012-12-09  1:12 ` [PATCH 2/2] Revert "HID: sensors: add to special driver list" Alexander Holler
2012-12-09 11:37 ` Alexander Holler [this message]
2012-12-09 11:44   ` [PATCH 1/2] HID: autodetect USB HID sensor hubs Alexander Holler
2012-12-10 16:56     ` Pandruvada, Srinivas
2012-12-12  9:42     ` Jiri Kosina
2012-12-12 15:37       ` Pandruvada, Srinivas
2012-12-12 15:52         ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50C47811.7010503@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=jic23@cam.ac.uk \
    --cc=jkosina@suse.cz \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).