linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* iio/hid-sensor-accel-3d: no output from /dev/iio:device*?
@ 2015-12-17 23:38 Nish Aravamudan
  2015-12-18  0:51 ` Srinivas Pandruvada
  0 siblings, 1 reply; 12+ messages in thread
From: Nish Aravamudan @ 2015-12-17 23:38 UTC (permalink / raw)
  To: Jiri Kosina
  Cc: Jonathan Cameron, Srinivas Pandruvada, Hartmut Knaack,
	Lars-Peter Clausen, Peter Meerwald, linux-input, linux-iio,
	linux-kernel, Crt Mori

[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.

-Nish

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2015-12-18 16:58 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2015-12-18  1:59       ` Nish Aravamudan

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).