Changes in Makefile

2c8920ff - iio: gyro: Add driver support for ADXRS290

Sun, 26 Jul 2020 14:10:16 +0000

iio: gyro: Add driver support for ADXRS290ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)angular rate sensor (gyroscope) designed for use in stabilizationapplications. It also features an internal temperature sensor andprogrammable high-pass and low-pass filters.Add support for ADXRS290 in direct-access mode for now.Datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/ADXRS290.pdfReviewed-by: Andy Shevchenko Signed-off-by: Nishant Malpani Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

4da38f1b - iio: gyro: fxas21002c: add spi driver

Fri, 12 Apr 2019 16:48:59 +0000

iio: gyro: fxas21002c: add spi driverAdd driver to talk over spi to a fxas21002c gyroscope device and usethe core as main controller.Signed-off-by: Rui Miguel Silva Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

a034cbe1 - iio: gyro: fxas21002c: add i2c driver

Fri, 12 Apr 2019 16:48:58 +0000

iio: gyro: fxas21002c: add i2c driverAdd the real driver to talk over i2c and use the fxas21002c corefor the main tasks.Signed-off-by: Rui Miguel Silva Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

a0701b62 - iio: gyro: add core driver for fxas21002c

Fri, 12 Apr 2019 16:48:57 +0000

iio: gyro: add core driver for fxas21002cAdd core support for the NXP fxas21002c Tri-axis gyroscope,using the iio subsystem. It supports PM operations, axis reading,temperature, scale factor of the axis, high pass and low passfiltering, and sampling frequency selection.It will have extras modules to support the communication over i2c andspi.Signed-off-by: Rui Miguel Silva Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/iio/gyro/Makefile

3904b28e - iio: gyro: Add driver for the MPU-3050 gyroscope

Tue, 25 Oct 2016 14:15:54 +0000

iio: gyro: Add driver for the MPU-3050 gyroscopeThis adds a new driver for the Invensense MPU-3050 gyroscope.This driver is based on information from the rough input driverin drivers/input/misc/mpu3050.c and the scratch misc driverposted by Nathan Royer in 2011. Some years have passed but thisis finally a fully-fledged driver for this gyroscope. It wasdeveloped and tested on the Qualcomm APQ8060 Dragonboard.The driver supports both raw and buffered input. It alsosupports the internal trigger mechanism by registering a triggerthat can fire in response to the internal sample engine of thecomponent. In addition to reading out the gyroscope sensorvalues, the driver also supports reading the temperature fromthe sensor.The driver currently only supports I2C but the MPU-3050 canalso be used from SPI, so the I2C portions are split in theirown file and we just use regmap to access all registers, soit will be trivial to plug in SPI support if/when someone hasa system requiring this.To conserve power, the driver utilizes the runtime PMframework and will put the sensor in off mode and disable theregulators when unused, after a timeout of 10 seconds.The fullscale can be set for the sensor to 250, 500, 1000 or2000 deg/s. This corresponds to scale values of rougly 0.000122,0.000275, 0.000512 or 0.001068. By writing such values (or closeto these) into "in_anglevel_scale", the corresponding fullscalecan be chosen. It will default to 2000 deg/s (~35 rad/s).The gyro component can have DC offsets on all axes. These can becompensated using the standard sysfs ABI property"in_anglevel_[xyz]_calibbias". This is in positive/negativevalues of the raw values, so a suitable calibration bias can bedetermined by userspace by reading the "in_anglevel_[xyz]_raw"for a few iterations while holding the sensor still, create anaverage integer, and writing the negative inverse of that into"in_anglevel_[xyz]_calibbias". After this the hardware willautomatically subtract the bias, also when using bufferedreadings.Since the MPU-3050 has an outgoing I2C port it needs to act asan I2C mux. This means that the device is switching I2C trafficto devices beyond it. On my system this is the only way to reachthe accelerometer. The "sensor fusion" ability of the MPU-3050to directly talk to the device on the outgoing I2C port iscurrently not used by the driver, but it has code to allow I2Ctraffic to pass through so that the Linux kernel can reach thedevice on the other side with a kernel driver.Example usage with the native trigger:$ generic_buffer -a -c10 -n mpu3050iio device number being used is 0iio trigger number being used is 0No channels are enabled, enabling all channelsEnabling: in_anglvel_z_enEnabling: in_timestamp_enEnabling: in_anglvel_y_enEnabling: in_temp_enEnabling: in_anglvel_x_en/sys/bus/iio/devices/iio:device0 mpu3050-dev029607.142578 -0.117493 0.074768 0.012817 18078879715029639.285156 -0.117493 0.076904 0.013885 18088898233529696.427734 -0.116425 0.076904 0.012817 18098917803929742.857422 -0.117493 0.076904 0.012817 18108937774229764.285156 -0.116425 0.077972 0.012817 18118957418729860.714844 -0.115356 0.076904 0.012817 18128977270529864.285156 -0.117493 0.076904 0.012817 18138997152029910.714844 -0.115356 0.076904 0.013885 18149017048329917.857422 -0.116425 0.076904 0.011749 18159036974229975.000000 -0.116425 0.076904 0.012817 181690567075Disabling: in_anglvel_z_enDisabling: in_timestamp_enDisabling: in_anglvel_y_enDisabling: in_temp_enDisabling: in_anglvel_x_enThe first column is the temperature in millidegrees, then the x,y,zaxes in succession followed by the timestamp. Also tested successfullyusing the HRTimer trigger.Cc: Nick Vaccaro Cc: Ge Gao Cc: Anna Si Cc: Dmitry Torokhov Cc: Crestez Dan Leonard Cc: Daniel Baluta Cc: Gregor Boirie Cc: Peter Rosin Cc: Peter Meerwald-Stadler Signed-off-by: Linus Walleij Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

b1d125cc - iio: bmg160: Add SPI driver

Wed, 19 Aug 2015 12:12:46 +0000

iio: bmg160: Add SPI driverSigned-off-by: Markus Pargmann Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

13426454 - iio: bmg160: Separate i2c and core driver

Wed, 19 Aug 2015 12:12:45 +0000

iio: bmg160: Separate i2c and core driverThis patch separates the core driver using regmap and the i2c driverwhich creates the i2c regmap. Also in the Kconfig file BMG160 andBMG160_I2C are separate now.Signed-off-by: Markus Pargmann Reviewed-by: Srinivas Pandruvada Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

a9afcaa6 - iio: common: ssp_sensors: Add sensorhub gyroscope sensor

Wed, 28 Jan 2015 14:05:54 +0000

iio: common: ssp_sensors: Add sensorhub gyroscope sensorThis patch adds gyroscope iio driver which uses sensorhub as dataprovider.Signed-off-by: Karol Wrona Acked-by: Kyungmin Park Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

22b46c45 - iio:gyro:bmg160 Gyro Sensor driver

Thu, 08 May 2014 21:57:00 +0000

iio:gyro:bmg160 Gyro Sensor driverThis change implements support for BMG160 Gyro sensor. Although chiphas several advanced features, this change implements minimum setrequired for using gyro sensor.Signed-off-by: Srinivas Pandruvada Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

555d5a9f - staging:iio:adis16260: Move out of staging

Wed, 17 Jul 2013 14:44:00 +0000

staging:iio:adis16260: Move out of stagingThe drivers is in more or less good shape, conforms to the IIO ABI and none ofthe default static code checker report any problems, so move it out of staging.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

3edc84e6 - iio: Add a comment to about alphabetical order to Kconfigs and Makefiles

Mon, 15 Jul 2013 07:45:00 +0000

iio: Add a comment to about alphabetical order to Kconfigs and MakefilesKeeping Makefile and Kconfig entries in alphabetical order usually works betterthan just appending new entries at the end, since it reduces the amount ofconflicts. This patch adds a comment to the IIO Kconfig and Makefile files todocument that the entries should be kept in alphabetical order.Also reorder those entries which weren't in alphabetical order yet.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

32341859 - staging:iio:adis16130: Move out of staging

Mon, 10 Jun 2013 14:00:00 +0000

staging:iio:adis16130: Move out of stagingThe adis16130 driver is fairly simple and it a good shape now, so move it out ofstaging. Remove an outdated FIXME along the way.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

9dbf091d - iio: gyro: Add itg3200

Fri, 01 Feb 2013 08:51:00 +0000

iio: gyro: Add itg3200This patch adds support for the InvenSense itg3200.The itg3200 is a three-axis gyro with 16-bit ADC andI2C interface.Signed-off-by: Manuel Stahl Reviewed-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

420b0fcb - staging:iio: Move adxrs450 driver out of staging

Thu, 31 Jan 2013 14:27:00 +0000

staging:iio: Move adxrs450 driver out of stagingThe adxrs450 is in a reasonable shape now. It follows the IIO ABI and non of thestandard code checker tools report any issue, so move it out of staging.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

7be56a8f - iio:gyro: Add STMicroelectronics gyroscopes driver

Fri, 25 Jan 2013 23:44:00 +0000

iio:gyro: Add STMicroelectronics gyroscopes driverThis patch adds a generic gyroscope driver for STMicroelectronicsgyroscopes, currently it supports:L3G4200D, LSM330DL, L3GD20, L3GD20H, LSM330DLC, L3G4IS, LSM330.Signed-off-by: Denis Ciocca Reviewed-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

a9fbbee8 - staging:iio:adis16080: Move out of staging

Wed, 09 Jan 2013 14:01:00 +0000

staging:iio:adis16080: Move out of stagingThe driver is rather simple and in a good shape. It follows the IIO ABI and thestandard codechecker tools do not report any issues, so move it out of staging.While moving it also remove one outdated 'fixme' comment.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

9caed0d9 - iio:gyro: Add support for the ADIS16136 gyroscope

Tue, 20 Nov 2012 13:36:00 +0000

iio:gyro: Add support for the ADIS16136 gyroscopeThis patch adds support for the ADIS16133, ADIS16135, ADIS16136 single channelgyroscopes. The main difference between them is the sensor precision.Signed-off-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile

c5bdbef7 - iio: hid-sensors: Added Gyroscope 3D

Wed, 05 Sep 2012 12:56:00 +0000

iio: hid-sensors: Added Gyroscope 3DAdded usage id processing for Gyroscope 3D. This uses IIOinterfaces for triggered buffer to present data to usermode.This uses HID sensor framework for registering callbackevents from the sensor hub.Signed-off-by: srinivas pandruvada Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/gyro/Makefile