Tags

ACPI and power management fixes for 3.14-rc6

 - ACPI tables in some BIOSes list device resources with size equal
   to 0, which doesn't make sense, so we should ignore them, but
   instead we try to use them and mangle things completely.  Fix
   from Zhang Rui.

 - Several models of Samsung laptops accumulate EC events when they
   are in sleep states which leads to EC buffer overflows that prevent
   new events from being signaled after system resume or reboot.  This
   has been affecting many users for quite a while and may be addressed
   by clearing the EC buffer during system resume and system startup on
   those machines.  From Kieran Clancy.

 - If the ACPI sleep control and status registers are not present
   (which  happens if the Hardware Reduced ACPI mode bit is set in
   the ACPI tables, but also may result from BIOS bugs), we should
   not try to use ACPI to power off the system and ACPI S5 should
   not be listed as supported.  Fix from Aubrey Li.

 - There's a race condition in cpufreq_get() that leads to a kernel
   crash if that function is called at a wrong time.  Fix from
   Aaron Plattner.

 - cpufreq policy objects have to be initialized entirely before
   they are first accessed by their users which isn't the case
   currently and that potentially leads to various kinds of
   breakage that is difficult to debug.  Fix from Viresh Kumar.

 - Locking is missing in __cpufreq_add_dev() which leads to a race
   condition that may trigger a kernel crash.  Fix from Viresh Kumar.

/

- fine-grained display power domains for byt (Imre)
- runtime pm prep patches for !hsw from Paulo
- WiZ hashing flag updates from Ville
- ppgtt setup cleanup and enabling of full 4G range on bdw (Ben)
- fixes from Jesse for the inherited intial config code
- gpu reset code improvements from Mika
- per-pipe num_planes refactoring from Damien
- stability fixes around bdw forcewake handling and other bdw w/a from Mika and
  Ken
- and as usual a pile of smaller fixes all over

This is the 3.13.6 stable release

This is the 3.10.33 stable release

A set of pin control fixes for the v3.14 series:

- Fix chained interrupts, interrupt masking and register offset
  calculation for the sunxi driver.

- Make MSM a bool rather than a tristate to stop build problems
  to happen - chained interrupt controllers cannot currently be
  defined in modules.

- Fix a clock in the PFC driver.

- Fix a kernel panic in the sirf driver.

Allwinner DT patches for 3.15, take 1:
  - Add SPI controllers for all the SoCs
  - Add various missing aliases
  - Add USB clocks nodes
  - Addition of the GMAC support
  - Introduction of the pcDuino board
  - A few DT cleanup patches: change of compatibles,

Two fixes for device trees additions that got added in 3.14. One fixes the
interrupt types of some IPs, the other fixes up a compatible that got
introduced during 3.14

Linux 3.14-rc5

ACPI and power management fixes for 3.14-rc5

 - One of the recent intel_pstate driver fixes introduced a rounding
   error that on some systems causes the frequency to be stuck at the
   lowest level forever.  Fix from Dirk Brandewie.

 - The firmware_class driver's PM notifier doesn't handle the
   PM_RESTORE_PREPARE event during hibernation image restore and that
   leads to a deadlock on umhelper_sem in __usermodehelper_disable().
   Fix from Sebastian Capella.

 - acpi_processor_set_throttling() abuses set_cpus_allowed_ptr() in a
   nasty way which triggers the WARN_ON_ONCE() in wq_worker_waking_up()
   among other things.  Fix from Lan Tianyu.

/

ASoC: Updates for v3.14

A few more driver specific bug fixes, all driver specific things that
only affect users of those devices.

drm: DisplayPort AUX framework for v3.15-rc1

This series of patches implements a small framework that abstracts away
some of the functionality that the DisplayPort AUX channel provides. It
comes with a set of generic helpers that use the driver implementations
to reduce code duplication.

Linux 3.14-rc4

ASoC: Fixes for v3.14

A somewhat large set of fixes here due to the identification of some
systematic problems with hard to use APIs in the subsystem.  Takashi did
a lot of work to address the enumeration API which uncovered a number of
off by one bugs caused by confusing APIs while Charles addressed issues
in the locking around DAPM.

This is the 3.13.5 stable release

This is the 3.12.13 stable release

This is the 3.10.32 stable release

This is the 3.4.82 stable release

ACPI and power management fixes for 3.14-rc4

 - Fix for a recent probing regression in the nouveau driver introduced
   by an ACPI change related to the handling of _DSM from Jiang Liu.

 - Fix for a dock station sysfs attribute that stopped working correctly
   after recent changes in the ACPI core.

 - cpufreq fix taking care of broken code related to CPU removal and
   overlooked by a previous recent fix in that area.  From Viresh Kumar.

 - Two intel_pstate fixes related to Baytrail support added during
   the 3.13 cycle (candidates for -stable) from Dirk Brandewie.

 - ACPI video fix removing duplicate brightness values from the _BCL
   table which makes its user space interface behave sanely.  From
   Hans de Goede.

 - Fix for the powernow-k8 cpufreq driver making it initialize its
   per-CPU data structures correctly from Srivatsa S. Bhat.

 - Fix for an obscure memory leak in the ACPI PCI interrupt allocation
   code (related to ISA) from Tomasz Nowicki.

 - ACPI video blacklist changes moving several systems that should
   use the native backlight interface instead of the ACPI one from
   the general ACPI _OSI blacklist the the ACPI video driver's
   blacklist where they belong.  This consists of an ACPI video
   driver update from Aaron Lu and a revert of a previous commit
   adding systems to the ACPI _OSI blacklist requested by Takashi Iwai.

 - Several fixes for build issues in ACPI drivers occuring when
   CONFIG_PM_SLEEP is unset from Shuah Khan.

 - Fix for an sscanf() format string in the ACPI Smart Battery
   Subsystem (SBS) driver from Luis G.F.

/