From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Patrick Pedersen <ctx.xda@gmail.com>, jikos@kernel.org
Cc: benjamin.tissoires@redhat.com, jic23@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] HID: Add quirk for Lenovo Yoga 910 with ITE Chips
Date: Mon, 17 Jul 2017 12:58:14 -0700 [thread overview]
Message-ID: <1500321494.21514.29.camel@linux.intel.com> (raw)
In-Reply-To: <20170715122721.6908-1-ctx.xda@gmail.com>
On Sat, 2017-07-15 at 14:27 +0200, Patrick Pedersen wrote:
> As with previous generations of this device (see https://patchwork.ke
> rnel.org/patch/7887361/), the ITE
> HID Sensor Hub, responsible for the accelerometer and als sensor,
> requires a quirk entry.
I want to get rid of these quirks as this is now the defacto standard.
Can you try with this change without any quirk.
diff --git a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
index 16ade0a..1fb407f 100644
--- a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
+++ b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
@@ -110,6 +110,9 @@ static int _hid_sensor_power_state(struct
hid_sensor_common *st, bool state)
int report_val;
s32 poll_value = 0;
+ st->power_state.logical_minimum = 1;
+ st->report_state.logical_minimum = 1;
+
if (state) {
if (!atomic_read(&st->user_requested_state))
return 0;
Thanks,
Srinivas
>
> Without the entry, the Sensor Hub can't be accessed and the kernel
> fails to report any movements. As a result
> iio-sensor-proxy receives no new data.
>
> It shall additionally be noted that the i2c-hid 'sleep' bug (present
> since kernel ver. 4.3)
> still affects the driver. This means that the sensor hub will not
> report any movement, until
> the device is suspended and resumed.
>
> Signed-off-by: Patrick Pedersen <ctx.xda@gmail.com>
> ---
> drivers/hid/hid-ids.h | 1 +
> drivers/hid/hid-sensor-hub.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 4f9a3938189a..b427a0bcfbe8 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -565,6 +565,7 @@
> #define USB_DEVICE_ID_ITE_LENOVO_YOGA 0x8386
> #define USB_DEVICE_ID_ITE_LENOVO_YOGA2 0x8350
> #define USB_DEVICE_ID_ITE_LENOVO_YOGA900 0x8396
> +#define USB_DEVICE_ID_ITE_LENOVO_YOGA910 0x8186
>
> #define USB_VENDOR_ID_JABRA 0x0b0e
> #define USB_DEVICE_ID_JABRA_SPEAK_410 0x0412
> diff --git a/drivers/hid/hid-sensor-hub.c b/drivers/hid/hid-sensor-
> hub.c
> index 4ef73374a8f9..85b8425483bd 100644
> --- a/drivers/hid/hid-sensor-hub.c
> +++ b/drivers/hid/hid-sensor-hub.c
> @@ -820,6 +820,9 @@ static const struct hid_device_id
> sensor_hub_devices[] = {
> { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB,
> USB_VENDOR_ID_ITE,
> USB_DEVICE_ID_ITE_LENOVO_YOGA900),
> .driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
> + { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB,
> USB_VENDOR_ID_ITE,
> + USB_DEVICE_ID_ITE_LENOVO_YOGA910),
> + .driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
> { HID_DEVICE(HID_BUS_ANY, HID_GROUP_SENSOR_HUB,
> USB_VENDOR_ID_INTEL_0,
> 0x22D8),
> .driver_data = HID_SENSOR_HUB_ENUM_QUIRK},
next prev parent reply other threads:[~2017-07-17 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 12:27 [PATCH] HID: Add quirk for Lenovo Yoga 910 with ITE Chips Patrick Pedersen
2017-07-15 12:27 ` Patrick Pedersen
2017-07-15 14:29 ` Bastien Nocera
2017-07-15 17:52 ` Patrick Pedersen
2017-07-15 17:58 ` Bastien Nocera
[not found] ` <1500141490.2490.1.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2017-07-15 20:05 ` Patrick
2017-07-15 20:05 ` Patrick
2017-07-17 20:19 ` Srinivas Pandruvada
2017-07-17 23:22 ` Bastien Nocera
2017-07-16 7:39 ` Arek Burdach
[not found] ` <af21ea47-29df-443d-0a3d-5fc36d8cf119-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-07-16 10:23 ` Brian Masney
2017-07-16 10:23 ` Brian Masney
2017-07-17 6:26 ` Arek Burdach
2017-07-17 19:58 ` Srinivas Pandruvada [this message]
2017-08-01 12:23 ` Patrick
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=1500321494.21514.29.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=ctx.xda@gmail.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.