linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Gregor Boirie <gregor.boirie@parrot.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 4/5] iio:magnetometer:ak8975: mounting matrix support
Date: Tue, 15 Mar 2016 21:56:14 +0000	[thread overview]
Message-ID: <56E884FE.90005@kernel.org> (raw)
In-Reply-To: <56E6F2BA.5010101@parrot.com>

On 14/03/16 17:19, Gregor Boirie wrote:
> On 03/09/2016 09:46 PM, Jonathan Cameron wrote:
> 
> [snip...]
>> Definitely needs ABI docs in Documentation/ABI/testing/sysfs-bus-iio
>> as well. We need the reference directions to be well specified as
>> well - how do we define the main hardware orientation?  on yours presumably
>> the usual approach of using the screen is irrelevant so that definition
>> could be a little 'interesting' to write down?
>>> The standard orientation for us is defined with respect to the drone's head
>>> and the propellers plane, which does not suit the nominal use cases indeed...
>>> Although it really deserves some more detailed documentation, I wonder if the
>>> question is relevant.
>>> Given that the DTS is board specific (correct me if I'm wrong), why not
>>> consider the reference orientation as board specific as well (and make the
>>> whole thing implicit) ?
>> I think that is fine for your sort of usecase - though might be nice to keep
>> a bit of documentation somewhere (perhaps as comments in the DTS), or perhaps
>> more centrally - would be nice for userspace libraries if at least all aircraft
>> had a similar 'default orientation'.
> As you said earlier, things are never that simple. The standard orientation
> may vary with types of UAVs (quad-rotor, fixed wings, bizarre home made UFOs...)
Sure, but let's document what we can so at least some cases are covered
>> For the more 'standard' device with a screen I think we would want to standardise
>> if at all possible.  Most hand held devices have a 'natural' orientation
>> (front facing camera at the top for example).  In those cases we are basically looking
>> at whether the sensor is mounted on the back or the front of the main circuit board and
>> then of course it can be at any rotation in plane but typically is at 90 degrees
>> (hence the inv mpu limitations)
>>
>> I'm guessing there are existing userspace mappings for this.  Perhaps in the Gnome
>> sensors stuff?
> [snip...]
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2016-03-15 21:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 10:44 [PATCH v2 0/5] iio:magnetometer:ak8975: fix and enhancements Gregor Boirie
2016-03-03 10:44 ` [PATCH v2 1/5] iio:magnetometer:ak8975: fix uninitialized chipset Gregor Boirie
2016-03-05 15:24   ` Jonathan Cameron
2016-03-03 10:44 ` [PATCH v2 2/5] iio:magnetometer:ak8975: remove unused field Gregor Boirie
2016-03-05 15:25   ` Jonathan Cameron
2016-03-03 10:44 ` [PATCH v2 3/5] iio:magnetometer:ak8975: power regulator support Gregor Boirie
2016-03-05 15:26   ` Jonathan Cameron
2016-03-03 10:44 ` [PATCH v2 4/5] iio:magnetometer:ak8975: mounting matrix support Gregor Boirie
2016-03-05 15:36   ` Jonathan Cameron
2016-03-09 10:56     ` Gregor Boirie
2016-03-09 20:46       ` Jonathan Cameron
2016-03-10  2:15         ` Rob Herring
2016-03-12  9:44           ` Jonathan Cameron
2016-03-14 17:19         ` Gregor Boirie
2016-03-15 21:56           ` Jonathan Cameron [this message]
2016-03-17 16:15             ` Gregor Boirie
2016-03-03 10:44 ` [PATCH v2 5/5] iio:magnetometer:ak8975: triggered buffer support Gregor Boirie
2016-03-05 15:45   ` Jonathan Cameron

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=56E884FE.90005@kernel.org \
    --to=jic23@kernel.org \
    --cc=gregor.boirie@parrot.com \
    --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;
as well as URLs for NNTP newsgroup(s).