On Mon, Jun 25, 2018 at 1:06 PM, Jonathan Cameron <jic23@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > On 25 June 2018 08:40:08 BST, Daniel Baluta <daniel.baluta@xxxxxxxxx> wrote: >>On Fri, Jun 22, 2018 at 4:44 PM, Jonathan Cameron >><jonathan.cameron@xxxxxxxxxx> wrote: >>> On Thu, 21 Jun 2018 12:04:37 +0530 >>> Himanshu Jha <himanshujha199640@xxxxxxxxx> wrote: >>> >>>> Add support to probe the bme680 sensor on the i2c bus using >>>> ACPI. >>>> >>>> Cc: Daniel Baluta <daniel.baluta@xxxxxxxxx> >>>> Signed-off-by: Himanshu Jha <himanshujha199640@xxxxxxxxx> >>> >>> This looks fine. Do we know for sure that they use that ACPI >>> ID? For these sorts of devices, it's fairly common to have entirely >>> random ids presented. Also, I'm a little curious to know, what >>> ACPI based device has one of these? >> >>Hi Jonathan, >> >>I am not aware of any ACPI device using our chosen ID. We just >>picked BME0680 based on previous drivers from Bosch. >> >>It is useful to enumerate the sensor via ACPI because our >>qemu testing setup uses ACPI. > > Cool. Any docs on that setup? Would be useful blog post if easy to do. We have multiple iterations of our setup, depending on the project. Generic description that we use at University can be found here: https://linux-kernel-labs.github.io/master/labs/vm.html Scripts are here: https://github.com/linux-kernel-labs/linux/tree/master/tools/labs/qemu For IIO we use DLN2 (USB-I2C/SPI) adapter and we pass -acpitable file=description.aml to qemu. thanks, Daniel. -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
