Changes in Makefile

07b24126 - iio: proximity: aw96103: Add support for aw96103/aw96105 proximity sensor

Tue, 27 Aug 2024 08:02:29 +0000

iio: proximity: aw96103: Add support for aw96103/aw96105 proximity sensorAW96103 is a low power consumption capacitive touch and proximity controller.Each channel can be independently config as sensor input, shield output.Channel Information: aw96103: 3-channel aw96105: 5-channelSigned-off-by: shuaijie wang Link: https://patch.msgid.link/20240827080229.1431784-3-wangshuaijie@awinic.comSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

60df5482 - iio: proximity: Add driver support for TYHX's HX9023S capacitive proximity sensor

Tue, 02 Jul 2024 14:12:34 +0000

iio: proximity: Add driver support for TYHX's HX9023S capacitive proximity sensorA SAR sensor from NanjingTianyihexin Electronics Ltd.The device has the following entry points:Usual frequency:- sampling_frequencyInstant reading of current values for different sensors:- in_proximity0_raw- in_proximity1_raw- in_proximity2_raw- in_proximity3_raw- in_proximity4_rawand associated events in events/Signed-off-by: Yasin Lee Link: https://patch.msgid.link/20240702-add-tyhx-hx9023s-sensor-driver-v9-3-c030f1801d9b@gmail.comSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

3db3562b - iio: Add driver for Murata IRS-D200

Wed, 19 Jul 2023 07:51:17 +0000

iio: Add driver for Murata IRS-D200Murata IRS-D200 is a PIR sensor for human detection. It has support forraw data measurements and detection event notification.Add a driver with support for triggered buffer and events. Map thevarious settings to the `iio` framework, e.g. threshold values, samplingfrequency, filter frequencies etc.Signed-off-by: Waqar Hameed Link: https://lore.kernel.org/r/d218a1bc75402b5ebd6e12a563f7315f83fe966c.1689753076.git.waqar.hameed@axis.comSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

1cdb4c47 - iio:proximity:sx9360: Add sx9360 support

Sat, 01 Jan 2022 20:37:58 +0000

iio:proximity:sx9360: Add sx9360 supportA simplified version of SX9324, it only have one pin and2 phases (aka channels).Only one event is presented.Signed-off-by: Gwendal Grignou Reviewed-by: Stephen Boyd Link: https://lore.kernel.org/r/20220101203800.290387-2-gwendal@chromium.orgSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

4c18a890 - iio:proximity:sx9324: Add SX9324 support

Sat, 01 Jan 2022 20:38:15 +0000

iio:proximity:sx9324: Add SX9324 supportSemtech SAR sensor SX9324 is an evolution of the SX9310:It has 4 phases that can be configured to capture and process datafrom any of 3 CS pins and provide independent detection:proximity, table proximity or body proximity.Gather antenna data: echo sx9324-dev3 > trigger/current_trigger echo 1 > scan_elements/in_proximity0_en echo 1 > buffer/enable od -v -An --endian=big -t d2 -w2 /dev/iio\:device3 (at 10Hz, the default).Trigger events:Setting: thresh_falling_period: 2 (events) thresh_rising_period: 2 (events) in_proximity0_thresh_either_value: 300 in_proximity0_thresh_either_hysteresis: 72using iio_event_monitor /dev/iio\:deviceX, approaching my hand to theantenna pad, I see:...Event: time: 1634763907532035297, type: proximity, channel: 0, evtype:thresh, direction: fallingEvent: time: 1634763910138104640, type: proximity, channel: 0, evtype:thresh, direction: rising...Datasheet: https://edit.wpgdadawant.com/uploads/news_file/program/2019/30184/tech_files/program_30184_suggest_other_file.pdfSigned-off-by: Gwendal Grignou Reviewed-by: Stephen Boyd Link: https://lore.kernel.org/r/20220101203817.290512-4-gwendal@chromium.orgSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

caa8ce7f - iio:proximity:sx9310: Extract common Semtech sensor logic

Sat, 01 Jan 2022 20:38:14 +0000

iio:proximity:sx9310: Extract common Semtech sensor logicBefore adding new Semtech sensors, move common logic to all Semtech SARsensor in its own file:- interface with IIO subsystem,- interrupt management,- channel access conrol,- event processing.The change adds a bidirectional interface between sx93xx and sx_common.The change is quite mechanical, as the impacted functions are movedand renamed.Signed-off-by: Gwendal Grignou Reviewed-by: Stephen Boyd Link: https://lore.kernel.org/r/20220101203817.290512-3-gwendal@chromium.orgSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

7792225b - iio: proximity: Add a ChromeOS EC MKBP proximity driver

Thu, 11 Feb 2021 02:46:01 +0000

iio: proximity: Add a ChromeOS EC MKBP proximity driverAdd support for a ChromeOS EC proximity driver that exposes a "front"proximity sensor via the IIO subsystem. The EC decides when frontproximity is near and sets an MKBP switch 'EC_MKBP_FRONT_PROXIMITY' tonotify the kernel of proximity. Similarly, when proximity detectssomething far away it sets the switch bit to 0. For now this driverexposes a single sensor, but it could be expanded in the future via moreMKBP bits if desired.Cc: Dmitry Torokhov Cc: Benson Leung Cc: Guenter Roeck Cc: Douglas Anderson Cc: Gwendal Grignou Reviewed-by: Enric Balletbo i Serra Signed-off-by: Stephen Boyd Reviewed-by: Gwendal Grignou Link: https://lore.kernel.org/r/20210211024601.1963379-4-swboyd@chromium.orgSigned-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

ac101e6b - iio: proximity: Add driver support for vcnl3020 proximity sensor

Sun, 10 May 2020 18:45:37 +0000

iio: proximity: Add driver support for vcnl3020 proximity sensorProximity sensor driver based on light/vcnl4000.c code.For now supports only the single on-demand measurement.The VCNL3020 is a fully integrated proximity sensor. Fullyintegrated means that the infrared emitter is included in thepackage. It has 16-bit resolution. It includes a signalprocessing IC and features standard I2C communicationinterface. It features an interrupt function.Datasheet: http://www.vishay.com/docs/84150/vcnl3020.pdfSigned-off-by: Ivan Mikhaylov Reviewed-by: Andy Shevchenko Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

72ad02b1 - iio: Add SEMTECH SX9310/9311 sensor driver

Tue, 10 Mar 2020 20:06:59 +0000

iio: Add SEMTECH SX9310/9311 sensor driverAdd SEMTECH SX9310/9311 driver.The device has the following entry points:Usual frequency:- sampling_frequency- sampling_frequency_availableInstant reading of current values for different sensors:- in_proximity0_raw- in_proximity1_raw- in_proximity2_raw- in_proximity3_comb_rawand associated events in events/Signed-off-by: Gwendal Grignou Signed-off-by: Enrico Granata Signed-off-by: Daniel Campello Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

7bb501f4 - iio: ping: add parallax ping sensors

Mon, 25 Nov 2019 08:05:02 +0000

iio: ping: add parallax ping sensorsAdd support for parallax ping and laser ping sensors with just one pinfor trigger and echo signal.This driver is based on srf04. In contrast to it it's necessary tochange direction of the pin and to request the irq just for the periodwhen the echo is rising and falling. Because this adds a lot of casesthere is this individual driver for handling this type of sensors.Add a new configuration variable CONFIG_PING to Kconfig and Makefile.Julia reported an issue with failing to unlock a mutex in some errorpaths.Signed-off-by: Andreas Klinger Reported-by: kbuild test robot Reported-by: Julia Lawall Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

16b05261 - mb1232.c: add distance iio sensor with i2c

Sun, 17 Mar 2019 20:38:03 +0000

mb1232.c: add distance iio sensor with i2cAdd I2CXL-MaxSonar ultrasonic distance sensors of types mb1202, mb1212,mb1222, mb1232, mb1242, mb7040, mb7137 using an i2c interfaceImplemented functionality:- reading the distance via in_distance_raw- buffered mode with trigger- make use of interrupt to announce completion of rangingAdd mb1232 driver to Kconfig and MakefileSigned-off-by: Andreas Klinger Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

6eb17c6c - iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.

Tue, 18 Sep 2018 08:24:21 +0000

iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.This driver was originally written by ST in 2016 as a misc input devicedriver, and hasn't been maintained for a long time. I grabbed some codefrom it's API and reformed it into an iio proximity device driver.This version of driver uses i2c bus to talk to the sensor andpolling for measuring completes, so no irq line is needed.It can be tested with reading from/sys/bus/iio/devices/iio:deviceX/in_distance_inputSigned-off-by: Song Qiang Reviewed-by: Rob Herring Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

1c287992 - iio: light: isl29501: Add support for the ISL29501 ToF sensor.

Fri, 20 Jul 2018 17:34:26 +0000

iio: light: isl29501: Add support for the ISL29501 ToF sensor.This patch adds support for the ISL29501 Time of Flight sensor.Signed-off-by: Mathieu Othacehe Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/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/proximity/Makefile

79e64188 - iio: proximity: Add rfd77402 driver

Tue, 10 Oct 2017 13:48:47 +0000

iio: proximity: Add rfd77402 driverDriver for RF Digital RFD77402 VCSEL (vertical-cavity surface-emittinglaser) Time-of-Flight (ToF) sensor to measure distance up to 2 m withmillimeter precisionSigned-off-by: Peter Meerwald-Stadler Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

feda2840 - iio: distance: add devantech us ranger srf04

Tue, 31 Jan 2017 18:03:45 +0000

iio: distance: add devantech us ranger srf04This patch adds support for the ultrasonic ranger srf04 of devantech.This device is measuring the distance of objects in a range between 1 cmand 3 meters and a theoretical resolution of 3 mm.There are two GPIOs used: - trigger: set as output to the device when the measurement should start - echo: set by the device when the ultrasonic wave is sent out and reset when the echo is recognized; this needs to be an interrupt inputThe time between setting and resetting the echo pin is the time thewaveform needed for one round trip. This time is recorded in the interrupthandler.The distance is calculated in the read function by using the ultrasonicspeed at 20 degrees celsius which is about 343 m/s.Signed-off-by: Andreas Klinger Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

78f83902 - iio: distance: srf08: add IIO driver for us ranger

Wed, 25 Jan 2017 19:07:19 +0000

iio: distance: srf08: add IIO driver for us rangerThis is the IIO driver for devantech srf08 ultrasonic ranger which can beused to measure the distances to an object.The sensor supports I2C with some registers.Supported Features include: - read the distance in ranging mode in centimeters - output of the driver is directly the read value - together with the scale the driver delivers the distance in meters - only the first echo of the nearest object is delivered - set sensitivity as analog value in the range of 0-31 means setting gain register on device - set range registers; userspace enters max. range in millimeters in 43 mm stepsFeatures not supported by this driver: - ranging mode in inches or in microseconds - ANN mode - change I2C address through this driver - light sensorThe driver was added in the directory "proximity" of the iio subsystem andthe menu in den config is now called "Proximity and distance sensors"Signed-off-by: Andreas Klinger Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

cb119d53 - iio: proximity: add support for PulsedLight LIDAR

Tue, 18 Aug 2015 14:40:38 +0000

iio: proximity: add support for PulsedLight LIDARAdd support for the PulsedLight LIDAR rangefinder sensor which allowshigh speed (over 300Hz) distance measurements using Barker Coding within40 meter range.Support only tested on the "blue label" rev 2, but may work using lowsample frequencies on the original version.Signed-off-by: Matt Ranostay Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

4193c0f1 - iio: driver for Semtech SX9500 proximity solution

Mon, 29 Dec 2014 12:41:14 +0000

iio: driver for Semtech SX9500 proximity solutionSupports buffering, IIO events and changing sampling frequency.Datasheet available at:http://www.semtech.com/images/datasheet/sx9500_ag.pdfSigned-off-by: Vlad Dogaru Reviewed-by: Hartmut Knaack Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile

24ddb0e4 - iio: Add AS3935 lightning sensor support

Wed, 03 Dec 2014 12:53:00 +0000

iio: Add AS3935 lightning sensor supportAS3935 chipset can detect lightning strikes and reports those back asevents and the estimated distance to the storm.Signed-off-by: Matt Ranostay Reviewed-by: Marek Vasut Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/iio/proximity/Makefile