Tags

This is the 3.10.35 stable release

regulator: Updates for v3.15

This release has lots and lots of small cleanups and fixes in the
regulator subsystem, mainly cleaning up some bad patterns that got
duplicated in DT code, but otherwise very little of note outside
of the scope of the relevant drivers:

 - Support for configuration of the initial state for gpio regulators
   with multi-voltage support.
 - Support for calling regulator_set_voltage() on fixed regulators.
 - New drivers for Broadcom BCM590xx, Freescale pfuze200, Samsung S2MPA01 &
   S2MPS11/4, some PWM controlled regulators found on some ST boards and
   TI TPS65218.

ASoC: Final updates for v3.15 merge window

A few more updates from last week - use of the tdm_slot mapping from
Xiubo plus a few smaller fixes and cleanups.

Pin control bulk changes for the v3.15 series, no new core
functionality this time, just incremental driver updates:

- A large refactoring of the MVEBU (Marvell) driver.

- A large refactoring of the Tegra (nVidia) driver.

- GPIO interrupt including soft edges support in the
  STi driver.

- Misc updates to PFC (Renesas), AT91, ADI2 (Blackfin),
  pinctrl-single, sirf (CSR), msm (Qualcomm), Exynos (Samsung),
  sunxi (AllWinner), i.MX (Freescale), Baytrail.

This is the 3.4.85 stable release

Linux 3.14

This is the 3.12.15 stable release

Linux 3.14-rc8

ASoC: A few more fixes for rcar

Since Linus hasn't done the release yet and Morimoto-san here are some
additional bug fixes for rcar which Morimoto-san sent overnight.

This is the 3.13.7 stable release

This is the 3.10.34 stable release

This is the 3.4.84 stable release

ASoC: Updates for v3.15

A few more updates for the merge window:

 - Fixes for the simple-card DAI format DT mess.
 - A new driver for Cirrus cs42xx8 devices.
 - DT support for a couple more devices.
 - A revert of a previous buggy fix for soc-pcm, plus a few more fixes
   and cleanups.

- Inherit/reuse firmwar framebuffers (for real this time) from Jesse, less
  flicker for fastbooting.
- More flexible cloning for hdmi (Ville).
- Some PPGTT fixes from Ben.
- Ring init fixes from Naresh Kumar.
- set_cache_level regression fixes for the vma conversion from Ville&Chris.
- Conversion to the new dp aux helpers (Jani).
- Unification of runtime pm with pc8 support from Paulo, prep work for runtime
  pm on other platforms than HSW.
- Larger cursor sizes (Sagar Kamble).
- Piles of improvements and fixes all over, as usual.

sound fixes for 3.14

Just two minor bug fixes: a fix for a regression in oxygen driver
that was introduced in 3.14-rc1, and a stable fix for the return
value of compress offload open callback.

Allwinner sunXi SoCs clock changes

This adds support for the new, more correct clock node naming and gets
the A10 compatibles in line with the rest of the other SoCs. It also
adds support for the USB, GMAC and A31's PLL6 clocks. Some of these
changes also require DT modifications that will be merged via arm-soc.

Linux 3.14-rc7

ACPI and power management fixes for 3.14-rc7

 - A recent ACPI resources handling fix overlooked the fact that it had
   to update the ACPI PNP subsystem's resources parsing too and caused
   confusing warning messages to be printed during system intialization
   on some systems (with arguably buggy ACPI tables).  Fix from Zhang Rui.

 - Moving the early ACPI initialization before timekeeping_init() earlier
   in this cycle broke fast TSC calibration on at least one system, so it
   needs to be done later, but still before efi_enter_virtual_mode() to
   allow the EFI initialization to refer to ACPI.

 - A change related to code duplication reduction in the cpufreq core
   inadvertently caused cpufreq intialization to fail for some CPUs
   handled by intel_pstate by adding checks that may fail for that
   driver, but aren't even necessary when it is used.  The issue is
   addressed by preventing those checks from run in the configurations
   in which they aren't needed.

 - If the Hardware Reduced ACPI flag is set in the ACPI tables, system
   suspend, hibernation and ACPI power off will only work when special
   sleep control and sleep status registeres are provided (their
   addresses in the ACPI tables are not zero).  If those registers are
   not available, the features in question have no chances to work,
   so they shouldn't even be regarded as supported.  That helps with
   power off in particular, because alternative power off methods may
   be used then and they may actually work.

/