From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rrs@researchut.com, linux-iio <linux-iio@vger.kernel.org>
Subject: Re: sensor-hub: Move the memset to sensor_hub_get_feature()
Date: Thu, 29 Dec 2016 09:22:07 -0800 [thread overview]
Message-ID: <1483032127.27585.13.camel@linux.intel.com> (raw)
In-Reply-To: <1482947598.21657.1.camel@researchut.com>
On Wed, 2016-12-28 at 23:23 +0530, Ritesh Raj Sarraf wrote:
> On Wed, 2016-12-28 at 23:07 +0530, Ritesh Raj Sarraf wrote:
> >
> > On Wed, 2016-12-28 at 22:54 +0530, Ritesh Raj Sarraf wrote:
> > >
> > > Device4, for which there are no x, y, z attributes, reports the
> > > name
> > > "dev_rotation".
> > > Even for the other devices, I see no change in the reported
> > > values.
> > On the 4.8 kernel, the values do change. The iio-sensor-proxy still
> > does not
> > do
> > the rotation.
> For the sake of completeness, I booted up iio-sensor-proxy (with
> latest patch
> from today), on both 4.8 and 4.9.
>
> With 4.8, I am reliably able to see screen rotation. And for the
> record, on 4.8,
> the memset change is the old one.
>
> With 4.9, nothing. Which may be expected given there were no data
> seen with
> those device attributes (when using cat).
>
>
> If you need more information, please tell me.
I tried on couple of systems with the patch. It seems to fix the issue.
It is possible some low level power related changes have impacted this.
Can you do bisect? I suggest just try 4.9-rc1. I think it will not work
there probably.
Thanks,
Srinivas
>
>
next prev parent reply other threads:[~2016-12-29 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 11:38 sensor-hub: Move the memset to sensor_hub_get_feature() Ritesh Raj Sarraf
2016-12-28 13:23 ` Ritesh Raj Sarraf
2016-12-28 16:48 ` Srinivas Pandruvada
2016-12-28 17:24 ` Ritesh Raj Sarraf
2016-12-28 17:37 ` Ritesh Raj Sarraf
2016-12-28 17:53 ` Ritesh Raj Sarraf
2016-12-29 17:22 ` Srinivas Pandruvada [this message]
2016-12-29 17:31 ` Ritesh Raj Sarraf
2016-12-30 10:47 ` Ritesh Raj Sarraf
2016-12-30 16:50 ` Srinivas Pandruvada
2016-12-31 12:55 ` Ritesh Raj Sarraf
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=1483032127.27585.13.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=rrs@researchut.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;
as well as URLs for NNTP newsgroup(s).