Skip to contentSkip to conversation

ACPI DSDT support for mount-matrix?

DISCUSSION Bastien Nocera 2 participants 2 messages Nov 22, 2016 – Nov 27, 2016 IIO

lore
Share & tools
lore
#0 lore raw

Hey,

Gregor added support for exporting the mount matrix from the Device Tree to the IIO accelerometer:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfc57732ad38f93ae6232a3b4e64fd077383a0f1

And Faouaz wanted to add support for exporting the mount matrix from the ACPI DSDT to sysfs as well:
http://www.spinics.net/lists/linux-acpi/msg51540.html

Would it be possible to rework that ACPI patch to export the mount matrix through IIO as is done for DeviceTree-based machines?

I'm adding mount-matrix support to iio-sensor-proxy, which currently means getting that information from the firmware through the IIO device, using udev as a way to override that, if the firmware doesn't contain that information. I'd like to avoid having 3 different sources for the value.

Cheers

PS: I'd also be interested in that _PLD information to export the information to webcams.

maintainer
#1 lore raw
Quoted 6 lines · Bastien Nocera

Hey,

Gregor added support for exporting the mount matrix from the Device Tree to the IIO accelerometer:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dfc57732ad38f93ae6232a3b4e64fd077383a0f1

Quoted 6 lines

And Faouaz wanted to add support for exporting the mount matrix from the ACPI DSDT to sysfs as well:
http://www.spinics.net/lists/linux-acpi/msg51540.html

Would it be possible to rework that ACPI patch to export the mount matrix through IIO as is done for DeviceTree-based machines?

There is obviously a lot of other information in there. Is it possible to access this via interfaces within the kernel? Obviously we could replicate parts of your patch set to read them directly but it would be good to avoid any code duplication (not that it looks like it would be that much!)

Jonathan

Quoted 16 lines

I'm adding mount-matrix support to iio-sensor-proxy, which currently means getting that information from the firmware through the IIO device, using udev as a way to override that, if the firmware doesn't contain that information. I'd like to avoid having 3 different sources for the value.

Cheers

PS: I'd also be interested in that _PLD information to export the information to webcams.
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html