mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Stephen Chandler Paul <thatslyude@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Srinivas Pandruvada <srinivas.pandruvada@intel.com>,
	Adam Williamson <awilliam@redhat.com>
Subject: Re: [PATCH] Add sensor hub quirk for ThinkPad Helix
Date: Thu, 03 Apr 2014 13:39:11 -0700	[thread overview]
Message-ID: <533DC6EF.9010909@linux.intel.com> (raw)
In-Reply-To: <1396556875-31108-1-git-send-email-thatslyude@gmail.com>


On 04/03/2014 01:27 PM, Stephen Chandler Paul wrote:
> Just like some of the other laptops/tablets on the market with ultrabook
> sensors, the ThinkPad Helix's sensor hub requires a special quirk in
> order for it to power on properly. Without it the sensors are detected
> by the kernel and set up as usual, but they won't output any data. This
> will also fix the sensors on any other laptops with the same model of
> sensor hub.
>
> Signed-off-by: Stephen Chandler Paul <thatslyude@gmail.com>
> ---
>   drivers/hid/hid-ids.h        | 3 ++-
>   drivers/hid/hid-sensor-hub.c | 7 +++++--
>   2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index bd22126..3312f1b5 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -455,7 +455,8 @@
>   
>   #define USB_VENDOR_ID_INTEL_0		0x8086
>   #define USB_VENDOR_ID_INTEL_1		0x8087
> -#define USB_DEVICE_ID_INTEL_HID_SENSOR	0x09fa
> +#define USB_DEVICE_ID_INTEL_HID_SENSOR_0	0x09fa
> +#define USB_DEVICE_ID_INTEL_HID_SENSOR_1	0x0a04
>   
>   #define USB_VENDOR_ID_STM_0             0x0483
>   #define USB_DEVICE_ID_STM_HID_SENSOR    0x91d1
> diff --git a/drivers/hid/hid-sensor-hub.c b/drivers/hid/hid-sensor-hub.c
> index 5182031..af8244b 100644
> --- a/drivers/hid/hid-sensor-hub.c
> +++ b/drivers/hid/hid-sensor-hub.c
> @@ -697,10 +697,13 @@ static void sensor_hub_remove(struct hid_device *hdev)
>   
>   static const struct hid_device_id sensor_hub_devices[] = {
>   	{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, USB_VENDOR_ID_INTEL_0,
> -			USB_DEVICE_ID_INTEL_HID_SENSOR),
> +			USB_DEVICE_ID_INTEL_HID_SENSOR_0),
>   			.driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
>   	{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, USB_VENDOR_ID_INTEL_1,
> -			USB_DEVICE_ID_INTEL_HID_SENSOR),
> +			USB_DEVICE_ID_INTEL_HID_SENSOR_0),
> +			.driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
> +	{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, USB_VENDOR_ID_INTEL_1,
> +			USB_DEVICE_ID_INTEL_HID_SENSOR_1),
>   			.driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
>   	{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB, USB_VENDOR_ID_STM_0,
>   			USB_DEVICE_ID_STM_HID_SENSOR),

Acked-by: Srinivas Pandruvada<srinivas.pandruvada@linux.intel.com>


Thanks,
Srinivas


  reply	other threads:[~2014-04-03 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 20:27 Stephen Chandler Paul
2014-04-03 20:39 ` Srinivas Pandruvada [this message]
2014-04-03 20:54 ` 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=533DC6EF.9010909@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=awilliam@redhat.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@intel.com \
    --cc=thatslyude@gmail.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

all inboxes | Powered by JetHome®