From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "nish.aravamudan@gmail.com" <nish.aravamudan@gmail.com>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"jic23@kernel.org" <jic23@kernel.org>,
"cmo@melexis.com" <cmo@melexis.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"jikos@kernel.org" <jikos@kernel.org>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>
Subject: Re: iio/hid-sensor-accel-3d: no output from /dev/iio:device*?
Date: Fri, 18 Dec 2015 01:11:01 +0000 [thread overview]
Message-ID: <1450400953.5427.18.camel@intel.com> (raw)
In-Reply-To: <CAOhV88OinTE31-qp1vh-4XHT-TqMTTOYwHiLk0yptg0prwetjw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2500 bytes --]
On Thu, 2015-12-17 at 17:08 -0800, Nish Aravamudan wrote:
> On Thu, Dec 17, 2015 at 5:00 PM, Pandruvada, Srinivas
> <srinivas.pandruvada@intel.com> wrote:
> > Hi Andy,
> >
> > As per Nish these patches are impacting sensors on Yoga.
> > https://lkml.org/lkml/2015/11/30/441
>
> To be clear, without that series, the touchpad and touchscreen on the
> Yoga 900 don't work at all. So they are necessary for functioning. I
> don't know (I will test it now), if removing the series makes the IIO
> sensors work properly in /dev/.
This is important to know before we take Andy's time.
Thanks,
Srinivas
>
> -Nish
>
> > On Thu, 2015-12-17 at 16:51 -0800, Srinivas Pandruvada 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.
> > >
> > > 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.
> > >
> > > Thanks,
> > > Srinivas
> > >
> > > > ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-12-18 1:11 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 [this message]
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
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=1450400953.5427.18.camel@intel.com \
--to=srinivas.pandruvada@intel.com \
--cc=andriy.shevchenko@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).