Tags

This is the 3.9.9 stable release

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.

ARM SoC non-cricitical bug fixes

These are various bug fixes that were not considered important enough
for merging into 3.10. The majority of the ARM fixes are for the OMAP
and at91 platforms, and there is another set of bug fixes for device
drivers that resolve 'randconfig' build errors and that the subsystem
maintainers either did not pick up or preferred to get merged through
the arm-soc tree.

KVM fixes for 3.11

On the x86 side, there are some optimizations and documentation updates.
The big ARM/KVM change for 3.11, support for AArch64, will come through
Catalin Marinas's tree.  s390 and PPC have misc cleanups and bugfixes.

There is a conflict due to "s390/pgtable: fix ipte notify bit" having
entered 3.10 through Martin Schwidefsky's s390 tree.  This pull request
has additional changes on top, so this tree's version is the correct one.

Pin control changes for the v3.11 kernel cycle:

- A large slew of improvements of the Genric pin configuration
  support, and deployment in four different platforms:
  Rockchip, Super-H PFC, ABx500 and TZ1090. Support BIAS_BUS_HOLD,
  get device tree parsing and debugfs support into shape.

- We also have device tree support with generic naming conventions
  for the generic pin configuration.

- Delete the unused and confusing direct pinconf API. Now state
  transitions is *the* way to control pins and multiplexing.

- New drivers for Rockchip, TZ1090, and TZ1090 PDC.

- Two pin control states related to power management are now
  handled in the device core: "sleep" and "idle", removing a lot
  of boilerplate code in drivers. We do not yet know if this is
  the final word for pin PM, but it already make things a lot
  easier to handle.

- Handle sparse GPIO ranges passing a list of disparate pins, and
  utilize these in the new BayTrail (x86 Atom SoC) driver.

- Make the sunxi (AllWinner) driver handle external interrupts.

- Make it possible for pinctrl-single to handle the case where
  several pins are managed by a single register, and augment it to
  handle sleep modes.

- Cleanups and improvements for the abx500 drivers.

- Move Sirf pin control drivers to their own directory, support
  save/restore of context and add support for the SiRFatlas6 SoC.

- PMU muxing for the Dove pinctrl driver.

- Finalization and support for VF610 in the i.MX6 pinctrl driver.

- Smoothen out various Exynos rough edges.

- Generic cleanups of various kinds.

Power management and ACPI updates for 3.11-rc1

- Hotplug changes allowing device hot-removal operations to fail
  gracefully (instead of crashing the kernel) if they cannot be
  carried out completely.  From Rafael J Wysocki and Toshi Kani.

- Freezer update from Colin Cross and Mandeep Singh Baines targeted
  at making the freezing of tasks a bit less heavy weight operation.

- cpufreq resume fix from Srivatsa S Bhat for a regression introduced
  during the 3.10 cycle causing some cpufreq sysfs attributes to
  return wrong values to user space after resume.

- New freqdomain_cpus sysfs attribute for the acpi-cpufreq driver to
  provide information previously available via related_cpus from
  Lan Tianyu.

- cpufreq fixes and cleanups from Viresh Kumar, Jacob Shin,
  Heiko Stübner, Xiaoguang Chen, Ezequiel Garcia, Arnd Bergmann, and
  Tang Yuantian.

- Fix for an ACPICA regression causing suspend/resume issues to
  appear on some systems introduced during the 3.4 development cycle
  from Lv Zheng.

- ACPICA fixes and cleanups from Bob Moore, Tomasz Nowicki, Lv Zheng,
  Chao Guan, and Zhang Rui.

- New cupidle driver for Xilinx Zynq processors from Michal Simek.

- cpuidle fixes and cleanups from Daniel Lezcano.

- Changes to make suspend/resume work correctly in Xen guests from
  Konrad Rzeszutek Wilk.

- ACPI device power management fixes and cleanups from Fengguang Wu
  and Rafael J Wysocki.

- ACPI documentation updates from Lv Zheng, Aaron Lu and Hanjun Guo.

- Fix for the IA-64 issue that was the reason for reverting commit
  9f29ab1 and updates of the ACPI scan code from Rafael J Wysocki.

- Mechanism for adding CMOS RTC address space handlers from Lan Tianyu
  (to allow some EC-related breakage to be fixed on some systems).

- Spec-compliant implementation of acpi_os_get_timer() from
  Mika Westerberg.

- Modification of do_acpi_find_child() to execute _STA in order to
  to avoid situations in which a pointer to a disabled device object
  is returned instead of an enabled one with the same _ADR value.
  From Jeff Wu.

- Intel BayTrail PCH (Platform Controller Hub) support for the ACPI
  Intel Low-Power Subsystems (LPSS) driver and modificaions of that
  driver to work around a couple of known BIOS issues from
  Mika Westerberg and Heikki Krogerus.

- EC driver fix from Vasiliy Kulikov to make it use get_user() and
  put_user() instead of dereferencing user space pointers blindly.

- Assorted ACPI code cleanups from Bjorn Helgaas, Nicholas Mazzuca and
  Toshi Kani.

- Modification of the "runtime idle" helper routine to take the return
  values of the callbacks executed by it into account and to call
  rpm_suspend() if they return 0, which allows some code bloat
  reduction to be done, from Rafael J Wysocki and Alan Stern.

- New trace points for PM QoS from Sahara <keun-o.park@windriver.com>.

- PM QoS documentation update from Lan Tianyu.

- Assorted core PM code cleanups and changes from Bernie Thompson,
  Bjorn Helgaas, Julius Werner, and Shuah Khan.

- New devfreq driver for the Exynos5-bus device from Abhilash Kesavan.

- Minor devfreq cleanups, fixes and MAINTAINERS update from
  MyungJoo Ham, Abhilash Kesavan, Paul Bolle, Rajagopal Venkat, and
  Wei Yongjun.

- OMAP Adaptive Voltage Scaling (AVS) SmartReflex voltage control
  driver updates from Andrii Tseglytskyi and Nishanth Menon.

/

Linux 3.10

This is the 3.2.48 stable release

This is the 3.4.51 stable release

This is the 3.9.8 stable release

This is the 3.0.84 stable release

KVM/ARM pull request for 3.11 merge window

Late power management and ACPI fixes for 3.10

- Fix for an ACPI dock regression introduced by the recent rework of
  the ACPI-based PCI hotplug code (acpiphp) that caused it to be
  initialized before the ACPI dock driver from Jiang Liu.

- Fix for PCI resources allocation in the ACPI-based PCI hotplug code
  (acpiphp) that makes it use the same PCI resources assignment rules
  during runtime hotplug that are used during boot from Jiang Liu.

- Fix for ordering and synchronization issues during hot-removal of
  PCI devices on docking stations from Rafael J Wysocki.

- Fix for a regression that removed the code to register a hotplug
  notificaion handler for for ATA ports/devices inadvertently from
  Aaron Lu.

- Fix for a recent cpufreq regression causing a NULL pointer
  dereference to trigger in od_set_powersave_bias() in some
  situations from Jacob Shin.

/

Now that we have a generic arch hook for broadcast we can remove the local
timer API entirely. Doing so will reduce code in ARM core, reduce the
architecture dependencies of our timer drivers, and simplify the code because
we no longer go through an architecture layer that is essentially a hotplug
notifier.

Now that we have a generic arch hook for broadcast we can remove the local
timer API entirely. Doing so will reduce code in ARM core, reduce the
architecture dependencies of our timer drivers, and simplify the code because
we no longer go through an architecture layer that is essentially a hotplug
notifier.

MSM clock updates for 3.11.

Per Stephen Boyd's coverletter:

Resending to collect higher level maintainer acks per Olof's request.
The plan is to push this patchset through MSM to the arm-soc tree.

This patchset moves the existing MSM clock code and affected drivers
to the common clock framework. A prerequisite of moving to the common
clock framework is to use clk_prepare() and clk_enable() so the first
few patches migrate drivers to that call (clk_prepare() is a no-op on
MSM right now). It also removes some custom clock APIs that MSM
provides and finally moves the proc_comm clock code to the common
struct clk.

This patch series will be used as the foundation of the MSM 8660/8960
clock code that I plan to send out after this series.