From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932415AbbLQXiZ (ORCPT ); Thu, 17 Dec 2015 18:38:25 -0500 Received: from mail-yk0-f175.google.com ([209.85.160.175]:35149 "EHLO mail-yk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752871AbbLQXiX (ORCPT ); Thu, 17 Dec 2015 18:38:23 -0500 MIME-Version: 1.0 Date: Thu, 17 Dec 2015 15:38:22 -0800 Message-ID: Subject: iio/hid-sensor-accel-3d: no output from /dev/iio:device*? From: Nish Aravamudan To: Jiri Kosina Cc: Jonathan Cameron , Srinivas Pandruvada , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald , linux-input@vger.kernel.org, linux-iio@vger.kernel.org, "linux-kernel@vger.kernel.org" , Crt Mori Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [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