Tags

This is the 3.2.53 stable release

GPIO fixes for the v3.13 series:

- A big slew of documentation for the gpiod transition that
  happened in the merge window, no semantic effect, but we should
  provide proper documentation with the new API.

- Fix flags related to the new API.

- Fix to the find_chip_by_name() lookup function related to the
  new API.

- Fix of_find_gpio() when not using device tree.

- Bug fix for the TB10x direction setting.

- Error path fixes from Dan Carpenter.

- Nasty IRQdomain bug relating to taking an unitialized spinlock.

- Minor fixes here and there.

ACPI and power management fixes for 3.13-rc2

 - Fix for a recent regression in the Tegra cpufreq driver causing
   excess error messages to be printed from Stephen Warren.

 - ACPI-based device hotplug fix to prevent conflicting notify handlers
   from being installed for PCI host bridge objects.  From Toshi Kani.

 - ACPICA update to upstream version 20131115.  This contains bug fixes
   mostly (loop termination fix for the get AML length function, fixes
   related to namespace node removal and debug output).  From Bob Moore,
   Tomasz Nowicki and Lv Zheng.

 - Removal of incorrect inclusions of internal ACPICA header files by
   non-ACPICA code from Lv Zheng.

 - Fixes for the ACPI sysfs interface exposing tables to user space
   from Daisuke Hatayama and Jeremy Compostella.

 - Assorted ACPI and cpufreq cleanups from Sachin Kamat and Al Stone.

 - cpupower tool fix and man page from Thomas Renninger.

/

First set of new features, drivers and cleanups for IIO in the 3.14 cycle.
This mostly consists of patches that didn't quite make the last cycle. Lots
of interesting things under review currently.

Core:
- Add devm_iio_device_register/unregister.  I took some convincing on whether
  there would be many devices that really were simple enough to need no
  explicit actions on removal.  Turns out there are some.
- Move some stray docs to above the relevant implemenation.
- Drop a redundant repeated check on the fact the trigger has actually changed
  when there is a userspace attempt change it.

Drivers:
New drivers
- Freescale MPL3115A2 Pressure / temperature sensor

New functionality
- hid_sensors: add sensitivity support.

DT bindings
- tsl2563
- hmc5843

Cleanups
- Drop unused scan_type from viperboard adc driver.
- devm_iio_device_register used in viperboard, ad5421, ad5755, adis16130,
  adxrs450, vcnl4000, adis16220, ad7816, lpc32xx, adt7316, adis16060, isl29018
  and ad2s1200.  Note that this was proposed in a number of other drivers
  and this revealed a number of missorderings in remove functions.  Also for
  now I have blocked this on any device that any hardware suspend suport on
  the basis that we probably want to power down devices if they have no driver
  support loaded.

First round of fixes for IIO in the 3.13 cycle.

The usual mixed bag of fixes.

* 3 cases where kconfig dependencies were missing.  We need to keep a closer
  eye on this in new drivers.

* hid_sensors was abusing the iio_dev->trigger pointer.  We had a round
  of clearing this out some time ago but this driver clearly slipped through.

* A misuse of the IIO_ST macro, in mcp3422, which we should really make a
  concertive effort to finish removing.

* Avoid a double free introduced by recent buffer reference counting in the
  one driver that (quite reasonably!) does things differently (am335x)

* A missing mutex_unlock in kxsd9 that means that driver has been non
  functional for some time and no one noticed (including me who for once
  actually has one of the supported devices).

* An incorrect assumption about the parameters of sign_extend32 in mcp3422.

So nothing controversial.  The only substantial patch is the hid_sensors
one and that is actually just adding a new pointer to the devices private
state then moving the code over to it.

regulator: Fixes for v3.13

A bunch of fixes, a few driver specific ones and a framework fix for
voltage enumeration on fixed voltage regulators which had previously
worked but had been misplaced during some refactoring causing problems
for users that needed to know the voltage.

Linux 3.13-rc1

sound fixes #2 for 3.13-rc1

A collection of small fixes in HD-audio quirks and runtime PM, ASoC
rcar, abs8500 and other codecs.  Most of commits are for stable
kernels, too.

This is the 3.12.1 stable release

This is the 3.11.9 stable release

This is the 3.10.20 stable release

This is the 3.4.70 stable release

More ACPI and power management updates for 3.13-rc1

- ACPI-based device hotplug fixes for issues introduced recently and
  a fix for an older error code path bug in the ACPI PCI host bridge
  driver.

- Fix for recently broken OMAP cpufreq build from Viresh Kumar.

- Fix for a recent hibernation regression related to s2disk.

- Fix for a locking-related regression in the ACPI EC driver from
  Puneet Kumar.

- System suspend error code path fix related to runtime PM and
  runtime PM documentation update from Ulf Hansson.

- cpufreq's conservative governor fix from Xiaoguang Chen.

- New processor IDs for intel_idle and turbostat and removal of
  an obsolete Kconfig option from Len Brown.

- New device IDs for the ACPI LPSS (Low-Power Subsystem) driver and
  ACPI-based PCI hotplug (ACPIPHP) cleanup from Mika Westerberg.

- Removal of several ACPI video DMI blacklist entries that are not
  necessary any more from Aaron Lu.

- Rework of the ACPI companion representation in struct device and
  code cleanup related to that change from Rafael J Wysocki,
  Lan Tianyu and Jarkko Nikula.

- Fixes for assigning names to ACPI-enumerated I2C and SPI devices
  from Jarkko Nikula.

/

sound fixes for 3.13-rc1

Two peaks in diffstat are for the audio EQ init of IDT codecs and the
EMU2004 usb mixer addition, both of which are pretty device-specific,
so safe to apply.  The rest are a bunch of small fixes, most of them
are regression fixes.

IOMMU Updates for Linux v3.13

This time the updates contain:

* Tracepoints for certain IOMMU-API functions to make
  their use easier to debug
* A tracepoint for IOMMU page faults to make it easier
  to get them in user space
* Updates and fixes for the new ARM SMMU driver after
  the first hardware showed up
* Various other fixes and cleanups in other IOMMU drivers

Here are the 3.13 KVM changes.  There was a lot of work on the PPC
side: the HV and emulation flavors can now coexist in a single kernel
is probably the most interesting change from a user point of view.
On the x86 side there are nested virtualization improvements and a
few bugfixes.  ARM got transparent huge page support, improved
overcommit, and support for big endian guests.

Finally, there is a new interface to connect KVM with VFIO.  This
helps with devices that use NoSnoop PCI transactions, letting the
driver in the guest execute WBINVD instructions.  This includes
some nVidia cards on Windows, that fail to start without these
patches and the corresponding userspace changes.

fbdev changes for 3.13

Nothing particularly stands out in this pull request. The biggest part of the
changes are cleanups.

Maybe one fix to mention is the "fb: reorder the lock sequence to fix potential
dead lock" which hopefully fixes the fb locking issues reported by multiple
persons.

There are also a few commits that have changes to arch/arm/mach-at91 and
arch/avr32, which have been acked by the maintainers.

This is the 3.11.8 stable release

This is the 3.10.19 stable release