Tags

The first round of IIO fixes for the 3.11 cycle.

This set is larger than I would like, partly due to my lack of review
time in the weeks before the merge window and partly because a
couple of large drivers and the subsystem as a whole seem to be
getting a lot more exposure and testing recently.

1) A long term bug in trigger handling gave a double free of the device.

2) Wrong return value handling means offsets are ignored in
   iio_convert_raw_to_processed_unlocked.

3) The iio_channel_has_info utility function was incorrectly updated
   during the recent info_mask split, this is now fixed.

4) mxs-lradc has a couple of little fixes.

5) A couple of missing .driver_module entries meant that drivers
   could be removed from underneath their users.

6) Error path fixes for ad7303 and lis3l02dq.

7) The scale value for presure in the lps331ap driver was out by
   a factor of 100.

Linux 3.11-rc1

This is the 3.10.1 stable release

This is the 3.9.10 stable release

This is the 3.4.53 stable release

This is the 3.0.86 stable release

More power management and ACPI updates for 3.11-rc1

- Fix for a recent cpufreq regression that caused WARN() to trigger
  overzealously in a couple of places and spam the kernel log with
  useless garbage as a result.  From Viresh Kumar.

- ACPI dock fix removing a discrepancy between the definition of
  acpi_dock_init(), which says that the function returns int, and
  its header in the header file, which says that it is a void
  function.  The function is now defined as void too.

- ACPI PM fix for failures to update device power states as needed,
  for example, during resume from system suspend, because the old
  state was deeper than the new one, but the new one is not D0.

- Fix for two debug messages in the ACPI power resources code that
  don't have a newline at the end and make the kernel log difficult
  to read.  From Mika Westerberg.

- Two ACPI cleanups from Naresh Bhat and Haicheng Li.

- cpupower updates from Thomas Renninger, including Intel Haswell
  support improvements and a new idle-set subcommand among other
  things.

/

vfio Updates for v3.11

Largely hugepage support for vfio/type1 iommu and surrounding cleanups and fixes.

regulator: Fixes for the merge window

A set of small fixes for issues noticed during the merge window, all
very much non-invasive.

IOMMU Updates for Linux 3.11

A few updates this time, most important and exiciting (to me) is:

	* The new ARM SMMU driver. This is a common IOMMU driver that will
	  hopefully be used in a lot of upcoming ARM chips. So the mess in the
	  past where every SOC had its own IOMMU will be over.

Besides that:

	* Some important fixes in the IOMMU unmap path. There are fixes in the
	  common code and also in the AMD IOMMU driver.
	* Other random fixes

This is the 3.0.85 stable release

This is the 3.4.52 stable release

This is the 3.9.9 stable release

regulator: Updates for v3.11

Very quiet release here, as well as the usual driver specific updates
only a couple of new things:

 - New drivers for TI ABB LDOs and MAX77693 PMICs.
 - Support for enabling bypass mode support via device tree.

ARM SoC specific changes

These changes are all to SoC-specific code, a total of 33 branches on
17 platforms were pulled into this. Like last time, Renesas sh-mobile
is now the platform with the most changes, followed by OMAP and EXYNOS.

Two new platforms, TI Keystone and Rockchips RK3xxx are added in
this branch, both containing almost no platform specific code at all,
since they are using generic subsystem interfaces for clocks, pinctrl,
interrupts etc. The device drivers are getting merged through the
respective subsystem maintainer trees.

One more SoC (u300) is now multiplatform capable and several others
(shmobile, exynos, msm, integrator, kirkwood, clps711x) are moving
towards that goal with this series but need more work.

Also noteworthy is the work on PCI here, which is traditionally part of
the SoC specific code. With the changes done by Thomas Petazzoni, we can
now more easily have PCI host controller drivers as loadable modules and
keep them separate from the platform code in drivers/pci/host. This has
already led to the discovery that three platforms (exynos, spear and imx)
are actually using an identical PCIe host controller and will be able
to share a driver once support for spear and imx is added.

Conflicts:
* asm/glue-proc.h has one CPU type getting added that conflicts
  with another addition in 3.10-rc7
* Simple context changes in arch/arm/Makefile and arch/arm/Kconfig

ARM SoC device tree changes

These changes from 30 individual branches for the most part update device
tree files, but there are also a few source code changes that have crept
in this time, usually in order to atomically move over a driver from
using hardcoded data to DT probing.

A number of platforms change their DT files to use the C preprocessor,
which is causing a bit of churn, but that is hopefully only this once.

There are a few conflicts with the other branches unfortunately:

* in exynos5440.dtsi and kirkwood-6281.dtsi, device nodes are added
  from multiple branches. Need to be careful to have the right
  set of closing braces as git gets this one wrong.

* In kirkwood.dtsi, one 'ranges' line got split into two lines, while
  another line got added. Order of the lines does not matter.

* in sama5d3.dtsi, some cleanup was merged the wrong way, causing
  a bogus conflict. We want the 'dmas' and 'dma-names' properties
  to get added here.

* Two lines got removed independently in arch/arm/mach-mxs/mach-mxs.c

* Contents get added independently in arch/arm/mach-omap2/cclock33xx_data.c

ARM SoC cleanups

This contains cleanups as preparation for other branches adding new
features, we pulled 16 branches for 9 platforms into this one.

Most notable here is the removal of support for ATAGS based OMAP4
systems. Since all OMAP4 machines are fully functional with DT based
booting in 3.10, we can remove a lot of code here.

Also noteworthy is Maxime Ripard's cleanup of the machine descriptors,
which means we need no machine descriptors in a lot more cases and
can boot additional machines by just having the respective device
drivers enabled.

ARM SoC board specific changes

These are 18 branches on 9 platforms with board specific changes, mostly
for defconfig files, but nothing really exciting in here.

Since the shmobile platform still uses board files for some of the newer
machines, we get a few changes there as the result of drivers getting
enabled for those boards. This causes some conflicts with contents getting
added from multiple branches in sh-mobile specific files. Renesas is
putting a lot of work into migrating to device-tree based setup, which
will make all those files obsolete in the future and avoid both the
conflicts and the need to have these files in the first place.

ARM SoC late changes

These are changes that arrived a little late before the merge
window or that have multiple dependencies on previous branches
so they did not fit into one of the earlier ones. There
are 10 branches merged here, a total of 39 non-merge commits.
Contents are a mixed bag for the above reasons:

* Two new SoC platforms: ST microelectronics stixxxx and
  the TI 'Nspire' graphing calculator. These should have
  been in the 'soc' branch but were a little late
* Support for the Exynos 5420 variant in mach-exynos,
  which is based on the other exynos branches to avoid
  conflicts.
* Various small changes for sh-mobile, ux500 and davinci
* Common clk support for MSM

Conflicts:
* In Kconfig.debug, various additions trivially conflict,
  the list should be kept in alphabetical order when
  resolving.