mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arek Burdach <arek.burdach@gmail.com>
To: Patrick Pedersen <ctx.xda@gmail.com>, jikos@kernel.org
Cc: benjamin.tissoires@redhat.com, jic23@kernel.org,
	srinivas.pandruvada@linux.intel.com, 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: Sun, 16 Jul 2017 09:39:19 +0200	[thread overview]
Message-ID: <af21ea47-29df-443d-0a3d-5fc36d8cf119@gmail.com> (raw)
In-Reply-To: <20170715122721.6908-1-ctx.xda@gmail.com>

Hi Patrick,

On 15.07.2017 14:27, Patrick Pedersen wrote:
> 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.
>
Do you have workaround for that? In my case suspending and resuming 
doesn't help. Sensor reporting is backing to work in unpredictable way. 
What I've tested:

- kernel v4.13-rc1 with your patch applied
- watch -n1 cat /sys/bus/iio/devices/iio\:device*/*_raw <- value not 
changing
- suspend
- resume
- watch -n1 cat /sys/bus/iio/devices/iio\:device*/*_raw <- still not 
changing

If you have some workaround scenario please add it to bug reported be 
me: https://bugzilla.kernel.org/show_bug.cgi?id=195681

Cheers,
Arek

  parent reply	other threads:[~2017-07-16  7:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 12:27 Patrick Pedersen
2017-07-15 14:29 ` Bastien Nocera
     [not found]   ` <CAA7d1im1hxM13SrsF5pQsJmtugjT2CJZnJdmbC2KxL5_QPXd_Q@mail.gmail.com>
2017-07-15 17:58     ` Bastien Nocera
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 [this message]
2017-07-16 10:23   ` Brian Masney
2017-07-17  6:26     ` Arek Burdach
2017-07-17 19:58 ` Srinivas Pandruvada
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=af21ea47-29df-443d-0a3d-5fc36d8cf119@gmail.com \
    --to=arek.burdach@gmail.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 \
    --cc=srinivas.pandruvada@linux.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
Powered by JetHome