Thread (16 messages) read the whole thread 16 messages, 4 authors, 2015-05-05

Re: [RFC PATCH 1/3] iio: export mounting matrix information

From: Jonathan Cameron <hidden>
Date: 2015-05-05 20:40:41
Also in: linux-acpi, linux-iio, lkml


On 4 May 2015 18:48:23 GMT+01:00, Octavian Purdila [off-list ref] wrote:
On Mon, May 4, 2015 at 2:25 PM, Jonathan Cameron [off-list ref]
wrote:
quoted
On 27/04/15 16:01, Octavian Purdila wrote:
quoted
Export a new sysfs attribute that describes the placement of the
sensor on the device in the form of a mounting matrix so that
userspace can do the required correction to get accurate data:

corrected X = MM[0] * X + MM[1] Y + MM[2] * Z
corrected Y = MM[3] * X + MM[4] Y + MM[5] * Z
corrected Z = MM[6] * X + MM[7] Y + MM[8] * Z

This information is read from the device properties of the parent of
the IIO device.

Signed-off-by: Octavian Purdila <redacted>
Hmm.  This could be done with existing code and a new info_mask
element.
quoted
The disadvantage is you'd have to change the read_raw to
read_raw_multi
quoted
callback, but that's hardly a big job.  If I could be bothered, I'd
move the whole subsystem over and drop read_raw entirely.

It was introduced precisely for this sort of element.
If I understand this correctly this will require changing every driver
that want to expose this information. However, this information is
independent of the driver, as this information is read from the device
tree or ACPI. As such, doesn't this fits better in the IIO core?
In this case it comes from one of those two but there is no inherent reason it won't come from elsewhere.

Take for example an IMU block with integrated components. The mounting
 matrix is then partly provided by acpi say and partly by values read from the device.

Yes moving to read_raw_multi involves a driver change but that is no bad thing anyway and the change is fairly trivial.
quoted
As I mentioned deeper in the thread.  If we are going to introduce a
mounting
quoted
matrix, I'd prefer a version that includes translation.  It might not
matter
quoted
to many devices but it has mattered a lot to me in the past and
doesn't hurt
quoted
others that much (I used to write papers on how to estimate this
stuff
quoted
from black box devices).
OK, I will look into that.

quoted
quoted
---
 Documentation/ABI/testing/sysfs-bus-iio | 11 +++++++++
 drivers/iio/industrialio-core.c         | 42
+++++++++++++++++++++++++++++++++
quoted
quoted
 include/linux/iio/iio.h                 |  9 +++++++
 3 files changed, 62 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation/ABI/testing/sysfs-bus-iio
quoted
quoted
index 866b4ec..d36476e 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -1375,3 +1375,14 @@ Description:
              The emissivity ratio of the surface in the field of
view of the
quoted
quoted
              contactless temperature sensor.  Emissivity varies
from 0 to 1,
quoted
quoted
              with 1 being the emissivity of a black body.
+
+What:               
/sys/bus/iio/devices/iio:deviceX/mounting_matrix
quoted
quoted
+KernelVersion:       4.2
+Contact:     linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+Description:
+             A list of 9 floating point values that describes the
+             transformation needed to account for the way the
sensor has been
quoted
quoted
+             placed on the PCB:
+             corrected X = MM[0] * X + MM[1] Y + MM[2] * Z
+             corrected Y = MM[3] * X + MM[4] Y + MM[5] * Z
+             corrected Z = MM[6] * X + MM[7] Y + MM[8] * Z
diff --git a/drivers/iio/industrialio-core.c
b/drivers/iio/industrialio-core.c
quoted
quoted
index 7c98bc1..9000c53 100644
--- a/drivers/iio/industrialio-core.c
+++ b/drivers/iio/industrialio-core.c
@@ -871,6 +871,45 @@ static ssize_t iio_show_dev_name(struct device
*dev,
quoted
quoted
 static DEVICE_ATTR(name, S_IRUGO, iio_show_dev_name, NULL);

+static bool iio_get_mounting_matrix(struct iio_dev *indio_dev)
+{
+     int i, err;
+
+     err = device_property_read_u32_array(&indio_dev->dev,
"mounting-matrix",
quoted
quoted
+                                         
indio_dev->mounting_matrix, 9);
quoted
quoted
+     if (!err) {
+             int *mm = indio_dev->mounting_matrix;
+
+             for (i = IIO_MM_SIZE - 2; i > 0; i -= 2) {
+                     mm[i] = mm[i / 2];
+                     mm[i + 1] = 0;
+             }
+
+             return true;
+     }
+
+     return false;
+}
+
+static ssize_t iio_show_mounting_matrix(struct device *dev,
+                                     struct device_attribute *attr,
+                                     char *buf)
+{
+     struct iio_dev *indio_dev = dev_to_iio_dev(dev);
+     char *tmp = buf;
+     int i;
+
+     for (i = 0; i < IIO_MM_SIZE; i += 2) {
+             tmp += iio_format_value(tmp, IIO_VAL_INT_PLUS_MICRO,
2,
quoted
quoted
+                                    
&indio_dev->mounting_matrix[i]);
quoted
quoted
+             if (((i + 2) / 2) % 3)
Hmm. if (i != 8) should also do the job with slightly less feedling
of
quoted
magic..
quoted
+                     tmp[-1] = ' ';
+     }
+     return tmp - buf;
+}
+
+static DEVICE_ATTR(mounting_matrix, S_IRUGO,
iio_show_mounting_matrix, NULL);
quoted
quoted
+
 static int iio_device_register_sysfs(struct iio_dev *indio_dev)
 {
      int i, ret = 0, attrcount, attrn, attrcount_orig = 0;
@@ -920,6 +959,9 @@ static int iio_device_register_sysfs(struct
iio_dev *indio_dev)
quoted
quoted
              indio_dev->chan_attr_group.attrs[attrn++] =
&p->dev_attr.attr;
quoted
quoted
      if (indio_dev->name)
              indio_dev->chan_attr_group.attrs[attrn++] =
&dev_attr_name.attr;
quoted
quoted
+     if (iio_get_mounting_matrix(indio_dev))
+             indio_dev->chan_attr_group.attrs[attrn++] =
+                     &dev_attr_mounting_matrix.attr;

      indio_dev->groups[indio_dev->groupcounter++] =
              &indio_dev->chan_attr_group;
diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
index b1e46ae..c1fa852 100644
--- a/include/linux/iio/iio.h
+++ b/include/linux/iio/iio.h
@@ -434,6 +434,8 @@ struct iio_buffer_setup_ops {
                                 const unsigned long *scan_mask);
 };

+#define IIO_MM_SIZE          18
+
 /**
  * struct iio_dev - industrial I/O device
  * @id:                      [INTERN] used to identify device
internally
quoted
quoted
@@ -469,6 +471,12 @@ struct iio_buffer_setup_ops {
  * @groups:          [INTERN] attribute groups
  * @groupcounter:    [INTERN] index of next attribute group
  * @flags:           [INTERN] file ops related flags including busy
flag.
quoted
Hmm. No absolute need to have this new data in the iio_dev.  I'd do
it
quoted
via the read_raw_multi callback, though this will require converting
read_raw
quoted
over to that more flexible version.
quoted
+ * @mounting_matrix: [INTERN] the mounting matrix is a series of 9
+ *                   IIO_VAL_INT_PLUS_MICRO pairs that describes
the
quoted
quoted
+ *                   transformation needed to account for the way
the sensor
quoted
quoted
+ *                   has been placed on the PCB. See the
mounting_matrix
quoted
quoted
+ *                   entry in
Documentation/ABI/testing/sysfs-bus-iio about
quoted
quoted
+ *                   details of the transformation operations.
  * @debugfs_dentry:  [INTERN] device specific debugfs dentry.
  * @cached_reg_addr: [INTERN] cached register address for debugfs
reads.
quoted
quoted
  */
@@ -509,6 +517,7 @@ struct iio_dev {
      int                             groupcounter;

      unsigned long                   flags;
+     int                             mounting_matrix[IIO_MM_SIZE];
 #if defined(CONFIG_DEBUG_FS)
      struct dentry                   *debugfs_dentry;
      unsigned                        cached_reg_addr;
--
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
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help