From: Ritesh Raj Sarraf <rrs@researchut.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Song Hongyan <hongyan.song@intel.com>,
linux-iio <linux-iio@vger.kernel.org>
Cc: stable@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3
Date: Tue, 04 Apr 2017 00:44:18 +0530 [thread overview]
Message-ID: <1491246858.17255.10.camel@researchut.com> (raw)
In-Reply-To: <1491059661.30396.37.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Adding Stable, LKML and IIO MLs.
Hello Hongyan,
Do you have any feedback ? With the bisected commit reverted, I've been
successfully running the machine without any issues.
Ritesh
On Sat, 2017-04-01 at 08:14 -0700, Srinivas Pandruvada wrote:
> Hello Hongyan,
>
> Can you check the findings of Ritesh?
>
> Thanks,
> Srinivas
>
> On Sat, 2017-04-01 at 14:07 +0530, Ritesh Raj Sarraf wrote:
> > Hello Srinivas,
> >
> > With the Linux 4.10.7 release, I have encountered a regression
> > introduced on my
> > Lenovo Yoga 2 13, for the ITE Rotation Sensor.
> >
> >
> > rrs@learner:~$ lsusb
> > Bus 001 Device 002: ID 8087:8000 Intel Corp.
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 002 Device 006: ID 048d:8350 Integrated Technology Express, Inc.
> > Bus 002 Device 005: ID 0bda:b728 Realtek Semiconductor Corp.
> > Bus 002 Device 004: ID 04f2:b40f Chicony Electronics Co., Ltd
> > Bus 002 Device 003: ID 04f3:0303 Elan Microelectronics Corp.
> > Bus 002 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129
> > Card Reader
> > Controller
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > 2017-04-01 / 14:04:49 ♒♒♒ ☺
> >
> >
> > The ITE sensors do not feed any data on the 4.10.7 kernel. Reverting
> > back to
> > 4.10.5, everything works back.
> >
> >
> > After a git bisect, the culprit reported is:
> >
> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
> > [6c2aab07d12436af1cd8d9ac1d117a442cc91eec] iio: hid-sensor-trigger:
> > Change get
> > poll value function order to avoid sensor properties losing after
> > resume from S3
> > 1
> >
> > Can you please review my findings to confirm that it really is a
> > regression bug
> > ?
> >
> >
> > Thanks,
> > Ritesh
> >
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2017-04-03 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1491035833.10386.1.camel@researchut.com>
[not found] ` <1491059661.30396.37.camel@linux.intel.com>
2017-04-03 19:14 ` Ritesh Raj Sarraf [this message]
2017-04-05 0:44 ` [STABLE REGRESSION] iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3 Srinivas Pandruvada
2017-04-05 1:12 ` Song, Hongyan
2017-04-05 10:51 ` Ritesh Raj Sarraf
2017-04-05 15:35 ` Srinivas Pandruvada
2017-04-06 4:58 ` Song, Hongyan
2017-04-06 5:18 ` Srinivas Pandruvada
2017-04-05 4:59 ` Song, Hongyan
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=1491246858.17255.10.camel@researchut.com \
--to=rrs@researchut.com \
--cc=hongyan.song@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@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