Tags

regulator: Fixes for v4.0

Two fixes here, one typo fix in the documentation and one fix for a
system hang with one of the Palmas chips caused by the use of an
incorrect offset being provided for one of the registers.

iwlwifi:

* avoid panic with lots of IBSS stations
* Fix dvm's behavior after suspend resume
* Allow to keep connection after CSA failure
* Remove a noisy by harmless WARN_ON
* New device IDs

rtlwifi:

* fix IOMMU mapping leak in AP mode

brcmfmac:

* disable MBSS feature for BCM43362 to get AP mode working again

ath9k:

* disable Transmit Power Control (TPC) again due to regressions

* fix beaconing issue with AP+STA setup

Linux 3.18.10

Linaro 15.03

Linux 4.0-rc5

Staging driver fixes for 4.0-rc5

Here are 4 small staging driver fixes, all for the vt6656 and vt6655
drivers, that resolve some reported issues with them.

All of these patches have been in linux next for a while.

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

Power management and ACPI fixes for v4.0-rc5

 - Revert a recent PCI commit related to IRQ resources management
   that introduced a regression for drivers attempting to bind to
   devices whose previous drivers did not balance pci_enable_device()
   and pci_disable_device() as expected (Rafael J Wysocki).

 - Fix a deadlock in at91_rtc_interrupt() introduced by a typo in a
   recent commit related to wakeup interrupt handling (Dan Carpenter).

 - Allow the power capping RAPL (Running-Average Power Limit) driver
   to use different energy units for domains within one CPU package
   which is necessary to handle Intel Haswell EP processors correctly
   (Jacob Pan).

 - Improve the cpuidle mvebu driver's handling of Armada XP SoCs by
   updating the target residency and exit latency numbers for those
   chips (Sebastien Rannou).

 - Prevent the cpuidle mvebu driver from calling cpu_pm_enter() twice
   in a row before cpu_pm_exit() is called on the same CPU which
   breaks the core's assumptions regarding the usage of those
   functions (Gregory Clement).

/

More DeviceTree fixes for 4.0:

- Revert setting stdout-path as preferred console. This caused
regressions in PowerMACs and other systems.

- Yet another fix for stdout-path option parsing.

- Fix error path handling in of_irq_parse_one

This is the 3.12.39 stable release

This is the 3.19.2 stable release

This is the 3.14.36 stable release

This is the 3.10.72 stable release

sound fixes for 4.0-rc5

This is a collection of many small fixes.  Most of fixes are for ASoC
drivers, including the fixes of wrong field usages for boolean kctls.

In addition, there is a fix in ASoC core for adding proper locks for
component lists, and a fix for a HD-audio regression by the previous
mono channel fix.

- EU count report param for gen9+ (Jeff McGee)
- piles of pll/wm/... fixes for chv, finally out of preliminary hw support
  (Ville, Vijay)
- gen9 rps support from Akash
- more work to move towards atomic from Matt, Ander and others
- runtime pm support for skl (Damien)
- edp1.4 intermediate link clock support (Sonika)
- use frontbuffer tracking for fbc (Paulo)
- remove ilk rc6 (John Harrison)
- a bunch of smaller things and fixes all over

regulator: Fixes for v4.0

The two main fixes here from Javier and Doug both fix issues seen on the
Exynos-based ARM Chromebooks with reference counting of GPIO regulators
over system suspend.  The GPIO enable code didn't properly take account
of this cases (a full analysis is in Doug's commit log).  This is fixed
by both fixing the reference counting directly and by making the resume
code skip enables it doesn't need to do.  We could skip the change in
the resume code but it's a very simple change and adds extra robustness
against problems in other drivers.

ASoC: Fixes for v4.0

As well as the usual collection of driver specific fixes there's a few
more generic things:

 - Lots of fixes from Takashi for drivers using the wrong field in the
   control union to communicate with userspace, leading to potential
   errors on 64 bit systems.
 - A fix from Lars for locking of the lists of devices we maintain,
   mostly only likely to trigger during device probe and removal.

Here are a few fixes that I'd like to still get in:
 * disable U-APSD for better interoperability, from Michal Kazior
 * drop unencrypted frames in mesh forwarding, from Bob Copeland
 * treat non-QoS/WMM HT stations as non-HT, to fix confusion when
   they connect and then get QoS packets anyway due to HT
 * fix counting interfaces for combination checks, otherwise the
   interface combinations aren't properly enforced (from Andrei)
 * fix pure ECSA by reacting to the IE change
 * ignore erroneous (E)CSA to the current channel which sometimes
   happens due to AP/GO bugs