Tags

This is the bulk of GPIO changes for the v4.1 development
cycle:

- A new GPIO hogging mechanism has been added. This can
  be used on boards that want to drive some GPIO line high,
  low, or set it as input on boot and then never touch it
  again. For some embedded systems this is bliss and
  simplifies things to a great extent.

- Some API cleanup and closure: gpiod_get_array() and
  gpiod_put_array() has been added to get and put GPIOs
  in bulk as was possible with the non-descriptor API.

- Encapsulate cross-calls to the pin control subsystem in
  <linux/gpio/driver.h>. Now this should be the only header
  any GPIO driver needs to include or something is wrong.
  Cleanups restricting drivers to this include are welcomed
  if tested.

- Sort the GPIO Kconfig and split it into submenus, as
  it was becoming and unstructured, illogical and
  unnavigatable mess. I hope this is easier to follow.
  Menus that require a certain subsystem like I2C can
  now be hidden nicely for example, still working on
  others.

- New drivers:

    - New driver for the Altera Soft GPIO.

    - The F7188x driver now handles the F71869 and
      F71869A variants.

    - The MIPS Loongson driver has been moved to
      drivers/gpio for consolidation and cleanup.

- Cleanups:

   - The MAX732x is converted to use the GPIOLIB_IRQCHIP
     infrastructure.

   - The PCF857x is converted to use the GPIOLIB_IRQCHIP
     infrastructure.

   - Radical cleanup of the OMAP driver.

- Misc:

   - Enable the DWAPB GPIO for all architectures. This is
     a "hard IP" block from Synopsys which has started to
     turn up in so diverse architectures as X86 Quark, ARC
     and a slew of ARM systems. So even though it's not an
     expander, it's generic enough to be available for all.

   - We add a mock GPIO on Crystalcove PMIC after a long
     discussion with Daniel Vetter et al, tracing back to
     the shootout at the kernel summit where DRM drivers
     and sub-componentization was discussed. In this case
     a mock GPIO is assumed to be the best compromise
     gaining some reuse of infrastructure without making
     DRM drivers overly complex at the same time. Let's
     see.

ACPICA updates for v4.1-rc1

 - Fix for a GPE handling regression on Dell Latitude D600 that
   caused GPE signaling to stop working on that machine, which
   appears to be due to a hardware glitch, but it used to work
   and it can be made work again in a relativly straightforward
   way (Rafael J Wysocki).

 - Fix for a mutex unlock regression related to the handling of ACPI
   tables introduced during the 3.16 development cycle (Octavian Purdila).

 - _REV modification to always return 2 which has been done by all
   versions of Windows since NT and the firmware people started to
   use it to distinguish between OSes in their AML and do some silly
   and wrong things on that basis (Bob Moore).

 - Fixes and cleanups related to the acpi_physicall_address data type
   including one stable-candidate fix for an issue occasionally occuring
   on 64-bit machines running 32-bit kernels where using offsets provided
   by the firmware may lead to address overflows (Lv Zheng).

 - External() opcode support infrastructure needed for recompiling
   disassembled ACPI tables in some cases including interpreter
   modification to ignore that opcode (Bob Moore).

 - Support for the "Windows 2015" string in _OSI (Bob Moore).

 - GPE debug interface change to return values read from hardware
   registers (Lv Zheng).

 - Removal of the __DATE__ macro usage in tools (Rasmus Villemoes).

 - Assorted minor fixes and cleanups (Lv Zheng, Rickard Strandqvist,
   Bob Moore).

/

sound updates for 4.1-rc1

There have been major modernization with the standard bus: in ALSA
sequencer core and HD-audio.  Also, HD-audio receives the regmap
support replacing the in-house cache register cache code.  These
changes shouldn't impact the existing behavior, but rather
refactoring.

In addition, HD-audio got the code split to a core library part and
the "legacy" driver parts.  This is a preliminary work for adapting
the upcoming ASoC HD-audio driver, and the whole transition is still
work in progress, likely finished in 4.1.

Along with them, there are many updates in ASoC area as usual, too:
lots of cleanups, Intel code shuffling, etc.

Here are some highlights:

ALSA core:
- PCM: the audio timestamp / wallclock enhancement
- PCM: fixes in DPCM management
- Fixes / cleanups of user-space control element management
- Sequencer: modernization using the standard bus

HD-audio:
- Modernization using the standard bus
- Regmap support
- Use standard runtime PM for codec power saving
- Widget-path based power-saving for IDT, VIA and Realtek codecs
- Reorganized sysfs entries for each codec object
- More Dell headset support

ASoC:
- Move of jack registration to the card level
- Lots of ASoC cleanups, mainly moving things from the CODEC level
  to the card level
- Support for DAPM routes specified by both the machine driver and DT
- Continuing improvements to rcar
- pcm512x enhacements
- Intel platforms updates
- rt5670 updates / fixes
- New platforms / devices: some non-DSP Qualcomm platforms, Google's
  Storm platform, Maxmim MAX98925 CODECs and the Ingenic JZ4780 SoC

Misc:
- ice1724: Improved ESI W192M support
- emu10k1: Emu 1010 fixes/enhancement

Power management and ACPI updates for v4.1-rc1

 - Generic PM domains support update including new PM domain
   callbacks to handle device initialization better (Russell King,
   Rafael J Wysocki, Kevin Hilman).

 - Unified device properties API update including a new mechanism
   for accessing data provided by platform initialization code
   (Rafael J Wysocki, Adrian Hunter).

 - ARM cpuidle update including ARM32/ARM64 handling consolidation
   (Daniel Lezcano).

 - intel_idle update including support for the Silvermont Core in
   the Baytrail SOC and for the Airmont Core in the Cherrytrail and
   Braswell SOCs (Len Brown, Mathias Krause).

 - New cpufreq driver for Hisilicon ACPU (Leo Yan).

 - intel_pstate update including support for the Knights Landing
   chip (Dasaratharaman Chandramouli, Kristen Carlson Accardi).

 - QorIQ cpufreq driver update (Tang Yuantian, Arnd Bergmann).

 - powernv cpufreq driver update (Shilpasri G Bhat).

 - devfreq update including Tegra support changes (Tomeu Vizoso,
   MyungJoo Ham, Chanwoo Choi).

 - powercap RAPL (Running-Average Power Limit) driver update
   including support for Intel Broadwell server chips (Jacob Pan,
   Mathias Krause).

 - ACPI device enumeration update related to the handling of the
   special PRP0001 device ID allowing DT-style 'compatible' property
   to be used for ACPI device identification (Rafael J Wysocki).

 - ACPI EC driver update including limited _DEP support (Lan Tianyu,
   Lv Zheng).

 - ACPI backlight driver update including a new mechanism to allow
   native backlight handling to be forced on non-Windows 8 systems
   and a new quirk for Lenovo Ideapad Z570 (Aaron Lu, Hans de Goede).

 - New Windows Vista compatibility quirk for Sony VGN-SR19XN (Chen Yu).

 - Assorted ACPI fixes and cleanups (Aaron Lu, Martin Kepplinger,
   Masanari Iida, Mika Westerberg, Nan Li, Rafael J Wysocki).

 - Fixes related to suspend-to-idle for the iTCO watchdog driver and
   the ACPI core system suspend/resume code (Rafael J Wysocki, Chen Yu).

 - PM tracing support for the suspend phase of system suspend/resume
   transitions (Zhonghui Fu).

 - Configurable delay for the system suspend/resume testing facility
   (Brian Norris).

 - PNP subsystem cleanups (Peter Huewe, Rafael J Wysocki).

/

This is the 3.4.107 stable release

regulator: Updates for v4.1

Another release, another set of regulator updates.  Not much of it is
showing up in the code yet but there's been a lot of discussion going on
about how to enhance the regulator API to work better with modern SoCs
which have a microcontroller sitting between Linux and the hardware.
I'm hopeful that'll start to come through into mainline for v4.2 but
it's not quite there for v4.1 - what we do have (along with the usual
small updates is) is:

 - Work from Bjorn Andersson on refactoring the configuration of
   regulator loading interfaces to be useful for use with
   microcontrollers, the existing interfaces were never actually useful
   for anything as-is since nobody was willing to put enough data into
   public code.
 - A summary tree display in debugfs from Heiko Stübner.
 - Support for act6000 regulators.

This is the 3.19.4 stable release

This is the 3.14.38 stable release

This is the 3.10.74 stable release

ASoC: Updates for v4.1

More updates for v4.1, pretty much all drivers:

 - Lots of cleanups from Lars, mainly moving things from the CODEC level
   to the card level.
 - Continuing improvements to rcar from Morimoto-san, pcm512x from
   Howard and Peter, the Intel platforms from Vinod, Jie, Jin and Han,
   and to rt5670 from Bard.
 - Support for some non-DSP Qualcomm platforms, Google's Storm
   platform, Maxmim MAX98925 CODECs and the Ingenic JZ4780 SoC.

Linux 4.0

ASoC: Last minute fix for v4.0

This patch backs out a change that came in during the merge window which
selects a configuration for GPIO4 on pcm512x CODECs that may not be
suitable for all systems using the device.  Changes for v4.1 will make
this properly configurable but for now it's safest to revert to the
v3.19 behaviour and leave the pin configuration alone.

Sorry for sending this direct at the last minute but due to the GPIO
misuse it'd be really good to get it in the release and I'd not realised
it hadn't been sent yet - between some travel, a job change and other
non-urgent fixes coming in I'd lost track of the urgency.  It's been in
-next for several weeks now, is isolated to the driver and fairly clear
to inspection.

The most interesting bit here is irqfd/ioeventfd support for ARM and ARM64.

ARM/ARM64: fixes for live migration, irqfd and ioeventfd support (enabling
vhost, too), page aging

s390: interrupt handling rework, allowing to inject all local interrupts
via new ioctl and to get/set the full local irq state for migration
and introspection.  New ioctls to access memory by virtual address,
and to get/set the guest storage keys.  SIMD support.

MIPS: FPU and MIPS SIMD Architecture (MSA) support.  Includes some patches
from Ralf Baechle's MIPS tree.

x86: bugfixes (notably for pvclock, the others are small) and cleanups.
Another small latency improvement for the TSC deadline timer.

There isn't much left, but we have
 * new mac80211 internal software queue to allow drivers to have
   shorter hardware queues and pull on-demand
 * use rhashtable for mac80211 station table
 * minstrel rate control debug improvements and some refactoring
 * fix noisy message about TX power reduction
 * fix continuous message printing and activity if CRDA doesn't respond
 * fix VHT-related capabilities with "iw connect" or "iwconfig ..."
 * fix Kconfig for cfg80211 wireless extensions compatibility

sound fixes for 4.0

Here are fixes gathered for 4.0-final; one FireFire endian fix, two
USB-audio quirks, and three HD-audio quirks.

All relatively small and device-specific fixes, should be pretty safe
to apply.

- cdclk handling cleanup and fixes from Ville
- more prep patches for olr removal from John Harrison
- gmbus pin naming rework from Jani (prep for bxt)
- remove ->new_config from Ander (more atomic conversion work)
- rps (boost) tuning and unification with byt/bsw from Chris
- cmd parser batch bool tuning from Chris
- gen8 dynamic pte allocation (Michel Thierry, based on work from Ben Widawsky)
- execlist tuning (not yet all of it) from Chris
- add drm_plane_from_index (Chandra)
- various small things all over

Power management and ACPI fixes for v4.0-rc8

 - Revert a 3.17 hibernate commit that was supposed to fix an issue
   related to e820 reserved regions, but broke resume from hibernation
   on Lenovo x230 (Rafael J Wysocki).

 - Prevent the ACPI cpuidle driver from overwriting the name and
   description of the C0 state set by the core when the list of
   C-states changes (Thomas Schlichter).

 - Remove the no longer needed state_count field from struct cpuidle_device
   which prevents the list of C-states shown by the sysfs interface from
   becoming incorrect when the current number of them is different from
   the number of C-states on boot (Bartlomiej Zolnierkiewicz).

 - The cpufreq core updates the policy object of the only online CPU
   during system resume to make it reflect the current hardware state,
   but it always assumes that CPU to be CPU0 which need not be the
   case, so fix the code to avoid that assumption (Viresh Kumar).

/

This is the 3.12.40 stable release