From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Crt Mori <cmo@melexis.com>
Subject: Re: iio/hid-sensor-accel-3d: no output from /dev/iio:device*?
Date: Thu, 17 Dec 2015 17:16:30 -0800 [thread overview]
Message-ID: <1450401390.5427.22.camel@linux.intel.com> (raw)
In-Reply-To: <CAOhV88MYvtD508toqR2KLOdpSq_tU=kwQKOf252t1sdiK4SviQ@mail.gmail.com>
On Thu, 2015-12-17 at 17:07 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 4:51 PM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > On Thu, 2015-12-17 at 15:38 -0800, Nish Aravamudan wrote:
> > > [Starting a new thread from https://lkml.org/lkml/2015/12/15/663,
> > > as
> > > now my laptop is displaying values in the sysfs *raw* files.]
> > >
> > > So I'm trying to understand exactly how the hid-sensor-accel-3d
> > > driver works.
> > >
> > > If I turn up debugging, when I `cat
> > > /sys/bus/iio/devices/device*/*raw*`, I see "iio iio:device3:
> > > accel_3d_proc_event" and I think that means that
> > > hid_sensor_push_data() is getting called.
> > >
> > > But read()'s on /dev/iio:device3 never produces anything, which
> > > is
> > > what iio-sensor-proxy uses to translate events to dbus.
> > >
> > > Is it expected that the dev-node is "silent"? Just trying to
> > > understand if an extension to the driver to support a chardev
> > > based
> > > output is appropriate, or if iio-sensor-proxy needs to be changed
> > > to
> > > handle this device.
> >
> > You are saying there is some regression. This used to work and now
> > it
> > doesn't work. Is raw values are displayed correctly, when you do
> > "cat"?
> > If cat of raw values is working then power on of sensors is
> > working.
>
> Sorry, I was unclear. I don't know if this is a regression. I can try
> going back to an older kernel to see if the /dev/iio:device* files
> produced any output.
>
> Yes, the *raw* files in sysfs are producing output, that is changing
> as I move the laptop around. But the /dev/ nodes seem to produce no
> output (I'm still reading through the driver code to understand where
> that data should be coming from.
>
> > Turn on HID debug prints. If it is regression we can do git bisect.
> > Any ACPI or PM changes can break this. Usually there will be GPIOs
> > which will be involved in power on, where ACPI comes into play.
> > This
> > will be done by i2c-hid. There are some prints in i2c-hid which can
> > be
> > enabled also.
>
> Ok, I will try this, as well.
>
Try increasing in_accel_sampling_frequency
echo 100 > in_accel_sampling_frequency
Adjust hysteresis to a low value
echo 0 > in_accel_hysteresis
These values are very vendor specific.
Thanks,
Srinivas
> -Nish
next prev parent reply other threads:[~2015-12-18 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 23:38 iio/hid-sensor-accel-3d: no output from /dev/iio:device*? Nish Aravamudan
2015-12-18 0:51 ` Srinivas Pandruvada
2015-12-18 1:00 ` Pandruvada, Srinivas
2015-12-18 1:08 ` Nish Aravamudan
2015-12-18 1:11 ` Pandruvada, Srinivas
2015-12-18 2:33 ` Nish Aravamudan
2015-12-18 2:50 ` Pandruvada, Srinivas
2015-12-18 3:06 ` Nish Aravamudan
2015-12-18 16:58 ` Pandruvada, Srinivas
2015-12-18 1:07 ` Nish Aravamudan
2015-12-18 1:16 ` Srinivas Pandruvada [this message]
2015-12-18 1:59 ` Nish Aravamudan
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=1450401390.5427.22.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=cmo@melexis.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=pmeerw@pmeerw.net \
/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).