License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license 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 binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the 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 cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base 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 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately 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 license
identifiers 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 the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version 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 correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-07-03 00:15:49 +08:00
|
|
|
#
|
|
|
|
|
# Makefile for sensor chip drivers.
|
|
|
|
|
#
|
|
|
|
|
|
2005-07-16 09:38:08 +08:00
|
|
|
obj-$(CONFIG_HWMON) += hwmon.o
|
2005-08-01 03:52:01 +08:00
|
|
|
obj-$(CONFIG_HWMON_VID) += hwmon-vid.o
|
2005-07-16 09:38:08 +08:00
|
|
|
|
2023-04-05 15:31:07 +08:00
|
|
|
# ACPI drivers
|
2011-05-26 02:43:32 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ACPI_POWER) += acpi_power_meter.o
|
2009-09-15 23:18:13 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ATK0110) += asus_atk0110.o
|
2022-01-24 09:56:43 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASUS_EC) += asus-ec-sensors.o
|
hwmon: (asus_wmi_sensors) Support X370 Asus WMI.
Provides a Linux kernel module "asus_wmi_sensors" that provides sensor
readouts via ASUS' WMI interface present in the UEFI of
X370/X470/B450/X399 Ryzen motherboards.
Supported motherboards:
* ROG CROSSHAIR VI HERO,
* PRIME X399-A,
* PRIME X470-PRO,
* ROG CROSSHAIR VI EXTREME,
* ROG CROSSHAIR VI HERO (WI-FI AC),
* ROG CROSSHAIR VII HERO,
* ROG CROSSHAIR VII HERO (WI-FI),
* ROG STRIX B450-E GAMING,
* ROG STRIX B450-F GAMING,
* ROG STRIX B450-I GAMING,
* ROG STRIX X399-E GAMING,
* ROG STRIX X470-F GAMING,
* ROG STRIX X470-I GAMING,
* ROG ZENITH EXTREME,
* ROG ZENITH EXTREME ALPHA.
Co-developed-by: Ed Brindley <kernel@maidavale.org>
Signed-off-by: Ed Brindley <kernel@maidavale.org>
Signed-off-by: Denis Pauk <pauk.denis@gmail.com>
[groeck: Squashed:
"hwmon: Fix warnings in asus_wmi_sensors.rst documetation."]
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2021-11-17 04:57:44 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASUS_WMI) += asus_wmi_sensors.o
|
2023-05-22 19:56:46 +08:00
|
|
|
obj-$(CONFIG_SENSORS_HP_WMI) += hp-wmi-sensors.o
|
2009-09-15 23:18:13 +08:00
|
|
|
|
|
|
|
|
# Native drivers
|
2005-07-03 00:15:49 +08:00
|
|
|
# asb100, then w83781d go first, as they can override other drivers' addresses.
|
|
|
|
|
obj-$(CONFIG_SENSORS_ASB100) += asb100.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_W83627HF) += w83627hf.o
|
2017-11-13 11:27:33 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83773G) += w83773g.o
|
2005-07-27 19:43:47 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83792D) += w83792d.o
|
2006-12-13 01:18:30 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83793) += w83793.o
|
2010-10-29 02:31:44 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83795) += w83795.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83781D) += w83781d.o
|
2006-04-25 20:21:03 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83791D) += w83791d.o
|
2005-07-03 00:15:49 +08:00
|
|
|
|
2006-06-05 02:22:24 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ABITUGURU) += abituguru.o
|
2007-06-17 06:28:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ABITUGURU3)+= abituguru3.o
|
2011-09-30 00:50:04 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AD7314) += ad7314.o
|
2008-08-07 04:41:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AD7414) += ad7414.o
|
2007-05-08 23:22:02 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AD7418) += ad7418.o
|
2014-01-25 14:25:33 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADC128D818) += adc128d818.o
|
2008-08-15 15:40:34 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADCXX) += adcxx.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADM1025) += adm1025.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_ADM1026) += adm1026.o
|
2007-02-15 04:15:04 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADM1029) += adm1029.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADM1031) += adm1031.o
|
2020-01-14 19:21:57 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADM1177) += adm1177.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADM9240) += adm9240.o
|
2008-01-23 07:00:02 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADS7828) += ads7828.o
|
2010-05-25 05:33:38 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADS7871) += ads7871.o
|
2013-03-12 18:38:46 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7X10) += adt7x10.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_ADT7310) += adt7310.o
|
2012-08-13 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7410) += adt7410.o
|
2010-03-06 05:17:23 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7411) += adt7411.o
|
2008-11-13 05:27:03 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7462) += adt7462.o
|
2007-08-01 02:06:52 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7470) += adt7470.o
|
2009-01-16 05:27:47 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ADT7475) += adt7475.o
|
2021-01-08 03:40:14 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AHT10) += aht10.o
|
2007-05-08 15:24:52 +08:00
|
|
|
obj-$(CONFIG_SENSORS_APPLESMC) += applesmc.o
|
hwmon: add driver for Aquacomputer D5 Next
This driver exposes hardware sensors of the Aquacomputer D5 Next
watercooling pump, which communicates through a proprietary USB HID
protocol.
Available sensors are pump and fan speed, power, voltage and current, as
well as coolant temperature. Also available through debugfs are the serial
number, firmware version and power-on count.
Attaching a fan is optional and allows it to be controlled using
temperature curves directly from the pump. If it's not connected,
the fan-related sensors will report zeroes.
The pump can be configured either through software or via its physical
interface. Configuring the pump through this driver is not implemented,
as it seems to require sending it a complete configuration. That
includes addressable RGB LEDs, for which there is no standard sysfs
interface. Thus, that task is better suited for userspace tools.
This driver has been tested on x86_64, both in-kernel and as a module.
Signed-off-by: Aleksa Savic <savicaleksa83@gmail.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2021-08-28 13:26:28 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AQUACOMPUTER_D5NEXT) += aquacomputer_d5next.o
|
2017-06-15 17:53:17 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ARM_SCMI) += scmi-hwmon.o
|
2015-05-21 22:08:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ARM_SCPI) += scpi-hwmon.o
|
2019-08-27 11:44:15 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AS370) += as370-hwmon.o
|
2010-03-06 05:17:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASC7621) += asc7621.o
|
2017-04-05 08:52:41 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASPEED) += aspeed-pwm-tacho.o
|
2024-02-21 18:40:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASPEED_G6) += aspeed-g6-pwm-tach.o
|
2024-01-08 17:44:50 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ASUS_ROG_RYUJIN) += asus_rog_ryujin.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ATXP1) += atxp1.o
|
2019-10-09 18:28:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AXI_FAN_CONTROL) += axi-fan-control.o
|
hwmon: Add Baikal-T1 PVT sensor driver
Baikal-T1 SoC provides an embedded process, voltage and temperature
sensor to monitor an internal SoC environment (chip temperature, supply
voltage and process monitor) and on time detect critical situations,
which may cause the system instability and even damages. The IP-block
is based on the Analog Bits PVT sensor, but is equipped with a
dedicated control wrapper, which provides a MMIO registers-based access
to the sensor core functionality (APB3-bus based) and exposes an
additional functions like thresholds/data ready interrupts, its status
and masks, measurements timeout. All of these is used to create a hwmon
driver being added to the kernel by this commit.
The driver implements support for the hardware monitoring capabilities
of Baikal-T1 process, voltage and temperature sensors. PVT IP-core
consists of one temperature and four voltage sensors, each of which is
implemented as a dedicated hwmon channel config.
The driver can optionally provide the hwmon alarms for each sensor the
PVT controller supports. The alarms functionality is made compile-time
configurable due to the hardware interface implementation peculiarity,
which is connected with an ability to convert data from only one sensor
at a time. Additional limitation is that the controller performs the
thresholds checking synchronously with the data conversion procedure.
Due to these limitations in order to have the hwmon alarms
automatically detected the driver code must switch from one sensor to
another, read converted data and manually check the threshold status
bits. Depending on the measurements timeout settings this design may
cause additional burden on the system performance. By default if the
alarms kernel config is disabled the data conversion is performed by
the driver on demand when read operation is requested via corresponding
_input-file.
Co-developed-by: Maxim Kaurkin <maxim.kaurkin@baikalelectronics.ru>
Signed-off-by: Maxim Kaurkin <maxim.kaurkin@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: linux-mips@vger.kernel.org
Cc: devicetree@vger.kernel.org
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2020-05-28 22:28:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_BT1_PVT) += bt1-pvt.o
|
hwmon: Add support for Amphenol ChipCap 2
The Amphenol ChipCap 2 is a capacitive polymer humidity and temperature
sensor with an integrated EEPROM and minimum/maximum humidity alarms.
All device variants offer an I2C interface and depending on the part
number, two different output modes:
- CC2D: digital output
- CC2A: analog (PDM) output
This driver adds support for the digital variant (CC2D part numbers),
which includes the following part numbers:
- non-sleep measurement mode (CC2D23, CC2D25, CC2D33, CC2D35)
- sleep measurement mode (CC2D23S, CC2D25S, CC2D33S, CC2D35S)
The Chipcap 2 EEPROM can be accessed to configure a series of parameters
like the minimum/maximum humidity alarm threshold and hysteresis. The
EEPROM is only accessible in the command window after a power-on reset.
The default window lasts 10 ms if no Start_CM command is sent. After the
command window is finished (either after the mentioned timeout of after
a Start_NOM command is sent), the device enters the normal operation
mode and makes a first measurement automatically.
Unfortunately, the device does not provide any hardware or software
reset and therefore the driver must trigger power cycles to enter the
command mode. A dedicated, external regulator is required for that.
This driver keeps the device off until a measurement or access to the
EEPROM is required, making use of the first automatic measurement to
avoid different code paths for sleep and non-sleep devices.
The minimum and maximum humidity alarms are configured with two
registers per alarm: one stores the alarm threshold and the other one
keeps the value that turns off the alarm. The alarm signals are only
updated when a measurement is carried out.
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Link: https://lore.kernel.org/r/20240130-topic-chipcap2-v6-5-260bea05cf9b@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2024-01-31 05:06:48 +08:00
|
|
|
obj-$(CONFIG_SENSORS_CHIPCAP2) += chipcap2.o
|
2007-05-08 23:22:02 +08:00
|
|
|
obj-$(CONFIG_SENSORS_CORETEMP) += coretemp.o
|
2020-06-26 13:59:36 +08:00
|
|
|
obj-$(CONFIG_SENSORS_CORSAIR_CPRO) += corsair-cpro.o
|
2020-10-27 21:17:10 +08:00
|
|
|
obj-$(CONFIG_SENSORS_CORSAIR_PSU) += corsair-psu.o
|
2024-05-29 14:27:12 +08:00
|
|
|
obj-$(CONFIG_SENSORS_CROS_EC) += cros_ec_hwmon.o
|
2012-03-17 18:04:41 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DA9052_ADC)+= da9052-hwmon.o
|
2012-10-08 21:26:47 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DA9055)+= da9055-hwmon.o
|
2015-05-14 19:16:37 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DELL_SMM) += dell-smm-hwmon.o
|
2007-06-09 22:11:16 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DME1737) += dme1737.o
|
hwmon: Driver for disk and solid state drives with temperature sensors
Reading the temperature of ATA drives has been supported for years
by userspace tools such as smarttools or hddtemp. The downside of
such tools is that they need to run with super-user privilege, that
the temperatures are not reported by standard tools such as 'sensors'
or 'libsensors', and that drive temperatures are not available for use
in the kernel's thermal subsystem.
This driver solves this problem by adding support for reading the
temperature of ATA drives from the kernel using the hwmon API and
by adding a temperature zone for each drive.
With this driver, the hard disk temperature can be read using the
unprivileged 'sensors' application:
$ sensors drivetemp-scsi-1-0
drivetemp-scsi-1-0
Adapter: SCSI adapter
temp1: +23.0°C
or directly from sysfs:
$ grep . /sys/class/hwmon/hwmon9/{name,temp1_input}
/sys/class/hwmon/hwmon9/name:drivetemp
/sys/class/hwmon/hwmon9/temp1_input:23000
If the drive supports SCT transport and reports temperature limits,
those are reported as well.
drivetemp-scsi-0-0
Adapter: SCSI adapter
temp1: +27.0°C (low = +0.0°C, high = +60.0°C)
(crit low = -41.0°C, crit = +85.0°C)
(lowest = +23.0°C, highest = +34.0°C)
The driver attempts to use SCT Command Transport to read the drive
temperature. If the SCT Command Transport feature set is not available,
or if it does not report the drive temperature, drive temperatures may
be readable through SMART attributes. Since SMART attributes are not well
defined, this method is only used as fallback mechanism.
Cc: Chris Healy <cphealy@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Martin K. Petersen <martin.petersen@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Tested-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2019-11-29 13:34:40 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DRIVETEMP) += drivetemp.o
|
2011-01-09 22:31:39 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DS620) += ds620.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_DS1621) += ds1621.o
|
2010-05-28 01:58:56 +08:00
|
|
|
obj-$(CONFIG_SENSORS_EMC1403) += emc1403.o
|
2010-08-15 03:08:54 +08:00
|
|
|
obj-$(CONFIG_SENSORS_EMC2103) += emc2103.o
|
2022-08-11 01:15:51 +08:00
|
|
|
obj-$(CONFIG_SENSORS_EMC2305) += emc2305.o
|
2011-05-26 02:43:33 +08:00
|
|
|
obj-$(CONFIG_SENSORS_EMC6W201) += emc6w201.o
|
2006-01-10 06:26:14 +08:00
|
|
|
obj-$(CONFIG_SENSORS_F71805F) += f71805f.o
|
2007-07-13 20:34:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_F71882FG) += f71882fg.o
|
2007-08-24 18:03:09 +08:00
|
|
|
obj-$(CONFIG_SENSORS_F75375S) += f75375s.o
|
2011-05-26 02:43:31 +08:00
|
|
|
obj-$(CONFIG_SENSORS_FAM15H_POWER) += fam15h_power.o
|
2007-10-11 20:06:29 +08:00
|
|
|
obj-$(CONFIG_SENSORS_FSCHMD) += fschmd.o
|
2016-07-18 19:51:29 +08:00
|
|
|
obj-$(CONFIG_SENSORS_FTSTEUTATES) += ftsteutates.o
|
2009-04-07 10:00:30 +08:00
|
|
|
obj-$(CONFIG_SENSORS_G760A) += g760a.o
|
2013-06-21 04:21:04 +08:00
|
|
|
obj-$(CONFIG_SENSORS_G762) += g762.o
|
2023-12-07 20:23:59 +08:00
|
|
|
obj-$(CONFIG_SENSORS_GIGABYTE_WATERFORCE) += gigabyte_waterforce.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_GL518SM) += gl518sm.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_GL520SM) += gl520sm.o
|
2020-05-16 01:57:08 +08:00
|
|
|
obj-$(CONFIG_SENSORS_GSC) += gsc-hwmon.o
|
2010-10-22 06:44:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_GPIO_FAN) += gpio-fan.o
|
2023-01-04 04:36:50 +08:00
|
|
|
obj-$(CONFIG_SENSORS_GXP_FAN_CTRL) += gxp-fan-ctrl.o
|
2012-06-27 16:55:11 +08:00
|
|
|
obj-$(CONFIG_SENSORS_HIH6130) += hih6130.o
|
2023-07-25 12:22:07 +08:00
|
|
|
obj-$(CONFIG_SENSORS_HS3001) += hs3001.o
|
2008-08-25 11:59:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_ULTRA45) += ultra45_env.o
|
2015-01-24 21:16:21 +08:00
|
|
|
obj-$(CONFIG_SENSORS_I5500) += i5500_temp.o
|
2007-10-19 04:22:43 +08:00
|
|
|
obj-$(CONFIG_SENSORS_I5K_AMB) += i5k_amb.o
|
2008-05-24 04:04:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_IBMAEM) += ibmaem.o
|
2007-09-15 03:33:46 +08:00
|
|
|
obj-$(CONFIG_SENSORS_IBMPEX) += ibmpex.o
|
2014-07-08 17:08:38 +08:00
|
|
|
obj-$(CONFIG_SENSORS_IBMPOWERNV)+= ibmpowernv.o
|
2013-03-21 06:21:00 +08:00
|
|
|
obj-$(CONFIG_SENSORS_IIO_HWMON) += iio_hwmon.o
|
2009-08-21 05:49:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_INA209) += ina209.o
|
2012-05-12 16:36:38 +08:00
|
|
|
obj-$(CONFIG_SENSORS_INA2XX) += ina2xx.o
|
2021-11-02 13:27:54 +08:00
|
|
|
obj-$(CONFIG_SENSORS_INA238) += ina238.o
|
2016-06-10 23:32:33 +08:00
|
|
|
obj-$(CONFIG_SENSORS_INA3221) += ina3221.o
|
2020-09-21 14:17:51 +08:00
|
|
|
obj-$(CONFIG_SENSORS_INTEL_M10_BMC_HWMON) += intel-m10-bmc-hwmon.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_IT87) += it87.o
|
2010-08-10 08:21:08 +08:00
|
|
|
obj-$(CONFIG_SENSORS_JC42) += jc42.o
|
2006-08-28 20:40:17 +08:00
|
|
|
obj-$(CONFIG_SENSORS_K8TEMP) += k8temp.o
|
2009-12-17 04:38:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_K10TEMP) += k10temp.o
|
2022-04-02 05:40:32 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LAN966X) += lan966x-hwmon.o
|
2024-03-28 20:12:50 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LENOVO_EC) += lenovo-ec-sensors.o
|
2010-09-30 11:12:08 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LINEAGE) += lineage-pem.o
|
2019-03-28 21:09:37 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LOCHNAGAR) += lochnagar-hwmon.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM63) += lm63.o
|
2006-06-13 04:00:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM70) += lm70.o
|
2009-12-10 03:35:50 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM73) += lm73.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM75) += lm75.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM77) += lm77.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM78) += lm78.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM80) += lm80.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM83) += lm83.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM85) += lm85.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM87) += lm87.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM90) += lm90.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LM92) += lm92.o
|
2007-07-05 23:58:29 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM93) += lm93.o
|
2013-03-11 07:54:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM95234) += lm95234.o
|
2009-04-01 06:24:27 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM95241) += lm95241.o
|
2011-06-28 23:11:23 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LM95245) += lm95245.o
|
2014-01-12 02:28:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC2945) += ltc2945.o
|
2019-10-21 23:41:14 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC2947) += ltc2947-core.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LTC2947_I2C) += ltc2947-i2c.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_LTC2947_SPI) += ltc2947-spi.o
|
2016-01-15 17:54:59 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC2990) += ltc2990.o
|
2023-10-26 18:33:13 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC2991) += ltc2991.o
|
2020-12-03 15:11:53 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC2992) += ltc2992.o
|
2011-03-04 03:13:21 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4151) += ltc4151.o
|
hwmon: Add LTC4215 driver
Add Linux support for the Linear Technology LTC4215 Hot Swap controller
I2C monitoring interface.
I have tested the driver with my board, and it appears to work fine. With
the power supplies disabled, it reads 11.93V input, 1.93V output, no
current and no power. With the supplies enabled, it reads 11.93V input,
11.98V output, no current, no power. I'm not drawing any current at the
moment, so this is reasonable. The value in the sense register never
reads anything except 0, so I expect to get zero from the current and
power calculations.
I didn't attempt to support changing any of the chip's settings or
enabling the FET. I'm not sure even how to do that and still fit within
the hwmon framework. :)
Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu>
Cc: Jean Delvare <khali@linux-fr.org>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-04-01 06:24:29 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4215) += ltc4215.o
|
2014-01-14 13:11:56 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4222) += ltc4222.o
|
2009-01-07 23:37:32 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4245) += ltc4245.o
|
2014-01-11 16:17:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4260) += ltc4260.o
|
2010-06-26 02:59:54 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4261) += ltc4261.o
|
2024-01-30 00:13:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTC4282) += ltc4282.o
|
2017-09-01 14:58:17 +08:00
|
|
|
obj-$(CONFIG_SENSORS_LTQ_CPUTEMP) += ltq-cputemp.o
|
2008-08-29 04:26:48 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX1111) += max1111.o
|
2020-11-24 02:56:57 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX127) += max127.o
|
2011-02-03 00:49:54 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX16065) += max16065.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX1619) += max1619.o
|
2011-06-02 23:43:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX1668) += max1668.o
|
hwmon: add Maxim MAX197 support
The MAX197 is an A/D converter, made by Maxim. This driver currently
supports the MAX197, and MAX199. They are both 8-Channel, Multi-Range,
5V, 12-Bit DAS with 8+4 Bus Interface and Fault Protection.
The available ranges for the MAX197 are {0,-5V} to 5V, and {0,-10V} to
10V, while they are {0,-2V} to 2V, and {0,-4V} to 4V on the MAX199.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2012-08-31 09:42:57 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX197) += max197.o
|
2016-03-31 00:16:24 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX31722) += max31722.o
|
2019-11-24 03:11:26 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX31730) += max31730.o
|
2022-09-11 01:19:42 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX31760) += max31760.o
|
2021-09-13 21:40:15 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX6620) += max6620.o
|
2017-10-04 02:08:27 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX6621) += max6621.o
|
2011-01-21 01:42:55 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX6639) += max6639.o
|
2007-05-08 23:22:00 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX6650) += max6650.o
|
2012-10-13 14:01:58 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX6697) += max6697.o
|
2015-08-30 19:44:26 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MAX31790) += max31790.o
|
2023-05-25 00:01:30 +08:00
|
|
|
obj-$(CONFIG_MAX31827) += max31827.o
|
2009-12-10 03:35:58 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MC13783_ADC)+= mc13783-adc.o
|
2023-01-18 20:30:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MC34VR500) += mc34vr500.o
|
2012-03-23 17:02:20 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MCP3021) += mcp3021.o
|
2016-10-11 05:26:31 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TC654) += tc654.o
|
2021-01-21 21:44:33 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TPS23861) += tps23861.o
|
2018-07-03 15:00:09 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MLXREG_FAN) += mlxreg-fan.o
|
2014-08-28 01:53:06 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MENF21BMC_HWMON) += menf21bmc_hwmon.o
|
2020-10-05 17:27:46 +08:00
|
|
|
obj-$(CONFIG_SENSORS_MR75203) += mr75203.o
|
2014-04-06 23:57:20 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT6683) += nct6683.o
|
2022-04-27 09:01:53 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT6775_CORE) += nct6775-core.o
|
|
|
|
|
nct6775-objs := nct6775-platform.o
|
2012-05-21 10:29:48 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT6775) += nct6775.o
|
2022-04-28 09:27:07 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT6775_I2C) += nct6775-i2c.o
|
2014-06-30 10:38:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT7802) += nct7802.o
|
2015-02-27 21:16:00 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NCT7904) += nct7904.o
|
2018-07-04 07:23:26 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NPCM7XX) += npcm750-pwm-fan.o
|
2016-03-05 23:34:56 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NSA320) += nsa320-hwmon.o
|
2011-06-20 15:48:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NTC_THERMISTOR) += ntc_thermistor.o
|
hwmon: add driver for NZXT Kraken X42/X52/X62/X72
These are "all-in-one" CPU liquid coolers that can be monitored and
controlled through a proprietary USB HID protocol.
While the models have differently sized radiators and come with varying
numbers of fans, they are all indistinguishable at the software level.
The driver exposes fan/pump speeds and coolant temperature through the
standard hwmon sysfs interface.
Fan and pump control, while supported by the devices, are not currently
exposed. The firmware accepts up to 61 trip points per channel
(fan/pump), but the same set of trip temperatures has to be maintained
for both; with pwmX_auto_point_Y_temp attributes, users would need to
maintain this invariant themselves.
Instead, fan and pump control, as well as LED control (which the device
also supports for 9 addressable RGB LEDs on the CPU water block) are
left for existing and already mature user-space tools, which can still
be used alongside the driver, thanks to hidraw. A link to one, which I
also maintain, is provided in the documentation.
The implementation is based on USB traffic analysis. It has been
runtime tested on x86_64, both as a built-in driver and as a module.
Signed-off-by: Jonas Malaco <jonas@protocubo.io>
Link: https://lore.kernel.org/r/20210319045544.416138-1-jonas@protocubo.io
[groeck: Removed unnecessary spinlock.h include]
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2021-03-19 12:55:44 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NZXT_KRAKEN2) += nzxt-kraken2.o
|
2024-01-29 19:19:28 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NZXT_KRAKEN3) += nzxt-kraken3.o
|
2021-10-31 11:30:58 +08:00
|
|
|
obj-$(CONFIG_SENSORS_NZXT_SMART2) += nzxt-smart2.o
|
2022-11-04 22:07:00 +08:00
|
|
|
obj-$(CONFIG_SENSORS_OXP) += oxp-sensors.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PC87360) += pc87360.o
|
2006-12-13 01:18:29 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PC87427) += pc87427.o
|
2009-03-31 03:46:43 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PCF8591) += pcf8591.o
|
2023-09-02 15:47:01 +08:00
|
|
|
obj-$(CONFIG_SENSORS_POWERZ) += powerz.o
|
2014-06-13 04:22:15 +08:00
|
|
|
obj-$(CONFIG_SENSORS_POWR1220) += powr1220.o
|
2024-02-06 20:54:20 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PT5161L) += pt5161l.o
|
2014-07-16 23:46:42 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PWM_FAN) += pwm-fan.o
|
2018-05-26 03:24:35 +08:00
|
|
|
obj-$(CONFIG_SENSORS_RASPBERRYPI_HWMON) += raspberrypi-hwmon.o
|
2020-12-12 05:54:25 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SBTSI) += sbtsi_temp.o
|
2021-07-26 21:36:13 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SBRMI) += sbrmi.o
|
2011-07-26 03:46:09 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SCH56XX_COMMON)+= sch56xx-common.o
|
2011-03-22 00:59:36 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SCH5627) += sch5627.o
|
2011-07-26 03:46:09 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SCH5636) += sch5636.o
|
2023-03-21 10:26:44 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SFCTEMP) += sfctemp.o
|
2024-08-17 10:22:57 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SG2042_MCU) += sg2042-mcu.o
|
2020-09-15 05:43:36 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SL28CPLD) += sl28cpld-hwmon.o
|
2009-04-14 05:39:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SHT15) += sht15.o
|
2011-01-07 15:15:39 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SHT21) += sht21.o
|
2016-06-02 15:59:11 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SHT3x) += sht3x.o
|
2021-05-24 22:20:38 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SHT4x) += sht4x.o
|
2014-06-06 06:24:19 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SHTC1) += shtc1.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SIS5595) += sis5595.o
|
2022-09-29 17:43:13 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SMPRO) += smpro-hwmon.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SMSC47B397)+= smsc47b397.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_SMSC47M1) += smsc47m1.o
|
2006-03-23 23:37:23 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SMSC47M192)+= smsc47m192.o
|
2020-06-18 21:59:51 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SPARX5) += sparx5-temp.o
|
2024-05-28 01:49:10 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SPD5118) += spd5118.o
|
2017-02-02 15:44:03 +08:00
|
|
|
obj-$(CONFIG_SENSORS_STTS751) += stts751.o
|
2024-01-31 08:58:55 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SURFACE_FAN)+= surface_fan.o
|
2024-08-11 08:14:41 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SURFACE_TEMP)+= surface_temp.o
|
2022-01-24 20:10:06 +08:00
|
|
|
obj-$(CONFIG_SENSORS_SY7636A) += sy7636a-hwmon.o
|
2010-01-09 06:43:04 +08:00
|
|
|
obj-$(CONFIG_SENSORS_AMC6821) += amc6821.o
|
2015-06-21 21:54:44 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TC74) += tc74.o
|
2007-07-09 04:43:00 +08:00
|
|
|
obj-$(CONFIG_SENSORS_THMC50) += thmc50.o
|
2010-05-28 01:58:56 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP102) += tmp102.o
|
2014-06-18 13:37:17 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP103) += tmp103.o
|
2016-12-02 10:32:41 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP108) += tmp108.o
|
2009-06-16 00:39:46 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP401) += tmp401.o
|
2009-09-15 23:18:11 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP421) += tmp421.o
|
2022-02-23 06:36:10 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP464) += tmp464.o
|
2019-11-13 06:30:01 +08:00
|
|
|
obj-$(CONFIG_SENSORS_TMP513) += tmp513.o
|
2016-01-30 01:35:52 +08:00
|
|
|
obj-$(CONFIG_SENSORS_VEXPRESS) += vexpress-hwmon.o
|
2009-12-17 04:38:28 +08:00
|
|
|
obj-$(CONFIG_SENSORS_VIA_CPUTEMP)+= via-cputemp.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_VIA686A) += via686a.o
|
2006-09-25 02:54:04 +08:00
|
|
|
obj-$(CONFIG_SENSORS_VT1211) += vt1211.o
|
2005-11-27 03:20:05 +08:00
|
|
|
obj-$(CONFIG_SENSORS_VT8231) += vt8231.o
|
2005-07-03 00:15:49 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83627EHF) += w83627ehf.o
|
|
|
|
|
obj-$(CONFIG_SENSORS_W83L785TS) += w83l785ts.o
|
2007-11-23 09:31:52 +08:00
|
|
|
obj-$(CONFIG_SENSORS_W83L786NG) += w83l786ng.o
|
2009-07-28 22:52:22 +08:00
|
|
|
obj-$(CONFIG_SENSORS_WM831X) += wm831x-hwmon.o
|
2009-07-20 19:43:45 +08:00
|
|
|
obj-$(CONFIG_SENSORS_WM8350) += wm8350-hwmon.o
|
2016-07-22 06:37:32 +08:00
|
|
|
obj-$(CONFIG_SENSORS_XGENE) += xgene-hwmon.o
|
2005-07-03 00:15:49 +08:00
|
|
|
|
2018-11-09 05:05:24 +08:00
|
|
|
obj-$(CONFIG_SENSORS_OCC) += occ/
|
2022-02-08 23:36:36 +08:00
|
|
|
obj-$(CONFIG_SENSORS_PECI) += peci/
|
2011-07-12 22:15:19 +08:00
|
|
|
obj-$(CONFIG_PMBUS) += pmbus/
|
2011-01-27 12:09:02 +08:00
|
|
|
|
2011-01-14 22:12:38 +08:00
|
|
|
ccflags-$(CONFIG_HWMON_DEBUG_CHIP) := -DDEBUG
|
