Tags

First round of IIO new drivers, cleanups and functionality for the 3.20 cycle.

New device support
* jsa1212 proxmity / ambient light sensor
* SM08500 supported added to the kxcjk-1013 accelerometer driver
* KMX61 Accelerometer/Magnetometer.  This took a somewhat rocky path
  being first merged, then reverted for a rewrite after a discussion of
  how to support additional functionality and finally being merged prior
  to some last reviews coming in, with resultant follow up patches.
* Freescale mma9551l driver (minor follow up warning supression patch).
* Semtech SX9500 proximity device driver.
* ak8975 gains support for ak09911 and ak09912 and drop the standalone driver
  for the ak09911.

New functionality
 * Dummy driver gains some virtual registers making it more flexible.
 * IIO_ACTIVITY channel types, with modifiers running, walking etc.  This is
   to support on chip motion clasifiers.  As such it is in the form of a
   confidence percentage.  The only devices so far only do binary decisions
   but this gives us room when other devices give more nuanced clasification.
 * IIO_EV_DIR_NONE type for events where there is no obvious direction.
   First case is step detection.
 * IIO_STEPS channel type for pedometers.
 * ENABLE mask element used to control turning on counting types such as
   the pedometer that need a 'start point'.
 * INSTANCE event type to support things that happen once.
 * info element for height calibration (used in various motion estimation
   algorithms). Note heigh tof use
 * dummy driver demonstration of the use of all the new bits above.
 * event monitor support for the new events.
 * inv_mpu6050 gains an i2c mux to allow bypassing the device to access
   additional devices connected on the other side of it.  Note that in
   Windows these are handled by firmware on the device and not exposed
   directly.
 * inv_mpu6050 gains ACPI enumeration.
 * inkern interface gains iio_write_channel_raw to allow in kernel users
   of DAC functionality via a simple wrapper.
 * Document input current readings in the ABI docs.
 * Add an error message when we get an out of range error in device tree
   processing for the in kernel interfaces.  Basically a device tree debugging
   aid.
 * Add a sanity check that a scan index for a channel is unique during
   registration.  There to help catch bugs as this should never happen
   in a bug free driver.

Cleanups and fixlets

 A rework of buffer registration from Lars - a precursor to some other
 upcoming new stuff (a few patches from others rolled in here as well).
 * Ensure all drivers register the same channels for the device and buffer.
 * Move buffer registration into the core rather than using the old
   two step approach.  Now we have simple ways of using a unified set channels
   for both without requiring channels be exposed by both interface, this
   removes a fair bit of boilerplate.
 * Stop sca3000 and ad5933 (both in staging) enabling buffer channels by
   default. It has long be convention in IIO to startup with no channels
   enabled and leave it up to userspace to say what goes in the buffer.
   Getting rid of these allows us to drop export of iio_scan_mask_set.
 * Drop get_bytes_per_datum from iio_buffer_access_funcs as not been used
   for a while.
 * Allocate standard buffer attributes in the core rather than in every
   driver with a buffer.
 * Make the length attribute read only when a driver is not able to set
   the length.
 * Drop the get_length callback for buffers as it is already available in
   struct iio_buffer.
 * Drop an unused arguement form iio_kfifo_allocate and add devm allocator
   for it.
 * some kconfig entries gain anotation with the resulting module name.
 * Fix a resulting compile issue in dummy driver due to a stub taking
   wrong parameters as a result of the above rework.
 * Fix an off by 2 error in copying the core assigned buffer attributes.

Other cleanups,
 * Trivial space before comma fixups.
 * ak8975 fixlets - none critical.  Rework to allow more device support.
 * Drop unnecessary sizeof(u8) calls.
 * bmp280 - refactor the compensation code to reduce copy operations and
   code length.  A second patch futher optimized this and performed some
   other minor cleanups.
 * kxcjk-1013 - various power control cleanups to avoid unnecessary enable
   / disable of device.  Make sure it is only controlled at all if CONFIG_PM
   is enabled.  Also som cleanups of error paths.
 * Small cleanups in adf4530 driver - pointless message and unnecessary braces.
 * Clarifiy the proximity ABI docs to make it clear it should get bigger
   as we move futher away.
 * Drop a misleading comment form industrialio-core.c
 * Trivial white space cleanups.
 * sca3000 looses an unused debug function.
 * Fix char unsigned ordering in ad8366
 * Increase the sleep time in ad9523 to make it predictable (value didn't
   really matter so make it more than 20 msecs)
 * mxs-lradc touchscreen property cleanups in device tree are fixed to ensure
   the meet all the 'interesting' documentation.
 * A couple of cleanups for the staging ad5933 driver to avoid unnecessary
   conversion to a processed temperature vlaue in kernel and remove
   platform data form the state structure as not needed after probe.
 * Fix a wrong scale factor in the docs.

Misc
 * Add IIO include files to the maintainers entry.

Changes:

* ath9k: enable Transmit Power Control (TPC) for ar9003 chips

* rtlwifi: cleanup and updates from the vendor driver

* rsi: fix memory leak related to firmware image

* ath: parameter fix for FCC DFS pattern

sound fixes for 3.19-rc3

Nothing too exciting as a new year's start here: most of fixes are for
ASoC, a boot crash fix on OMAP for deferred probe, a few driver
specific fixes (Intel, dwc, rockchip, rt5677), in addition to typo
fixes in kerneldoc comments for PCM.

This is the 3.2.66 stable release

misc fixes in PHY drivers

Power management and ACPI material for 3.19-rc3

 - Fix for a potential NULL pointer dereference in the cpufreq
   core due to an initialization race condition (Ethan Zhao).

 - Fixes for abuse of the OPP (Operating Performance Points) API
   related to RCU and other minor issues in the OPP library and
   the cpufreq-dt driver (Dmitry Torokhov).

 - cpuidle governors cleanup making them measure idle duration in
   a better way without using the CPUIDLE_FLAG_TIME_INVALID flag
   which allows that flag to be dropped from the ACPI cpuidle driver
   and from the core too (Len Brown).

 - New ACPI backlight blacklist entries for Samsung machines
   without a working native backlight interface that need to
   use the ACPI backlight instead (Aaron Lu).

 - New CPU IDs of future Intel Xeon CPUs for the Intel RAPL power
   capping driver (Jacob Pan).

 - Generic power domains framework modification to export the
   of_genpd_get_from_provider() function to modular drivers that
   will allow future driver modifications to be based on the mainline
   (Amit Daniel Kachhap).

 - Two fixes for the cpupower tool (Michal Privoznik, Prarit Bhargava).

/

regulator: Fix for v3.19

One fix here, a fix for the voltage mapping on one of the s2mps11
regulators which broke systems using it including apparently the Gear 2
smartwatches.

ASoC: Updates for v3.20

Nothing too exciting here yet, a small optimization for DAPM from
Lars-Peter and a few small bits and pieces for drivers but nothing
that really stands out.

ASoC: Fixes for v3.19

A few fixes for v3.19, a few driver specifics and one core fix which
fixes a boot crash on OMAP if deferred probing kicks in due to
attempting to modify static data.

Linux 3.19-rc2

sound fixes for 3.19-rc2

Just a couple of fixes for the new Intel Skylake HD-audio support.

o Paul made a Kconfig dependency fix to ipw2200, it was not possible to
  enable that driver because Wireless Extensions is now disabled by default.

o Mika fixed brcmfmac not to crash when platform data is not populated

o Emmanuel provided few fixes to iwlwifi, he says:

  "I have here new device IDs and a fix for double free bug I
  introduced. I also fix an issue with the RFKILL interrupt - the HW
  needs us to ACK the interrupt again after we reset it. Liad fixes an
  issue with the firmware debugging infrastructure. While working on
  torture scenarios of firmware restarts, Eliad found an issue which
  he fixed."

Linux 3.19-rc1

CONFIG_PM_RUNTIME elimination for 3.19-rc1

This removes the last few uses of CONFIG_PM_RUNTIME introduced
recently and makes that config option finally go away.

CONFIG_PM will be available directly from the menu now and
also it will be selected automatically if CONFIG_SUSPEND or
CONFIG_HIBERNATION is set.

/

- plane handling refactoring from Matt Roper and Gustavo Padovan in prep for
  atomic updates
- fixes and more patches for the seqno to request transformation from John
- docbook for fbc from Rodrigo
- prep work for dual-link dsi from Gaurav Signh
- crc fixes from Ville
- special ggtt views infrastructure from Tvrtko Ursulin
- shadow patch copying for the cmd parser from Brad Volkin
- execlist and full ppgtt by default on gen8, for testing for now

More ACPI and power management updates for 3.19-rc1

 - Fix a regression in leds-gpio introduced by a recent commit that
   inadvertently changed the name of one of the properties used by
   the driver (Fabio Estevam).

 - Fix a regression in the ACPI backlight driver introduced by a
   recent fix that missed one special case that had to be taken
   into account (Aaron Lu).

 - Drop the level of some new kernel messages from the ACPI core
   introduced by a recent commit to KERN_DEBUG which they should
   have used from the start and drop some other unuseful KERN_ERR
   messages printed by ACPI (Rafael J Wysocki).

 - Revert an incorrect commit modifying the cpupower tool
   (Prarit Bhargava).

 - Fix two regressions introduced by recent commits in the OPP
   library and clean up some existing minor issues in that code
   (Viresh Kumar).

 - Continue to replace CONFIG_PM_RUNTIME with CONFIG_PM throughout
   the tree (or drop it where that can be done) in order to make
   it possible to eliminate CONFIG_PM_RUNTIME (Rafael J Wysocki,
   Ulf Hansson, Ludovic Desroches).  There will be one more
   "CONFIG_PM_RUNTIME removal" batch after this one, because some
   new uses of it have been introduced during the current merge
   window, but that should be sufficient to finally get rid of it.

 - Make the ACPI EC driver more robust against race conditions
   related to GPE handler installation failures (Lv Zheng).

 - Prevent the ACPI device PM core code from attempting to
   disable GPEs that it has not enabled which confuses ACPICA
   and makes it report errors unnecessarily (Rafael J Wysocki).

 - Add a "force" command line switch to the intel_pstate driver
   to make it possible to override the blacklisting of some
   systems in that driver if needed (Ethan Zhao).

 - Improve intel_pstate code documentation and add a MAINTAINERS
   entry for it (Kristen Carlson Accardi).

 - Make the ACPI fan driver create cooling device interfaces
   witn names that reflect the IDs of the ACPI device objects
   they are associated with, except for "generic" ACPI fans
   (PNP ID "PNP0C0B").  That's necessary for user space thermal
   management tools to be able to connect the fans with the
   parts of the system they are supposed to be cooling properly.
   From Srinivas Pandruvada.

/

sound fixes for 3.19-rc1

Here are a few fixes that have landed after the previous pull
request.  All are driver specific fixes including:
- error/int value fixes in OXFW,
- Intel Skylake HD-audio HDMI codec support,
- Additional HD-audio Realtek codecs and AD1986A codec fixes/quirks,
- a few more DSD support and a quirk for Arcam rPAC in usb-audio,
- a typo fix for Scarlett 6i6,
- fixes for new ASIHPI firmware,
- ASoC Exynos7 cleanups,
- Intel ACPI support, and
- a fix for PCM512 register cache sync.

This relatively large collection of fixes is all over - from things
that were broken a long time ago (the management key issue) but not
noticed yet, to small issues that were only introduced into 3.19
(like the multicast issue). At least one issue is old but can crash
the kernel based on invalid userspace requests (the nl80211 matches
array one.)