Tags

Linux 4.0-rc4

First set of new drivers, cleanups and functionality for IIO in the 4.1 cycle.

New drivers
* CM3323 color sensor.
* MS5611 pressure and temperature sensor.

New functionality
* mup6050 - create mux clients for devices described via ACPI. The reasoning
     and approach taken in this patch are complex.  Basically there is no
     otherway of finding out what is there than by some esoteric look ups in
     the ACPI data.
* cm3232 - PM support
* itg3200 - suspend/resume support
* mcp320x - add more ADCs to the kconfig to reflect what the driver supports
     (this patch and the bindings got left behind when the support was added
      a while back).

Docs / utils
* ti-adc128s052 - DT bindings.
* mcp3422 - DT bindings.
* mcp320x - DT bindings
* ABI docs for event threshold scale attributes, in_magn_offset, proximity
  scan_element and thresh falling/rising values for accelerometers.  All
  elements long in use that have slipped by being explicitly documented.
* Tidy up the tools previously in drivers/staging/iio/Documentation and move
  them out to /tools/iio. Yet another move that should have happened long ago.
  This time Roberta Dobrescu did the leg work.  Thanks!

Core Cleanups
* Export userspace IIO headers.  We should have done the appropriate header
  splitting a long time ago. Thanks to Daniel for sorting this out.

* Refactor the registring of attributes for buffers to move all non-custom
  ones to a vector allowing easier additions to the current set in the future.

Driver Cleanups
* gpiod related cleanups.  Make use of the additional parameter to specify
  	initial direciton to avoid extra code.
* bmc150 - Various refactorings to reduce code repitition and prepare for
           hardware buffer support.  Some of these cleanups are good even
	   without the new functionality.
* kmx61 - direct use of index to an array avoiding a structure element which
          was always the index to an element in an array of that structure.
* vf610 - avoid incorrect type for return from wait_for_completion_timeout.
* gp2ap020a00f - use put_unaligned_le32 for slight code simplification.
* ade7754 - improve error handling including suppressing some build warnings.
* ade7759 - improve error handling including suppressing some build warnings.
* hmc5843 - Long line and indentation fixes. Also some constifying of various
      constant data.
* ade7854 - 80+ character line splitting.
* ad2s1210 - fix wrong printf format string.
* mxs-lradc - fix wrong printf format string.
* ade7954-i2c - code alignment fixes and other trivial but worthwhile bits.
* periodic rtc trigger - make the frequency type an unsigned int as it
  is always treated as such.
* jsa1212 - constify struct regmap_config as it is constant.
* ad7793 - typo in the MODULE_DESCRIPTION
* mma9551 - check gpiod_to_irq errors.  Note that this doesn't actually cause
    any trouble but is worth tidying up as obviously incorrect.
* mlx90614 - refactor the register symbols to make it clear which reads are to
    RAM not PROM.

3rd set of IIO fixes for the 4.0 cycle.

* A double free occured on an error path in due to an event registration issue.
  The fix is the minimal change rather than possibly reworking this area of
  the core to give a more elegant solution (future work).
* A number of drivers were directly accessing indio_dev->buffer->scan_mask
  to identify the currently enabled channel set.  This may not be correct
  if we have additional clients on the push interface.  The correct option
  is indio_dev->active_scan_mask. This is fixed.
* bmc150 had incorrectly specified sampling frequency (a datasheet confusion
  as they are specified in terms of bandwith - e.g. half the sampling
  frequency).
* hmc5843 wasn't setting it's name and hence the name attribute was
  returning an empty string.
* inv_mpu6050 wasn't clearing the locally held timestamp buffer when the
  hardware fifo was reset. Also an inconsistency existed in the interface
  for the scale of the channels.  Magic numbers were written but real ones
  were used for the reads.  Now uses real numbers (i.e. not array indexes)
  for both.
* fix a missing dependency in the dummy driver. Previously shielded from
  the autobuilders by an earlier build error.

contains fixes all over drivers/phy and includes the following
*) Using phy_get_drvdata instead of dev_get_drvdata in armada375-usb2.c
*) Fixes w.r.t checking return values in regmap APIs, protecting regmap ops
   with spin lock and directly using regmap_update_bits instead of having a
   separate function to do the same in the various PHYs used in exynos.
*) check return value in platform_get_resource of hix5hd2-sata PHY
*) Removed NULL terminating entry from phys array and fix off-by-one
   valid value checking for args->args[0] in of_xlate of exynos USB PHY.
*) Fixup rockchip_usb_phy_power_on failure path
*) Fix devm_phy_match to find the correct match in phy core and also fix to
   return the correct value from PHY APIs if PM runtime is not enabled.
*) Removed redundant code in twl4030 and xgene
*) Fixed sizeof during memory allocation in miphy PHYs
*) simplify ti_pipe3_dpll_wait_lock implementation, fix missing clk_prepare
   when using old dt name and nit pick in MOUDLE_ALIAS in TI PHYs.

Power management and ACPI fixes for v4.0-rc4

 - Fix an ACPI LPSS (Low-Power Subsystem) driver issue causing the
   8250_dw driver to confuse an LPSS clock with another one it is
   supposed to handle due to the lack of identification allowing it
   to tell those clocks apart (Heikki Krogerus).

 - Revert a recent commit that was supposed to improve the usability
   of the cpupower tool, but clearly did the opposite (Josh Boyer).

/

DeviceTree fixes for 4.0-rc:

- Fix for stdout-path option parsing with added unittest

- Fix for stdout-path interaction with earlycon

- Several DT unittest fixes

- Fix Sparc allmodconfig build error on
  of_platform_register_reconfig_notifier

- Several DT overlay kconfig and build warning fixes

- Several DT binding documentation updates

sound fixes for 4.0-rc4

This is a round of HD-audio fixes: there are a long-standing
regression fix and a few more device/codec-specific quirks.
In addition, a couple of FireWire regression fixes, a USB-audio quirk
for Roland UA-22 and a sanity check in API for user-defined control
elements.

IOMMU Fixes for Linux v4.0-rc3

The patches contain:

	* Fix multiple ARM IOMMU drivers to behave well when the
	  hardware is not present

	* Mark MSM driver as broken

	* Fix build errors with the new ARM generic io-page-table code

iwlwifi:

* fix ROC removal - avoids a firmware crash
* fix throughput regression on iwldvm devices
* fix panic in BT Coex
* fixes in rate control
* fixes in scan

b43:

* fix support for 5 GHz only BCM43228 model

rtlwifi:

* improve handling of IPv6 packets

brcmfmac:

* perform bound checking on vendor command buffer

Linux 4.0-rc3

staging driver fixes for 4.0-rc3

Here are some IIO and staging driver fixes for 4.0-rc3.

Details are in the shortlog, nothing major, mostly IIO fixes for
reported issues.

All have been in linux-next successfully.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

regulator: Fixes for v4.0

A couple of driver specific fixes plus a fix for a regression in the
core where the updates to use sysfs group registration were overly
enthusiastic in eliding properties and removed some that had been
previously present.

This is the 3.19.1 stable release

This is the 3.18.9 stable release

This is the 3.14.35 stable release

This is the 3.10.71 stable release

Major changes:

brcmfmac:

* sdio improvements
* add a debugfs file so users can provide us all the revinfo we could
  ask for

iwlwifi:

* add triggers for firmware dump collection
* remove support for -9.ucode
* new statitics API
* rate control improvements

ath9k:

* add per-vif TX power capability
* BT coexistance fixes

ath10k:

* qca6174: enable STA transmit beamforming (TxBF) support
* disable multi-vif power save by default

bcma:

* enable support for PCIe Gen 2 host devices

Power management and ACPI fixes for v4.0-rc3

 - Fix ACPI resources management problems introduced by the recent
   rework of the code in question (Jiang Liu) and a build issue
   introduced by those changes (Joachim Nilsson).

 - Fix a recent suspend-to-idle regression on systems where entering
   idle states causes local timers to stop, prevent suspend-to-idle
   from crashing in restricted configurations (no cpuidle driver,
   cpuidle disabled etc.) and clean up the idle loop somewhat while
   at it (Rafael J Wysocki).

 - Fix build problem in the cpufreq ppc driver (Geert Uytterhoeven).

 - Allow the ACPI backlight driver module to be loaded if ACPI is
   disabled which helps the i915 driver in those configurations
   (stable-candidate) and change the code to help debug unusual use
   cases (Chris Wilson).

 - Wakeup IRQ management changes in v3.18 caused some drivers on the
   at91 platform to trigger a warning from the IRQ core related to
   an unexpected combination of interrupt action handler flags.
   However, on at91 a timer IRQ is shared with some other devices
   (including system wakeup ones) and that leads to the unusual
   combination of flags in question.  To make it possible to avoid
   the warning introduce a new interrupt action handler flag (which
   can be used by drivers to indicate the special case to the core)
   and rework the problematic at91 drivers to use it and work as
   expected during system suspend/resume.  From Boris Brezillon,
   Rafael J Wysocki and Mark Rutland.

 - Clean up the generic power domains subsystem's debugfs interface
   (Kevin Hilman).

/