From: Elad Alfassa <elad@fedoraproject.org>
To: linux-iio@vger.kernel.org
Subject: Re: Kernel wishlist item: Better IIO API
Date: Sat, 21 Mar 2015 16:08:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20150321T160224-902@post.gmane.org> (raw)
In-Reply-To: 5469214A.9000203@kernel.org
Jonathan Cameron <jic23@...> writes:
[snip]
> > - on some variants, tweak the hysteresis [2] to trigger changes
> interesting one. - Note I personally don't mind fixes for firmware bugs
> in kernel - if there is a simple way of identifying parts with the problem.
Late followup, but (hopefully) better than nothing:
I have such device that has the hysteresis issue.
I don't know if there's a sure way to identify devices with this issue...
either automatically tweak the hysteresis when getting EAGAIN, or keep a
list of USB device IDs which require the hysteresis fix and apply them
automatically. Does this make sense?
I would really prefer that this sort of fix will live in the kernel and not
in any userspace utility that might want to use the sensors.
> > [2]:
https://github.com/hadess/iio-sensor-proxy/issues/1#issuecomment-54536393
prev parent reply other threads:[~2015-03-21 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 14:30 Kernel wishlist item: Better IIO API Bastien Nocera
2014-10-29 17:21 ` Lars-Peter Clausen
2014-10-29 17:33 ` Bastien Nocera
2014-10-29 17:39 ` Lars-Peter Clausen
2014-10-29 17:47 ` Bastien Nocera
2014-10-29 18:30 ` Lars-Peter Clausen
2014-11-03 23:01 ` Bastien Nocera
2014-11-04 7:52 ` Jonathan Cameron
2014-11-04 8:18 ` Daniel Baluta
2014-11-04 8:27 ` Bastien Nocera
2014-11-04 8:37 ` Daniel Baluta
2014-11-04 8:45 ` Bastien Nocera
2014-11-04 8:56 ` Daniel Baluta
2014-11-06 14:55 ` Bastien Nocera
2014-11-13 20:05 ` Bastien Nocera
2014-11-16 22:12 ` Jonathan Cameron
2014-11-16 22:42 ` Bastien Nocera
2014-11-17 13:34 ` Jonathan Cameron
2015-03-21 16:08 ` Elad Alfassa [this message]
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=loom.20150321T160224-902@post.gmane.org \
--to=elad@fedoraproject.org \
--cc=linux-iio@vger.kernel.org \
/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