Re: [RFC] Issues with Zephyr Sensors API and ways to resolve them


Paul Sokolovsky
 

Hello,

On Fri, 26 Jan 2018 16:07:59 +0200
Paul Sokolovsky <Paul.Sokolovsky@linaro.org> wrote:

Hello Anas,

On Fri, 26 Jan 2018 00:36:17 +0000
"Nashif, Anas" <anas.nashif@intel.com> wrote:

I am fine with humidity unit change and now that I see the original
author’s reply I am more comfortable with this.\
Thanks, that sounds reassuring. I'll collect evidence on millimeter
-> meter switchover then ;-).
As a follow-up, the arguments for millimeter -> meter switchover were
posted at
https://github.com/zephyrproject-rtos/zephyr/issues/5693#issuecomment-361430731 ,
followed by PR https://github.com/zephyrproject-rtos/zephyr/pull/5927,
which is together with an earlier
https://github.com/zephyrproject-rtos/zephyr/pull/5825, by now have
been approved and merged.

So, I'd like to take another change to draw attentions that these are
backward-incompatible changes, but emphasize again that the reason
they're being made is to catch a chance to do that until this API is
widely used, and make sure that the LTS release (1.12 planned AFAIK)
has a clean, consistent, and confusion-free API.


The proposal to make changes to "struct sensor_value"
(https://github.com/zephyrproject-rtos/zephyr/issues/5692) didn't
receive any feedback, so apparently nothing should be done to it. My
plan is to add documentation to disambiguate its usage (in 1.11
timeframe), then as time permits, add a function which converts struct
sensor_value to a string without relying on floating-point arithmetics.


Thanks,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

Join devel@lists.zephyrproject.org to automatically receive all group messages.