linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Jiri Kosina <jikos@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>
Cc: linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] more quirks for hid-sensor-hub
Date: Mon, 28 Nov 2016 08:53:17 -0800	[thread overview]
Message-ID: <1480351997.6544.236.camel@linux.intel.com> (raw)
In-Reply-To: <1480068224-32224-1-git-send-email-benjamin.tissoires@redhat.com>

Hi Benjamin,

On Fri, 2016-11-25 at 11:03 +0100, Benjamin Tissoires wrote:
> Hi Jiri,
> 
> here are 2 more quirks for the sensor-hub.
> 
> Srinivas, I am wondering if we can not detect those automatically.
> Looking at the report_fixup, it looks like the buggy report
> descriptors have
> a logical max of 5 (which would correspond to an enum of 0 to 5). But
> there
> are 6 fields in the enum, so that means the report descriptor is just
> wrong.
> 
> Given that Microsoft's driver requires a min of 1, wouldn't it be too
> much
> assumption to say that we need to fix the report descriptor anyway
> when we
> see a range of 0..5 instead of 1..6?

The problem is that they should have also changed logical minimum,
which vendors didn't do as Windows driver will always assume
enumeration base as 1.

As far as I can tell there was only Windows platform where base was 0,
but I am sure that Windows update and BIOS update would have fixed that
by now after 3 years.

I am in opinion to change this to match this with Windows driver, so
that we don't need this quirks. This is a small change in IIO sensor
hub driver.

If nobody has objection, I can submit a trivial change for this.

Thanks,
Srinivas


> 
> Cheers,
> Benjamin
> 
> Benjamin Tissoires (2):
>   HID: sensor-hub add quirk for Microsoft Surface 3
>   HID: sensor-hub: add quirk for Microchip MM7150
> 
>  drivers/hid/hid-sensor-hub.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 

  parent reply	other threads:[~2016-11-28 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 10:03 [PATCH 0/2] more quirks for hid-sensor-hub Benjamin Tissoires
2016-11-25 10:03 ` [PATCH 1/2] HID: sensor-hub add quirk for Microsoft Surface 3 Benjamin Tissoires
2016-11-25 12:16   ` Bastien Nocera
2016-11-25 12:59     ` Benjamin Tissoires
2016-11-25 10:03 ` [PATCH 2/2] HID: sensor-hub: add quirk for Microchip MM7150 Benjamin Tissoires
2016-11-28 13:33 ` [PATCH 0/2] more quirks for hid-sensor-hub Jiri Kosina
2016-11-28 16:53 ` Srinivas Pandruvada [this message]
2016-11-29  8:19   ` Benjamin Tissoires

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=1480351997.6544.236.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=benjamin.tissoires@redhat.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 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).