From: Gregor Boirie <gregor.boirie@parrot.com>
To: Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Irina Tirdea <irina.tirdea@intel.com>,
Cristina Moraru <cristina.moraru09@gmail.com>,
Daniel Baluta <daniel.baluta@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>
Subject: Re: [PATCH v3 2/3] iio:magnetometer:ak8975: mounting matrix support
Date: Tue, 29 Mar 2016 11:44:22 +0200 [thread overview]
Message-ID: <56FA4E76.1000406@parrot.com> (raw)
In-Reply-To: <56F947B4.3090503@kernel.org>
On 03/28/2016 05:03 PM, Jonathan Cameron wrote:
[snip...]
>
> Why is the sysfs interface specific to ak8975?
>>> AFAIK, this is just the first IIO driver implementation relying on floating
>>> point numbers. Should a single driver be enough to justify a "generic" API,
>>> I suppose code could be factored out in a similar way to over sampling rate
>>> support. People could call this on a per-driver basis.
>> Given it is an ABI, yes I think so. We don't want to end up with a
>> bunch of similar yet different interfaces.
>>
> Absolutely. Most interfaces get made up based on one implementation ;)
> A second is always nice, but here the interface is obvious enough we don't
> need to wait.
Right. I'll post a separate patch then.
>>>> Furthermore, why is it specific to magnetometer? Couldn't
>>>> accelerometers need the same thing? There's a thread discussing a
>>>> similar matrix on android-x86[1].
>>> Same may apply to gyro / accelero / imu and magnetometers at least.
>>> inv_mpu_core.c already implements such a rotation matrix exposed as 3x3 integers
>>> array. Should we be smart enough to keep this compatible with existing userspace
>>> apps ?
>> You have to maintain the ABI. If both interfaces can co-exist, then
>> you can have both and mark the old one as deprecated. In time we can
>> remove the old one.
> If you want to (or someone else does) it would be good to add the new abi to
> inv_mpu_core as well and indeed mark the old one as deprecated.
> The cost of keeping it is negligible, so we may never actually bother to
> remove it.
What's the better way to mark this as deprecated ? dev_warn() ?
__deprecated ?
Anything else ?
>>>>> diff --git a/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt b/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> index 34a3206..f936f86 100644
>>>>> --- a/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> +++ b/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> @@ -9,6 +9,7 @@ Optional properties:
>>>>>
>>>>> - gpios : should be device tree identifier of the magnetometer DRDY pin
>>>>> - vdd-supply: an optional regulator that needs to be on to provide VDD
>>>>> + - matrix: an optional 3x3 mounting rotation matrix
>>>> Perhaps "rotation-matrx" would be a better name in case there's ever
>>>> any other matrix needed.
>>> What about "mounting-matrix" ?
>> Sure.
> Works for me as well.
>> Rob
>> --
>> 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
>>
WARNING: multiple messages have this Message-ID (diff)
From: Gregor Boirie <gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
Peter Meerwald <pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>,
Geert Uytterhoeven
<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
Irina Tirdea
<irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Cristina Moraru
<cristina.moraru09-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Daniel Baluta
<daniel.baluta-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Julia Lawall <Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
Subject: Re: [PATCH v3 2/3] iio:magnetometer:ak8975: mounting matrix support
Date: Tue, 29 Mar 2016 11:44:22 +0200 [thread overview]
Message-ID: <56FA4E76.1000406@parrot.com> (raw)
In-Reply-To: <56F947B4.3090503-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On 03/28/2016 05:03 PM, Jonathan Cameron wrote:
[snip...]
>
> Why is the sysfs interface specific to ak8975?
>>> AFAIK, this is just the first IIO driver implementation relying on floating
>>> point numbers. Should a single driver be enough to justify a "generic" API,
>>> I suppose code could be factored out in a similar way to over sampling rate
>>> support. People could call this on a per-driver basis.
>> Given it is an ABI, yes I think so. We don't want to end up with a
>> bunch of similar yet different interfaces.
>>
> Absolutely. Most interfaces get made up based on one implementation ;)
> A second is always nice, but here the interface is obvious enough we don't
> need to wait.
Right. I'll post a separate patch then.
>>>> Furthermore, why is it specific to magnetometer? Couldn't
>>>> accelerometers need the same thing? There's a thread discussing a
>>>> similar matrix on android-x86[1].
>>> Same may apply to gyro / accelero / imu and magnetometers at least.
>>> inv_mpu_core.c already implements such a rotation matrix exposed as 3x3 integers
>>> array. Should we be smart enough to keep this compatible with existing userspace
>>> apps ?
>> You have to maintain the ABI. If both interfaces can co-exist, then
>> you can have both and mark the old one as deprecated. In time we can
>> remove the old one.
> If you want to (or someone else does) it would be good to add the new abi to
> inv_mpu_core as well and indeed mark the old one as deprecated.
> The cost of keeping it is negligible, so we may never actually bother to
> remove it.
What's the better way to mark this as deprecated ? dev_warn() ?
__deprecated ?
Anything else ?
>>>>> diff --git a/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt b/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> index 34a3206..f936f86 100644
>>>>> --- a/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> +++ b/Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>>>>> @@ -9,6 +9,7 @@ Optional properties:
>>>>>
>>>>> - gpios : should be device tree identifier of the magnetometer DRDY pin
>>>>> - vdd-supply: an optional regulator that needs to be on to provide VDD
>>>>> + - matrix: an optional 3x3 mounting rotation matrix
>>>> Perhaps "rotation-matrx" would be a better name in case there's ever
>>>> any other matrix needed.
>>> What about "mounting-matrix" ?
>> Sure.
> Works for me as well.
>> Rob
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
next prev parent reply other threads:[~2016-03-29 9:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:43 [PATCH v3 0/3] iio:magnetometer:ak8975: fix and enhancements Gregor Boirie
2016-03-17 16:43 ` Gregor Boirie
2016-03-17 16:43 ` [PATCH v3 1/3] iio:magnetometer:ak8975: fix missing regulator_disable Gregor Boirie
2016-03-17 16:43 ` Gregor Boirie
2016-03-20 11:07 ` Jonathan Cameron
2016-03-20 11:07 ` Jonathan Cameron
2016-03-17 16:43 ` [PATCH v3 2/3] iio:magnetometer:ak8975: mounting matrix support Gregor Boirie
2016-03-17 16:43 ` Gregor Boirie
2016-03-20 11:12 ` Jonathan Cameron
2016-03-20 11:12 ` Jonathan Cameron
2016-03-21 14:58 ` Rob Herring
2016-03-21 14:58 ` Rob Herring
2016-03-21 19:01 ` Jonathan Cameron
2016-03-21 19:01 ` Jonathan Cameron
2016-03-21 22:21 ` Gregor Boirie
2016-03-21 22:21 ` Gregor Boirie
2016-03-22 12:38 ` Rob Herring
2016-03-22 12:38 ` Rob Herring
2016-03-28 15:03 ` Jonathan Cameron
2016-03-28 15:03 ` Jonathan Cameron
2016-03-29 9:44 ` Gregor Boirie [this message]
2016-03-29 9:44 ` Gregor Boirie
2016-04-03 10:26 ` Jonathan Cameron
2016-04-03 10:26 ` Jonathan Cameron
2016-03-17 16:43 ` [PATCH v3 3/3] iio:magnetometer:ak8975: triggered buffer support Gregor Boirie
2016-03-17 16:43 ` Gregor Boirie
2016-03-20 11:21 ` Jonathan Cameron
2016-03-20 11:21 ` 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=56FA4E76.1000406@parrot.com \
--to=gregor.boirie@parrot.com \
--cc=Julia.Lawall@lip6.fr \
--cc=cristina.moraru09@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=irina.tirdea@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.