From: Jonathan Cameron <jic23@cam.ac.uk>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
linux-iio@vger.kernel.org, jic23@kernel.org, lars@metafoo.de
Subject: Re: iio: v2, add support for HMC5883/HMC5883L to HMC5843 driver
Date: Wed, 09 May 2012 15:20:12 +0100 [thread overview]
Message-ID: <4FAA7D1C.6060401@cam.ac.uk> (raw)
In-Reply-To: <alpine.DEB.2.01.1205091524570.5308@pmeerw.net>
On 5/9/2012 2:33 PM, Peter Meerwald wrote:
> Hello,
>
>>> the driver has a severe limitation: X/Y/Z must ALL be read to allow new
>>> data to become available (the device goes into a locked state until all
>>> are read)
>> Thats a limitation comming from the data sheet right?
> yes, it affects all devices (hmc5843/5883/5883l)
>
>> Are you suggesting a read all and report only requested?
>> to work round that.
> probably yes
>
> I brought it up to see if there are ideas for a solution; maybe the issue
> is more common and this should be solved at iio core level?
>
> with individual reads for X/Y/Z there is no guarantee that all values come
> from the same measurement cycle ('atomic read')
>
> the hmc58x3 'solves' this with the lock logic and introduces another issue
>
> maybe iio should only allow reads to all data elements at once?
If you need to do that, use buffered access rather than sysfs. Anything
else
makes for fiddly and hard to generalize interfaces I'm afraid.
It is indeed a common situation. Actually I much prefer this to the
alternative
of getting an inconsistent set depending on precise read times.
Jonathan
prev parent reply other threads:[~2012-05-09 14:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 22:19 iio: v2, add support for HMC5883/HMC5883L to HMC5843 driver Peter Meerwald
2012-05-08 22:19 ` [PATCH 1/8] iio: fix access to hmc5843 private data Peter Meerwald
2012-05-09 9:59 ` Shubhrajyoti Datta
2012-05-10 14:19 ` Shubhrajyoti Datta
2012-05-10 9:10 ` Jonathan Cameron
2012-05-10 13:18 ` Peter Meerwald
2012-05-08 22:20 ` [PATCH 2/8] iio: change strict_strtoul() to kstrtoul() in hmc5843 Peter Meerwald
2012-05-10 9:11 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 3/8] iio: rename and prefix CONSTANTs to distinguish between HMC5843 and HMC5883 Peter Meerwald
2012-05-10 12:11 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 4/8] iio: rework sampling rate setting in hmc5843 Peter Meerwald
2012-05-10 12:13 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 5/8] iio: add check for measurement configuration value passed to hmc5843 Peter Meerwald
2012-05-10 12:15 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 6/8] iio: cleanup and move comments in hmc5843 Peter Meerwald
2012-05-10 12:18 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 7/8] iio: rename function/data to consistently start with hmc5843_ Peter Meerwald
2012-05-10 12:18 ` Jonathan Cameron
2012-05-08 22:20 ` [PATCH 8/8] iio: add support for hmc5883/hmc5883l to hmc5843 magnetometer driver Peter Meerwald
2012-05-10 12:29 ` Jonathan Cameron
2012-05-09 9:55 ` iio: v2, add support for HMC5883/HMC5883L to HMC5843 driver Shubhrajyoti Datta
2012-05-09 13:33 ` Peter Meerwald
2012-05-09 14:20 ` Jonathan Cameron [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=4FAA7D1C.6060401@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=omaplinuxkernel@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).