From: Ritesh Raj Sarraf <rrs@researchut.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: sensor-hub: Move the memset to sensor_hub_get_feature()
Date: Wed, 28 Dec 2016 23:23:18 +0530 [thread overview]
Message-ID: <1482947598.21657.1.camel@researchut.com> (raw)
In-Reply-To: <1482946633.12558.1.camel@researchut.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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.
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlhj/A8ACgkQpjpYo/Lh
dWmrVBAAmvevxwMKsO9+rcOxa4QyuV1m8dX/j13eX3pz/qPQAP+sn/AeIS7B3HVT
EdbSTAzAPEJGxR3KLxYP4+3L30RO4V94T371h9INujJWAFbu29J2p2WiUtTWtpLI
ZtBrS4x7pPRUdn6io9AMKfGFSZdDoskfCHbCC/lUN05zXJnKZRYXSRispSJ6c02F
f9A8zwaTGC+lrP3uLJ/0l9nPa545ivyCPYyfBrbpBedV/9NO2YfPbGxGETpUOEt+
7YCxC2W/mVVmbm5bdAbZ8EwoWsl/AWuy93/A5AAse1LF1o//eZXc8Dry0VKzkm8t
lq/yZYGwKLgT8vgQwoTyNSO19o+P96NY/WkiOxTCj4ZMHFAXz1+v1FWKDzwKlaPc
Egyw1Go3Rd0xciZBmZeru6szmKL+daJBKhZSHyoMjYVtaxp49EtsDjkv7lhsUvWI
hj2ctO8vLo1UNq+V26icP2ofaWuLpjd7hx9jTt5PhEEmK0yus3HnI0S417FMlDvU
dqpJKLRTAdO6sGYyVuMs9U/7Q5mRAzEgeOHlLGkghCfH+163HPCY4uNq4QZ9wj5Y
XioSJ/HjFW6R0Mxyr9jI5WcFQ82QcGsoOzocyjbxYWK7SFknRtkIDt3fQaEqvCSq
9tATFHcoUIQXCrk00uOj2ZYsBqlhN3PFaqJm9irSJdWpdnqUNtE=
=5uwZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-12-28 17:54 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 [this message]
2016-12-29 17:22 ` Srinivas Pandruvada
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=1482947598.21657.1.camel@researchut.com \
--to=rrs@researchut.com \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).