[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210106212353.951807-1-jbhayana@google.com>
Date: Wed, 6 Jan 2021 21:23:53 +0000
From: Jyoti Bhayana <jbhayana@...gle.com>
To: Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Jyoti Bhayana <jbhayana@...gle.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh@...nel.org>,
Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
cristian.marussi@....com, sudeep.holla@....com,
egranata@...gle.com, mikhail.golubev@...nsynergy.com,
Igor.Skalkin@...nsynergy.com, Peter.hilber@...nsynergy.com,
ankitarora@...gle.com
Subject: Reply to [RFC PATCH v2 0/1] Adding support for IIO SCMI based sensors
Hi Jonathan,
Instead of adding IIO_VAL_INT_H32_L32, I am thinking of adding IIO_VAL_FRACTIONAL_LONG
or IIO_VAL_FRACTIONAL_64 as the scale/exponent used for min/max range can be different
than the one used in resolution according to specification.
I am planning to use read_avail for IIO_CHAN_INFO_PROCESSED using IIO_AVAIL_RANGE
and this new IIO_VAL_FRACTIONAL_64 for min range,max range and resolution.
Instead of two values used in IIO_VAL_FRACTIONAL, IIO_VAL_FRACTIONAL_64 will use 4 values
val_high,val_low,and val2_high and val2_low.
Let me know if that is an acceptable solution.
Thanks,
Jyoti
Powered by blists - more mailing lists