On Mon, 2014-08-25 at 20:04 +0300, Elad Alfassa wrote: > Hi Srinivas. > > I sent this to Reyad previously: > Here's the dmeg output: https://elad.fedorapeople.org/iio-debug/dmesg.txt > and here's the rdesc file: https://elad.fedorapeople.org/iio-debug/rdesc.txt > > It's indeed a usb hub, Bus 002 Device 003: ID 0483:91d1 STMicroelectronics > > So what happens is that when I use iio-sensor-proxy > (https://github.com/hadess/iio-sensor-proxy) it gets one read and gets > EAGAIN for all next reads. > So I kept it running, and while it was running I used cat on the raw > values, which were read without error. And when I ran the cat I saw > that iio-sensor-proxy managed to get another read, I want to make sure that this hub doesn't require some GPIO magic to wake up. So when you cat raw values, are they sane? Do they change when you move? Thanks, Srinivas > it happens every time I cat, ie. if I run cat in an endless loop while > iio-sensor-proxy is running then all the reads it tries to do succeed. > > I'll send you acpidump later. > > On Mon, Aug 25, 2014 at 7:56 PM, Srinivas Pandruvada > <srinivas.pandruvada@xxxxxxxxxxxxxxx> wrote: > > So I understand you are using buffered mode. When you get this error > > what happens if you just cat raw values? Do you get the same error? > > > > Also kernel debug logs as suggested by Reyad will be helpful to debug. > > Can you confirm that the sensor hub is an usb hub (with lsusb for > > vendor/product id) not i2c. > > Send me also output of acpidump (you can install acpidump in most of the > > distros) > > > > Thanks, > > Srinivas > > > > On Sat, 2014-08-23 at 18:19 +0300, Elad Alfassa wrote: > >> Hey Reyad. > >> > >> I don't see the > >> hid_sensor_hub:sensor_hub_report_fixup:540: hid-sensor-hub > >> 0003:0483:91D1.0003: No Enum quirks > >> line in my dmesg, so the patch did enable the enum quirk. > >> However, the symptoms are still the same. > >> > >> Thanks for your help. > >> > >> On Sat, Aug 23, 2014 at 6:14 PM, Reyad Attiyat <reyad.attiyat@xxxxxxxxx> wrote: > >> > Hey Elad, > >> > > >> > That is unfortunate that the patch doesn't work. If the patch did > >> > enable the enum quirk you should no longer see this line in your dmesg > >> > when hid-sensor-hub module is loaded: > >> > hid_sensor_hub:sensor_hub_report_fixup:540: hid-sensor-hub > >> > 0003:0483:91D1.0003: No Enum quirks > >> > > >> > I'll CC Srinivas for you to try and get additional help. > >> > > >> > Hey Srinivas, > >> > > >> > Elad has a hid sensor hub from STM that is failing to produce new > >> > data, any ideas what might cause this. He is getting a resource > >> > temporarily unavailable after only one value is read. I had thought it > >> > might need the quirk to change logical minimum to 1 for the state > >> > enums but it had no effect. Any other ideas? > >> > > >> > On Fri, Aug 22, 2014 at 4:34 PM, Elad Alfassa <elad@xxxxxxxxxxxxxxxxx> wrote: > >> >> Hey Reyad. > >> >> > >> >> Unfortunately, this patch does not fix the issue. > >> >> The symptoms are exactly like before. > >> >> > >> >> Thanks, > >> >> -- > >> >> -Elad Alfassa. > >> > >> > >> > > > > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
