Tags

Linux 3.12-rc4

Third set of new functionality and cleanups for IIO in the 3.13 cycle.

Driver New Functionality
* MXS - new interrupt driven touch screen support for i.MX23/28. Old
  polled implementation dropped.

Driver Cleanups
* Some spi_sync boilerplate dropped by using spi_sync_transfer
* Some switching of drivers to the fractional type for scale reading.
  Moves the ugly calculation into one place.
* Fix the documentation for *_voltage_scale which is never been correct
  or as implemented in any driver.
* HID sensor hub and children : Open the sensor hub only when someone cares.
* hmc5843 - various minor

Fixes for the GPIO tree for v3.12:
- Two patches for the OMAP driver, dealing with setting up IRQs
  properly on the device tree boot path.

This is the 3.11.4 stable release

This is the 3.10.15 stable release

This is the 3.4.65 stable release

This is the 3.0.99 stable release

ACPI and power management fixes for 3.12-rc4

 1) The resume part of user space driven hibernation (s2disk) is now
    broken after the change that moved the creation of memory bitmaps
    to after the freezing of tasks, because I forgot that the resume
    utility loaded the image before freezing tasks and needed the
    bitmaps for that.  The fix adds special handling for that case.

 2) One of recent commits changed the export of acpi_bus_get_device()
    to EXPORT_SYMBOL_GPL(), which was technically correct but broke
    existing binary modules using that function including one in
    particularly widespread use.  Change it back to EXPORT_SYMBOL().

 3) The intel_pstate driver sometimes fails to disable turbo if its
    no_turbo sysfs attribute is set.  Fix from Srinivas Pandruvada.

 4) One of recent cpufreq fixes forgot to update a check in cpufreq-cpu0
    which still (incorrectly) treats non-NULL as non-error.  Fix from
    Philipp Zabel.

 5) The SPEAr cpufreq driver uses a wrong variable type in one place
    preventing it from catching errors returned by one of the functions
    called by it.  Fix from Sachin Kamat.

/

IOMMU Fixes for Linux v3.12-rc3

A couple of fixes from the IOMMU side:

	* Some small fixes for the new ARM-SMMU driver
	* A register offset correction for VT-d
	* Adding MAINTAINERS entry for drivers/iommu

Overall no really big or intrusive changes.

Pin control fixes for the v3.12 series:

- Various build warning fixes.

- Correct the S5P pin count.

- Handle BIAS_DEFAULT properly in the Palmas driver.

This is the 3.11.3 stable release

This is the 3.10.14 stable release

This is the 3.4.64 stable release

This is the 3.0.98 stable release

Second set of IIO fixes for the 3.12 cycle (take 2)

A few small fixes:
1) Make sure that debugfs entries are removed early enough to prevent
a race.
2) Drop a stray regulator_put from ad8366 left over from the devm_ patches.
3) The ST magnetometer driver had incorrect register addresses for the
   actual data channels.

regulator: Fixes for v3.12

Quite a few fixes here, mostly small driver specific ones.  The stand
out thing is a fix for errors generating the documentation from Randy
Dunlap, otherwise unless you're using the driver in question there
should be no impact.

Linux 3.12-rc3

Second set of new functionality for IIO in the 3.13 cycle - with bug fixes for first set.

This is a small, mainly to get a couple of compile bug related fixes into
the tree ASAP.

New device support:
1) Add ad5446 dac support to the ad5641 driver.

New functionality and cleanups:
1) Optional power supply regulators for the st pressure sensors drivers using
   the new optional regulator interface.
2) Bit of tidying up of naming in the sysfs trigger.

Bug fixes from the previous series:
1) Missing select IIO_BUFFER for ti_am335x_adc
2) Drop a bonus bracket in iio-trig-bfin-timmer

ACPI and power management fixes for 3.12-rc3

 1) After recent locking changes in the cpufreq core it is possible
    to trigger BUG_ON(!policy) in lock_policy_rwsem_read() if
    cpufreq_get() is called before registering a cpufreq driver.
    Fix from Viresh Kumar.

 2) If intel_pstate has been loaded already, it doesn't make sense
    to do anything in acpi_cpufreq_init() and moreover doing something
    in there in that case may be harmful, so make that function return
    immediately if another cpufreq driver is already present.  From
    Yinghai Lu.

 3) The ACPI IPMI driver sometimes attempts to acquire a mutex from
    interrupt context, which can be avoided by replacing that mutex
    with a spinlock.  From Lv Zheng.

 4) A NULL pointer may be dereferenced by the exynos5440 cpufreq
    driver if a memory allocation made by it fails.  Fix from
    Sachin Kamat.

 5) Hanjun Guo's commit fixes a typo in the kerneldoc comment
    documenting acpi_bus_unregister_driver().

/

Small fbdev fixes for various fb drivers