Tags

ACPI and power management fixes and cleanups for 3.14-rc1

 - ACPI device hotplug fix preventing ACPI drivers from binding to device
   objects that acpi_bus_trim() has been called for and the devices
   represented by them may not be operational.

 - Recent cpufreq changes related to the "boost" (turbo) feature broke
   the acpi-cpufreq error code path causing a NULL pointer dereference
   to occur on some systems.  Fix from Konrad Rzeszutek Wilk.

 - The log level of a CPU initialization error message added recently
   needs to be reduced, because the particular BIOS issue indicated by
   it turns out to be widespread and doesn't really matter for the
   majority of systems having it.  From Jiang Liu.

 - The regulator API needs to be told to stay away from things on systems
   with ACPI BIOSes or it may conflict with the BIOS' own handling of
   voltage regulators.  Fix from Mark Brown that works around a 3.13
   regression in lm90 on PCs occuring if the regulator API is enabled.

 - Prevent the Exynos4 devfreq driver from being built on multiplatform,
   because it depends on things that aren't available during such builds.
   From Sachin Kamat.

 - Upstream ACPICA doesn't use the bool type as defined in the kernel,
   so modify the kernel's ACPICA code to follow the upstream in that
   respect (only one variable definition is affected) to reduce
   divergences between the two.  From Lv Zheng.

 - Make the ACPI device PM code use ACPI_COMPANION() instead of its own
   routine doing the same thing (and invokng ACPI_COMPANION() in the
   process).

 - Modify some routines in the ACPI processor driver to follow the
   common convention and return negative integers on errors.  From
   Hanjun Guo.

/

IOMMU Updates for Linux v3.14

A few patches have been queued up for this merge window:

	* Improvements for the ARM-SMMU driver
	  (IOMMU_EXEC support, IOMMU group support)
	* Updates and fixes for the shmobile IOMMU driver
	* Various fixes to generic IOMMU code and the
	  Intel IOMMU driver
	* Some cleanups in IOMMU drivers (dev_is_pci() usage)

This is the 3.4.78 stable release

This is the 3.13.1 stable release

This is the 3.12.9 stable release

This is the 3.10.28 stable release

fbdev changes for 3.14

This is a rather boring pull request. There is one new fb driver, OpenCores
VGA/LCD, but other than that it's just minor cleanups and fixes.

- Convert to misc driver to support module auto loading
- Remove unnecessary and dangerous use of device_lock

drm/tegra: Changes for v3.14-rc1 (update)

These patches fix some issues caused by the DRM panel support from the
previous pull request and add two more panels (for the Toshiba AC100 as
well as the Seaboard and Ventana).

Bulk pin control changes for the v3.14 cycle:

- New driver for the Qualcomm TLMM pin controller and its
  msm8x74 subdriver.

- New driver for the Broadcom Capri BCM281xx SoC.

- New subdriver for the imx25 pin controller.

- New subdriver for the Tegra124 pin controller.

- Lock GPIO lines as IRQs for select combined pin control and
  GPIO drivers for baytrail and sirf.

- Some semi-big refactorings and extenstions to the sirf
  driver.

- Lots of patching, cleanup and fixing in the Renesas "PFC"
  driver and associated subdrivers as usual. It is settling
  down a little bit now it seems.

- Minor fixes and incremental updates here and there as usual.

GPIO tree bulk changes for v3.14

A big set this merge window, as we have much going on in
this subsystem. Major changes this time:

- Some core improvements and cleanups to the new GPIO
  descriptor API. This seems to be working now so we can
  start the exodus to this API, moving gradually away from
  the global GPIO numberspace.

- Incremental improvements to the ACPI GPIO core, and move
  the few GPIO ACPI clients we have to the GPIO descriptor
  API right *now* before we go any further. We actually
  managed to contain this *before* we started to litter
  the kernel with yet another hackish global numberspace for
  the ACPI GPIOs, which is a big win.

- The RFkill GPIO driver and all platforms using it have
  been migrated to use the GPIO descriptors rather than
  fixed number assignments. Tegra machine has been migrated
  as part of this.

- New drivers for MOXA ART, Xtensa GPIO32 and SMSC SCH311x.
  Those should be really good examples of how I expect a
  nice GPIO driver to look these days.

- Do away with custom GPIO implementations on a major
  part of the ARM machines: ks8695, lpc32xx, mv78xx0.
  Make a first step towards the same in the horribly
  convoluted Samsung S3C include forest. We expect to
  continue to clean this up as we move forward.

- Flag GPIO lines used for IRQ on adnp, bcm-kona, em,
  intel-mid and lynxpoint.
  This makes the GPIOlib core aware that a certain GPIO line
  is used for IRQs and can then enforce some semantics such
  as disallowing a GPIO line marked as in use for IRQ to be
  switched to output mode.

- Drop all use of irq_set_chip_and_handler_name().
  The name provided in these cases were just unhelpful
  tags like "mux" or "demux".

- Extend the MCP23s08 driver to handle interrupts.

- Minor incremental improvements for rcar, lynxpoint, em
  74x164 and msm drivers.

- Some non-urgent bug fixes here and there, duplicate
  #includes and that usual kind of cleanups.

ACPI and power management updates for 3.14-rc1

 - ACPI core changes to make it create a struct acpi_device object for every
   device represented in the ACPI tables during all namespace scans regardless
   of the current status of that device.  In accordance with this, ACPI hotplug
   operations will not delete those objects, unless the underlying ACPI tables
   go away.

 - On top of the above, new sysfs attribute for ACPI device objects allowing
   user space to check device status by triggering the execution of _STA for
   its ACPI object.  From Srinivas Pandruvada.

 - ACPI core hotplug changes reducing code duplication, integrating the
   PCI root hotplug with the core and reworking container hotplug.

 - ACPI core simplifications making it use ACPI_COMPANION() in the code
   "glueing" ACPI device objects to "physical" devices.

 - ACPICA update to upstream version 20131218.  This adds support for the
   DBG2 and PCCT tables to ACPICA, fixes some bugs and improves debug
   facilities.  From Bob Moore, Lv Zheng and Betty Dall.

 - Init code change to carry out the early ACPI initialization earlier.
   That should allow us to use ACPI during the timekeeping initialization
   and possibly to simplify the EFI initialization too.  From Chun-Yi Lee.

 - Clenups of the inclusions of ACPI headers in many places all over from
   Lv Zheng and Rashika Kheria (work in progress).

 - New helper for ACPI _DSM execution and rework of the code in drivers
   that uses _DSM to execute it via the new helper.  From Jiang Liu.

 - New Win8 OSI blacklist entries from Takashi Iwai.

 - Assorted ACPI fixes and cleanups from Al Stone, Emil Goode, Hanjun Guo,
   Lan Tianyu, Masanari Iida, Oliver Neukum, Prarit Bhargava, Rashika Kheria,
   Tang Chen, Zhang Rui.

 - intel_pstate driver updates, including proper Baytrail support, from
   Dirk Brandewie and intel_pstate documentation from Ramkumar Ramachandra.

 - Generic CPU boost ("turbo") support for cpufreq from Lukasz Majewski.

 - powernow-k6 cpufreq driver fixes from Mikulas Patocka.

 - cpufreq core fixes and cleanups from Viresh Kumar, Jane Li, Mark Brown.

 - Assorted cpufreq drivers fixes and cleanups from Anson Huang, John Tobias,
   Paul Bolle, Paul Walmsley, Sachin Kamat, Shawn Guo, Viresh Kumar.

 - cpuidle cleanups from Bartlomiej Zolnierkiewicz.

 - Support for hibernation APM events from Bin Shi.

 - Hibernation fix to avoid bringing up nonboot CPUs with ACPI EC disabled
   during thaw transitions from Bjørn Mork.

 - PM core fixes and cleanups from Ben Dooks, Leonardo Potenza, Ulf Hansson.

 - PNP subsystem fixes and cleanups from Dmitry Torokhov, Levente Kurusa,
   Rashika Kheria.

 - New tool for profiling system suspend from Todd E Brandt and a cpupower
   tool cleanup from One Thousand Gnomes.

/

Linux 3.13

Last-minute ACPI fix for 3.13

This reverts a commit that causes the Alan Cox' ASUS T100TA to "crash
and burn" during boot if the Baytrail pinctrl driver is compiled in.

/

This is the 3.12.8 stable release

This is the 3.10.27 stable release

This is the 3.4.77 stable release

Linux 3.13-rc8