Tags

ASoC: Fixes for v4.0

A few driver specific fixes here, none of them earth shattering in
themselves, that have accumliated since the opening of the merge window.

Linux 4.0-rc2

Two GPIO fixes for the v4.0 kernel series:

- Fix a translation problem in of_get_named_gpiod_flags()
- Fix a long standing container_of() mistake in the TPS65912
  driver.

Linaro 15.02

Second round of IIO fixes for the 4.0 cycle (or round one part two really!)
These are fixes for patches in the recent merge window and are in a separate
branch to avoid rebasing the main fixes-togreg branch.

* jsa1212 - select missing REGMAP_I2C
* ssp_common - build warning fix for PM functions when PM not in use.
* ak8975 - the addition of a utility library for this driver (as part of
           adding new device support) led to a dependency not being inforced
	   for the original driver (I2C and GPIOLIB).

First round of fixes for IIO in the 4.0 cycle. Note a followup
set dependent on patches in the recent merge windows will follow shortly.

* dht11 - fix a read off the end of an array, add some locking to prevent
          the read function being interrupted and make sure gpio/irq lines
	  are not enabled for irqs during output.
* iadc - timeout should be in jiffies not msecs
* mpu6050 - avoid a null id from ACPI emumeration being dereferenced.
* mxs-lradc - fix up some interaction issues between the touchscreen driver
              and iio driver.  Mostly about making sure that the adc driver
              only affects channels that are not being used for the
              touchscreen.
* ad2s1200 - sign extension fix for a result of c type promotion.
* adis16400 - sign extension fix for a result of c type promotion.
* mcp3422 - scale table was transposed.
* ad5686 - use _optional regulator get to avoid a dummy reg being allocate
           which would cause the driver to fail to initialize.
* gp2ap020a00f - select REGMAP_I2C
* si7020 - revert an incorrect cleanup up and then fix the issue that made
           that cleanup seem like a good idea.

- Y tiling support for scanout from Tvrtko&Damien
- Remove more UMS support
- some small prep patches for OLR removal from John Harrison
- first few patches for dynamic pagetable allocation from Ben Widawsky, rebased
  by tons of other people
- DRRS support patches (Sonika&Vandana)
- fbc patches from Paulo
- make sure our vblank callbacks aren't called when the pipes are off
- various patches all over

A few patches have accumulated, among them the fix for Linus's
four-way-handshake problem. The others are various small fixes
for problems all over, nothing really stands out.

This is the 3.14.34 stable release

This is the 3.18.8 stable release

This is the 3.10.70 stable release

sound fixes for 4.0-rc2

Most of changes in this pull request are about the fixes of crash of
FireWire drivers at hot-unplugging.  In addition, there are a few
HD-audio fixes (removal of wrong static, a pin quirk for an ASUS mobo,
a regression fix for runtime PM on Panther Point) and a long-standing
(but fairly minor) bug of PCM core.

Linux 34.0-rc1

Additional power management and ACPI updates for v3.20-rc1

 - Revert a recent ACPI LPSS driver commit that prevented the touchpad
   driver from loading on Dell XPS13 (Jarkko Nikula).

 - Make the ACPI LPSS driver disable the I2C controllers and deassert
   SPI host controllers resets at startup on Intel BayTrail and Braswell
   SoCs in case they have been left in wrong states by the platform
   firmware which then may casuse fatal controller driver failures during
   resume from hibernation (Mika Westerberg).

 - Make two recently added ACPI EC messages look better (Scot Doyle).

 - Reduce the printk level of a recently added debug message related to
   ACPI resources that may become noisy in some cases (Rafael J Wysocki).

 - Add a new ACPI backlight blacklist entry for Samsung Series 9
   (900X3C/900X3D/900X3E/900X4C/900X4D) laptops where the native backlight
   interface doesn't work while the ACPI based one does (Jens Reyer).

 - Make the PNP sybsystem's core code use __request_region() followed by
   __release_region() instead of __check_region() which then will allow
   us to get rid of the latter as it has no more users (Jakub Sitnicki).

 - Fix a build breakage and an issue with two __init functions that may be
   called after initialization in the s3c cpufreq driver (Arnd Bergmann).

 - Make the powernv cpuidle driver read target_residency values for idle
   states from a Device Tree (as we have the suitable DT bindings for that
   now) and improve the parsing of the powermgmt DT node in that driver
   (Preeti U Murthy).

/

The clock framework changes for 3.20 contain the usual driver additions,
enhancements and fixes mostly for ARM32, ARM64, MIPS and Power-based
devices. Additionaly the framework core underwent a bit of surgery with
two major changes. The boundary between the clock core and clock
providers (e.g clock drivers) is now more well defined with dedicated
provider helper functions. struct clk no longer maps 1:1 with the
hardware clock but is a true per-user cookie which helps us tracker
users of hardware clocks and debug bad behavior. The second major change
is the addition of rate constraints for clocks. Rate ranges are now
supported which are analogous to the voltage ranges in the regulator
framework. Unfortunately these changes to the core created some
breakeage. We think we fixed it all up but for this reason there are
lots of last minute commits trying to undo the damage.

This is the 3.2.67 stable release