From: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Cc: Gregor Boirie <gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org>, "linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Samu Onkalo <samu.onkalo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: [PATCH] iio: document bindings for mounting matrixes Date: Mon, 29 Aug 2016 18:24:58 +0100 [thread overview] Message-ID: <ec3fb3a4-1f8e-1eae-e4b7-42f8eb16fe25@kernel.org> (raw) In-Reply-To: <CACRpkda-Mz0wOAXx4uoZ43OCVw0U_E0+iCrboUO_7keYV2scBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> On 25/08/16 23:04, Linus Walleij wrote: > On Wed, Aug 24, 2016 at 11:29 PM, Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote: >> Gregor: >>> So I feel like we should keep away from any temptation to define the coordinates >>> system too strictly. >>> I also think of systems composed of multiple hardware parts with sensors >>> scattered all over them. What would be the right "device/main hardware" reference >>> frame definition in these cases ? >>> As this is product specific, I feel like "device/main hardware" reference frame >>> definition should be left to the "board/main hardware/device..." implementor's >>> choice. >> >> Flexible is good, but I think we should define a base rule for the chips frame >> of reference and fix up any that disagree (which is nasty ABI breakage :( >> Trivial choice of either right handed or left handed frame might be all we >> define in general. Useful to define consistent frames for device types that >> are common perhaps as well. (such as the screen ones Linus has here). > > Admittedly I come from the mobile phone industry. > > So these frames of reference is not cooked up by me, I installed the > Android app "Sensors test" to test two devices relative the world, so this > is the frame of reference used by all mobile phones and tablets on the > planet (I hardly think iPhone deviates). > > I would be happy to write explicitly that for human interaction devices > with screens that frame of reference should always be assumed, but for > other uses and device types other frames of reference may apply, would > you agree? Absolutely. The references Gregor gave might also be worth mentioning as they provide pretty pictures etc ;) Jonathan > > Yours, > Linus Walleij > -- > 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 > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <jic23@kernel.org> To: Linus Walleij <linus.walleij@linaro.org> Cc: Gregor Boirie <gregor.boirie@parrot.com>, "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>, Sebastian Reichel <sre@kernel.org>, Samu Onkalo <samu.onkalo@intel.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org> Subject: Re: [PATCH] iio: document bindings for mounting matrixes Date: Mon, 29 Aug 2016 18:24:58 +0100 [thread overview] Message-ID: <ec3fb3a4-1f8e-1eae-e4b7-42f8eb16fe25@kernel.org> (raw) In-Reply-To: <CACRpkda-Mz0wOAXx4uoZ43OCVw0U_E0+iCrboUO_7keYV2scBw@mail.gmail.com> On 25/08/16 23:04, Linus Walleij wrote: > On Wed, Aug 24, 2016 at 11:29 PM, Jonathan Cameron <jic23@kernel.org> wrote: >> Gregor: >>> So I feel like we should keep away from any temptation to define the coordinates >>> system too strictly. >>> I also think of systems composed of multiple hardware parts with sensors >>> scattered all over them. What would be the right "device/main hardware" reference >>> frame definition in these cases ? >>> As this is product specific, I feel like "device/main hardware" reference frame >>> definition should be left to the "board/main hardware/device..." implementor's >>> choice. >> >> Flexible is good, but I think we should define a base rule for the chips frame >> of reference and fix up any that disagree (which is nasty ABI breakage :( >> Trivial choice of either right handed or left handed frame might be all we >> define in general. Useful to define consistent frames for device types that >> are common perhaps as well. (such as the screen ones Linus has here). > > Admittedly I come from the mobile phone industry. > > So these frames of reference is not cooked up by me, I installed the > Android app "Sensors test" to test two devices relative the world, so this > is the frame of reference used by all mobile phones and tablets on the > planet (I hardly think iPhone deviates). > > I would be happy to write explicitly that for human interaction devices > with screens that frame of reference should always be assumed, but for > other uses and device types other frames of reference may apply, would > you agree? Absolutely. The references Gregor gave might also be worth mentioning as they provide pretty pictures etc ;) Jonathan > > Yours, > Linus Walleij > -- > 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 >
next prev parent reply other threads:[~2016-08-29 17:24 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-24 10:17 [PATCH] iio: document bindings for mounting matrixes Linus Walleij 2016-07-24 10:17 ` Linus Walleij [not found] ` <1469355434-17043-1-git-send-email-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-07-24 19:03 ` Jonathan Cameron 2016-07-24 19:03 ` Jonathan Cameron [not found] ` <06168d06-b609-a0ec-945e-aa36a4dbe795-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2016-07-25 8:42 ` Linus Walleij 2016-07-25 8:42 ` Linus Walleij 2016-07-25 12:48 ` Gregor Boirie 2016-07-25 12:48 ` Gregor Boirie [not found] ` <57960AAF.1060103-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org> 2016-07-25 13:57 ` Linus Walleij 2016-07-25 13:57 ` Linus Walleij 2016-07-26 19:07 ` Rob Herring 2016-07-26 19:07 ` Rob Herring 2016-07-26 21:01 ` Jonathan Cameron 2016-07-26 21:01 ` Jonathan Cameron 2016-08-11 11:33 ` Linus Walleij 2016-08-11 11:33 ` Linus Walleij [not found] ` <CACRpkdY0gCLKD3rmiYuFgWSYOe6dtUaBeRi1ns-UFF=AspntFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-08-15 14:58 ` Jonathan Cameron 2016-08-15 14:58 ` Jonathan Cameron [not found] ` <c8e83cf2-f9dc-0bc9-fcde-326b05ee290b-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2016-08-15 18:47 ` Linus Walleij 2016-08-15 18:47 ` Linus Walleij 2016-08-24 13:18 ` Gregor Boirie 2016-08-24 13:18 ` Gregor Boirie [not found] ` <57BD9EB6.1090504-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org> 2016-08-24 21:29 ` Jonathan Cameron 2016-08-24 21:29 ` Jonathan Cameron [not found] ` <067a4882-c6f2-5994-e3ce-100e317ed121-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2016-08-25 12:28 ` Gregor Boirie 2016-08-25 12:28 ` Gregor Boirie 2016-08-25 22:04 ` Linus Walleij 2016-08-25 22:04 ` Linus Walleij [not found] ` <CACRpkda-Mz0wOAXx4uoZ43OCVw0U_E0+iCrboUO_7keYV2scBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-08-29 17:24 ` Jonathan Cameron [this message] 2016-08-29 17:24 ` Jonathan Cameron 2016-08-21 15:56 ` Jonathan Cameron 2016-08-21 15:56 ` Jonathan Cameron [not found] ` <ab89a386-dfca-bbc3-3dec-613d32d374a5-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2016-08-25 21:56 ` Linus Walleij 2016-08-25 21:56 ` Linus Walleij [not found] ` <CACRpkdbA=qZO9M=nc2mUK7Sg5ZdOzcH=x0kUQ004_+uVTQ8tCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-08-29 17:31 ` Jonathan Cameron 2016-08-29 17:31 ` 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=ec3fb3a4-1f8e-1eae-e4b7-42f8eb16fe25@kernel.org \ --to=jic23-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org \ --cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=samu.onkalo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \ --cc=sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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: linkBe 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.