lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 Jan 2021 23:09:20 +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, > So, sensor_max_range can effectively be exposed as a combination of > scale and the *_raw_avail for a raw read (via the read_avail callback in IIO). > We'll ignore the fact the interface assumes a single value (so I assume symmetric?) Based on the SCMI specification the sensor min range and max range are 64 bits signed number. looks like IIO_AVAIL_RANGE can only take the following types of data which all looks like 32 bit. IIO_VAL_FRACTIONAL also takes two int type numbers. How can I send 64 bit sensor range using this and read_avail callback? #define IIO_VAL_INT 1 #define IIO_VAL_INT_PLUS_MICRO 2 #define IIO_VAL_INT_PLUS_NANO 3 #define IIO_VAL_INT_PLUS_MICRO_DB 4 #define IIO_VAL_INT_MULTIPLE 5 #define IIO_VAL_FRACTIONAL 10 #define IIO_VAL_FRACTIONAL_LOG2 11 #define IIO_VAL_CHAR 12 Thanks, Jyoti
Powered by blists - more mailing lists