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 21:07:57 +07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2012-05-11 20:35:33 +07:00
|
|
|
#
|
|
|
|
|
# Makefile for IIO ADC drivers
|
|
|
|
|
#
|
|
|
|
|
|
2013-07-15 14:45:00 +07:00
|
|
|
# When adding new entries keep the list in alphabetical order
|
2012-08-10 23:36:00 +07:00
|
|
|
obj-$(CONFIG_AD_SIGMA_DELTA) += ad_sigma_delta.o
|
2012-06-25 19:52:49 +07:00
|
|
|
obj-$(CONFIG_AD7266) += ad7266.o
|
2014-06-30 15:50:00 +07:00
|
|
|
obj-$(CONFIG_AD7291) += ad7291.o
|
2012-11-17 18:42:59 +07:00
|
|
|
obj-$(CONFIG_AD7298) += ad7298.o
|
2013-02-13 13:47:00 +07:00
|
|
|
obj-$(CONFIG_AD7923) += ad7923.o
|
2012-09-10 15:34:00 +07:00
|
|
|
obj-$(CONFIG_AD7476) += ad7476.o
|
2016-09-23 22:19:44 +07:00
|
|
|
obj-$(CONFIG_AD7766) += ad7766.o
|
2012-09-04 22:26:00 +07:00
|
|
|
obj-$(CONFIG_AD7791) += ad7791.o
|
2012-11-21 23:27:00 +07:00
|
|
|
obj-$(CONFIG_AD7793) += ad7793.o
|
2012-11-05 16:56:00 +07:00
|
|
|
obj-$(CONFIG_AD7887) += ad7887.o
|
2014-10-03 16:31:00 +07:00
|
|
|
obj-$(CONFIG_AD799X) += ad799x.o
|
2017-03-29 04:52:59 +07:00
|
|
|
obj-$(CONFIG_ASPEED_ADC) += aspeed_adc.o
|
2012-05-11 20:35:33 +07:00
|
|
|
obj-$(CONFIG_AT91_ADC) += at91_adc.o
|
2016-01-14 22:38:13 +07:00
|
|
|
obj-$(CONFIG_AT91_SAMA5D2_ADC) += at91-sama5d2_adc.o
|
2017-04-04 13:34:41 +07:00
|
|
|
obj-$(CONFIG_AXP20X_ADC) += axp20x_adc.o
|
2014-10-07 11:17:15 +07:00
|
|
|
obj-$(CONFIG_AXP288_ADC) += axp288_adc.o
|
2016-06-28 14:40:35 +07:00
|
|
|
obj-$(CONFIG_BCM_IPROC_ADC) += bcm_iproc_adc.o
|
2015-05-18 16:19:18 +07:00
|
|
|
obj-$(CONFIG_BERLIN2_ADC) += berlin2-adc.o
|
2015-01-07 03:47:35 +07:00
|
|
|
obj-$(CONFIG_CC10001_ADC) += cc10001_adc.o
|
2017-03-24 10:38:42 +07:00
|
|
|
obj-$(CONFIG_CPCAP_ADC) += cpcap-adc.o
|
2015-06-21 17:15:51 +07:00
|
|
|
obj-$(CONFIG_DA9150_GPADC) += da9150-gpadc.o
|
2017-07-07 05:39:33 +07:00
|
|
|
obj-$(CONFIG_DLN2_ADC) += dln2-adc.o
|
2016-11-08 18:58:58 +07:00
|
|
|
obj-$(CONFIG_ENVELOPE_DETECTOR) += envelope-detector.o
|
2017-07-25 03:51:45 +07:00
|
|
|
obj-$(CONFIG_EP93XX_ADC) += ep93xx_adc.o
|
2013-02-15 13:56:00 +07:00
|
|
|
obj-$(CONFIG_EXYNOS_ADC) += exynos_adc.o
|
2015-12-14 20:53:51 +07:00
|
|
|
obj-$(CONFIG_FSL_MX25_ADC) += fsl-imx25-gcq.o
|
2015-08-28 21:27:52 +07:00
|
|
|
obj-$(CONFIG_HI8435) += hi8435.o
|
2017-01-06 00:51:57 +07:00
|
|
|
obj-$(CONFIG_HX711) += hx711.o
|
2015-12-08 17:26:20 +07:00
|
|
|
obj-$(CONFIG_IMX7D_ADC) += imx7d_adc.o
|
2015-12-07 16:09:34 +07:00
|
|
|
obj-$(CONFIG_INA2XX_ADC) += ina2xx-adc.o
|
iio: adc: add new lp8788 adc driver
TI LP8788 PMU provides regulators, battery charger, ADC,
RTC, backlight driver and current sinks.
This patch enables the LP8788 ADC functions.
The LP8788 ADC has several ADC input selection and supports 12bit resolution.
Internal operation of getting ADC is access to registers of LP8788.
The LP8788 ADC uses exported functions for accessing these registers.
(exported by LP8788 MFD device driver)
This driver supports IIO_CHAN_INFO_RAW and SCALE.
So the IIO consumer can calculate the value with raw and scale.
The unit of scale is micro.
(ADC Input Selection)
Voltage: battery voltage (MAX 5.0, 5.5 and 6.0V)
charger input voltage
four general ADC inputs
coin cell voltage
Current: battery charging current
Temperature: IC temperature
(The IIO map for the IIO consumer)
The ADC input is configurable in the platform side.
Even though this platform data is not defined,
the default IIO map is created for supporting the power supply driver.
The battery voltage and temperature are used inside this driver.
(History)
Patch v6.
(a) Fix scale value for each ADC input selection
Voltage and current type are mili unit and temperature is degree.
To calculate the IC temperature,
temp = raw * scaleint + (raw * scalepart)/ 1000000, scaleint is always 0.
= raw * 0.061050, raw: 0 ~ 4095
Then range of IC temperature(ADC result) is 0 ~ 250'C
(b) Reorganization of the IIO channel Spec
Remove address, scan_type and scan_index and rollback the datasheet name.
The reason why 'address' field is unnecessary is no relation with each channel.
Moreover, to get the raw ADC value, the address info is not only one register
but also several registers.
Therefore specific function(lp8788_get_adc_result) is called rather than
using one 'address' field.
(c) Fix coding style
Remove duplicated checking routine while unregistering the IIO map.
Fix code for space and parenthesis.
Patch v5.
Fix default consumer name as 'lp8788-charger'.
Add mutex for ADC read operation.
Reorganization on lp8788_adc_read_raw().
Patch v4.
Fix adc_raw function: support RAW and SCALE channel info.
Change LP8788 ADC platform data - iio map.
Enables the default IIO map.
Patch v3.
Fix wrong size of allocating iio private data.
Fix coding styles.
Patch v2.
Support RAW and SCALE interface for IIO consumer.
Clean up the iio channel spec macro.
Signed-off-by: Milo(Woogyom) Kim <milo.kim@ti.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
2012-09-17 16:35:00 +07:00
|
|
|
obj-$(CONFIG_LP8788_ADC) += lp8788_adc.o
|
2016-03-12 19:30:14 +07:00
|
|
|
obj-$(CONFIG_LPC18XX_ADC) += lpc18xx_adc.o
|
2017-02-05 20:07:00 +07:00
|
|
|
obj-$(CONFIG_LPC32XX_ADC) += lpc32xx_adc.o
|
2017-07-03 13:25:57 +07:00
|
|
|
obj-$(CONFIG_LTC2471) += ltc2471.o
|
2016-08-25 12:48:43 +07:00
|
|
|
obj-$(CONFIG_LTC2485) += ltc2485.o
|
2017-03-29 16:42:58 +07:00
|
|
|
obj-$(CONFIG_LTC2497) += ltc2497.o
|
2014-06-15 05:27:00 +07:00
|
|
|
obj-$(CONFIG_MAX1027) += max1027.o
|
2017-01-18 23:30:52 +07:00
|
|
|
obj-$(CONFIG_MAX11100) += max11100.o
|
2017-03-28 23:34:48 +07:00
|
|
|
obj-$(CONFIG_MAX1118) += max1118.o
|
2012-10-06 20:42:27 +07:00
|
|
|
obj-$(CONFIG_MAX1363) += max1363.o
|
2017-04-06 21:20:53 +07:00
|
|
|
obj-$(CONFIG_MAX9611) += max9611.o
|
2013-05-03 16:58:00 +07:00
|
|
|
obj-$(CONFIG_MCP320X) += mcp320x.o
|
2013-09-02 21:00:00 +07:00
|
|
|
obj-$(CONFIG_MCP3422) += mcp3422.o
|
2016-08-18 14:11:36 +07:00
|
|
|
obj-$(CONFIG_MEDIATEK_MT6577_AUXADC) += mt6577_auxadc.o
|
2014-02-26 23:29:07 +07:00
|
|
|
obj-$(CONFIG_MEN_Z188_ADC) += men_z188_adc.o
|
2017-01-23 01:17:13 +07:00
|
|
|
obj-$(CONFIG_MESON_SARADC) += meson_saradc.o
|
2017-03-16 19:27:10 +07:00
|
|
|
obj-$(CONFIG_MXS_LRADC_ADC) += mxs-lradc-adc.o
|
2013-06-25 00:24:00 +07:00
|
|
|
obj-$(CONFIG_NAU7802) += nau7802.o
|
2015-10-16 19:53:38 +07:00
|
|
|
obj-$(CONFIG_PALMAS_GPADC) += palmas_gpadc.o
|
2014-10-22 21:13:33 +07:00
|
|
|
obj-$(CONFIG_QCOM_SPMI_IADC) += qcom-spmi-iadc.o
|
2017-04-04 19:08:18 +07:00
|
|
|
obj-$(CONFIG_QCOM_VADC_COMMON) += qcom-vadc-common.o
|
2015-01-20 17:15:22 +07:00
|
|
|
obj-$(CONFIG_QCOM_SPMI_VADC) += qcom-spmi-vadc.o
|
2017-04-04 19:08:19 +07:00
|
|
|
obj-$(CONFIG_QCOM_PM8XXX_XOADC) += qcom-pm8xxx-xoadc.o
|
2017-01-28 06:08:37 +07:00
|
|
|
obj-$(CONFIG_RCAR_GYRO_ADC) += rcar-gyroadc.o
|
2014-07-24 04:24:00 +07:00
|
|
|
obj-$(CONFIG_ROCKCHIP_SARADC) += rockchip_saradc.o
|
2018-06-21 10:14:05 +07:00
|
|
|
obj-$(CONFIG_SC27XX_ADC) += sc27xx_adc.o
|
2017-02-05 19:34:00 +07:00
|
|
|
obj-$(CONFIG_SPEAR_ADC) += spear_adc.o
|
iio: stx104: Add IIO support for the ADC channels
The Apex Embedded Systems STX104 features 16 channels of single-ended (8
channels of true differential) 16-bit analog input. Differential input
configuration may be selected via a physical jumper on the device.
Similarly, input polarity (unipolar/bipolar) is configured via a
physical jumper on the device.
Input gain selection is available to the user via software, thus
allowing eight possible input ranges: +-10V, +-5V, +-2.5V, +-1.25V,
0 to 10V, 0 to 5V, 0 to 2.5V, and 0 to 1.25V. Four input gain
configurations are supported: x1, x2, x4, and x8.
This ADC resolution is 16-bits (1/65536 of full scale). Analog input
samples are taken on software trigger; neither FIFO sampling nor
interrupt triggering is supported by this driver.
The Apex Embedded Systems STX104 is primarily an analog-to-digital
converter device. The STX104 IIO driver was initially placed in the DAC
directory because only the DAC portion of the STX104 was supported at
the time. Now that ADC support has been added to the STX104 IIO driver,
the driver should be moved to the more appropriate ADC directory.
Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
2016-08-30 03:22:56 +07:00
|
|
|
obj-$(CONFIG_STX104) += stx104.o
|
2016-12-13 21:33:32 +07:00
|
|
|
obj-$(CONFIG_SUN4I_GPADC) += sun4i-gpadc-iio.o
|
2016-11-15 22:30:57 +07:00
|
|
|
obj-$(CONFIG_STM32_ADC_CORE) += stm32-adc-core.o
|
2016-11-15 22:30:58 +07:00
|
|
|
obj-$(CONFIG_STM32_ADC) += stm32-adc.o
|
2018-01-10 17:13:10 +07:00
|
|
|
obj-$(CONFIG_STM32_DFSDM_CORE) += stm32-dfsdm-core.o
|
2018-01-10 17:13:11 +07:00
|
|
|
obj-$(CONFIG_STM32_DFSDM_ADC) += stm32-dfsdm-adc.o
|
2012-11-23 22:13:00 +07:00
|
|
|
obj-$(CONFIG_TI_ADC081C) += ti-adc081c.o
|
2016-02-07 16:14:16 +07:00
|
|
|
obj-$(CONFIG_TI_ADC0832) += ti-adc0832.o
|
2017-05-09 23:05:01 +07:00
|
|
|
obj-$(CONFIG_TI_ADC084S021) += ti-adc084s021.o
|
2016-08-28 21:52:49 +07:00
|
|
|
obj-$(CONFIG_TI_ADC12138) += ti-adc12138.o
|
2017-05-17 22:28:17 +07:00
|
|
|
obj-$(CONFIG_TI_ADC108S102) += ti-adc108s102.o
|
2014-03-09 01:38:00 +07:00
|
|
|
obj-$(CONFIG_TI_ADC128S052) += ti-adc128s052.o
|
2016-08-20 10:17:03 +07:00
|
|
|
obj-$(CONFIG_TI_ADC161S626) += ti-adc161s626.o
|
2016-02-11 20:49:54 +07:00
|
|
|
obj-$(CONFIG_TI_ADS1015) += ti-ads1015.o
|
2016-11-28 23:58:15 +07:00
|
|
|
obj-$(CONFIG_TI_ADS7950) += ti-ads7950.o
|
2015-11-09 19:52:59 +07:00
|
|
|
obj-$(CONFIG_TI_ADS8688) += ti-ads8688.o
|
2012-10-16 14:25:45 +07:00
|
|
|
obj-$(CONFIG_TI_AM335X_ADC) += ti_am335x_adc.o
|
2017-01-16 15:38:24 +07:00
|
|
|
obj-$(CONFIG_TI_TLC4541) += ti-tlc4541.o
|
2014-03-16 08:43:31 +07:00
|
|
|
obj-$(CONFIG_TWL4030_MADC) += twl4030-madc.o
|
iio: twl6030-gpadc: TWL6030, TWL6032 GPADC driver
The GPADC is general purpose ADC found on TWL6030, and TWL6032 PMIC,
known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and 19 channels
respectively. Some channels have current source and are used for
measuring voltage drop on resistive load for detecting battery ID
resistance, or measuring voltage drop on NTC resistors for external
temperature measurements. Some channels measure voltage, (i.e. battery
voltage), and have voltage dividers, thus, capable to scale voltage.
Some channels are dedicated for measuring die temperature.
Some channels are calibrated in 2 points, having offsets from ideal
values kept in trim registers. This is used to correct measurements.
The differences between GPADC in TWL6030 and TWL6032:
- 10 bit vs 12 bit ADC;
- 17 vs 19 channels;
- channels have different purpose(i.e. battery voltage
channel 8 vs channel 18);
- trim values are interpreted differently.
Based on the driver patched from Balaji TK, Graeme Gregory, Ambresh K,
Girish S Ghongdemath.
Signed-off-by: Balaji T K <balajitk@ti.com>
Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
Signed-off-by: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
2013-07-25 20:26:00 +07:00
|
|
|
obj-$(CONFIG_TWL6030_GPADC) += twl6030-gpadc.o
|
2014-01-26 12:39:00 +07:00
|
|
|
obj-$(CONFIG_VF610_ADC) += vf610_adc.o
|
This is the MFD patch set for the 3.8 merge window.
We have several new drivers, most of the time coming with their sub devices
drivers:
- Austria Microsystem's AS3711
- Nano River's viperboard
- TI's TPS80031, AM335x TS/ADC,
- Realtek's MMC/memstick card reader
- Nokia's retu
We also got some notable cleanups and improvements:
- tps6586x got converted to IRQ domains.
- tps65910 and tps65090 moved to the regmap IRQ API.
- STMPE is now Device Tree aware.
- A general twl6040 and twl-core cleanup, with moves to the regmap I/O and IRQ
APIs and a conversion to the recently added PWM framework.
- sta2x11 gained regmap support.
Then the rest is mostly tiny cleanups and fixes, among which we have Mark's
wm5xxx and wm8xxx patchset.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAABAgAGBQJQznPnAAoJEIqAPN1PVmxKuA8P/0nOJduXFM1c0Gy+DD5DnJnG
cXzzeSTV8iO3a3sHIye43QPJ5V2YUR5uxLTUEOo/G7my/MoZ/azeNidkUD3qLVlm
wVIq35lcS8dWTZaY7nlpBcWc6e39UB0sEueuJNxyhOv5lnMKdi2tAow5f4vIRQnd
Q67/EbrgqdltcOpGmVuCdQcvphvWgy+K65jzbJG5zXs7hGX13Q+M5RnYhx76kc8f
TDd0APZ71n5/RyISFSBSu2vfl2kES6o47aMgqqXMEHri6d3puAaXM0rFoMzXg/4G
eBdxndN25H7rW7xvt9tuUod2rn1AO7tif5d7jal3Cfj61y3iqKY30yb3OzS9XQXH
9WZ2qDst11zvzQivxIkMGvfRXRfncNLWR4DrBSqVfSbYV2uQj2eS8C6ONwKVMXsQ
5tjNp91PFqN19sWQjIjSMcrNswxgpvdQ9mqFTyOGmISbqrpPSTi+MuO8r9+xTfUF
PnzUX2nVOW/i9NcI7uotjzh8jiw6t8XMVHhkehiSYR9hzCb6MaPsFPN4jWq9XA2m
1htCHylNpHqHQ3Mup7Is6j0Li1ahdwfm4lbrgiVEA4t4Mqs5E/Ka+3V8laNAKylW
PfCP/VmnJYzmgVTK/qobFNeKzRqR0i4WTL6T7oAxGL87Q4TJaqKpEkXWne8UXV+Q
yIbN0fmWfCveCetM+vaf
=F790
-----END PGP SIGNATURE-----
Merge tag 'mfd-3.8-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6
Pull MFS update from Samuel Ortiz:
"This is the MFD patch set for the 3.8 merge window.
We have several new drivers, most of the time coming with their sub
devices drivers:
- Austria Microsystem's AS3711
- Nano River's viperboard
- TI's TPS80031, AM335x TS/ADC,
- Realtek's MMC/memstick card reader
- Nokia's retu
We also got some notable cleanups and improvements:
- tps6586x got converted to IRQ domains.
- tps65910 and tps65090 moved to the regmap IRQ API.
- STMPE is now Device Tree aware.
- A general twl6040 and twl-core cleanup, with moves to the regmap
I/O and IRQ APIs and a conversion to the recently added PWM
framework.
- sta2x11 gained regmap support.
Then the rest is mostly tiny cleanups and fixes, among which we have
Mark's wm5xxx and wm8xxx patchset."
Far amount of annoying but largely trivial conflicts. Many due to
__devinit/exit removal, others due to one or two of the new drivers also
having come in through another tree.
* tag 'mfd-3.8-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6: (119 commits)
mfd: tps6507x: Convert to devm_kzalloc
mfd: stmpe: Update DT support for stmpe driver
mfd: wm5102: Add readback of DSP status 3 register
mfd: arizona: Log if we fail to create the primary IRQ domain
mfd: tps80031: MFD_TPS80031 needs to select REGMAP_IRQ
mfd: tps80031: Add terminating entry for tps80031_id_table
mfd: sta2x11: Fix potential NULL pointer dereference in __sta2x11_mfd_mask()
mfd: wm5102: Add tuning for revision B
mfd: arizona: Defer patch initialistation until after first device boot
mfd: tps65910: Fix wrong ack_base register
mfd: tps65910: Remove unused data
mfd: stmpe: Get rid of irq_invert_polarity
mfd: ab8500-core: Fix invalid free of devm_ allocated data
mfd: wm5102: Mark DSP memory regions as volatile
mfd: wm5102: Correct default for LDO1_CONTROL_2
mfd: arizona: Register haptics devices
mfd: wm8994: Make current device behaviour the default
mfd: tps65090: MFD_TPS65090 needs to select REGMAP_IRQ
mfd: Fix stmpe.c build when OF is not enabled
mfd: jz4740-adc: Use devm_kzalloc
...
2012-12-17 09:55:20 +07:00
|
|
|
obj-$(CONFIG_VIPERBOARD_ADC) += viperboard_adc.o
|
2014-02-17 21:10:00 +07:00
|
|
|
xilinx-xadc-y := xilinx-xadc-core.o xilinx-xadc-events.o
|
|
|
|
|
obj-$(CONFIG_XILINX_XADC) += xilinx-xadc.o
|
2018-01-10 17:13:08 +07:00
|
|
|
obj-$(CONFIG_SD_ADC_MODULATOR) += sd_adc_modulator.o
|