Tags

This is the 4.9.122 stable release

This is the 4.4.150 stable release

This is the 4.18.2 stable release

This is the 4.17.16 stable release

This is the 4.14.64 stable release

This is the 4.9.121 stable release

This is the 4.4.149 stable release

This is the 3.18.119 stable release

2 fixes, one for a power-down/re-enabling cycle for a simple plane and another one to not isolate Sean Paul from the world by changing his e-mail address.

media updates for v4.19-rc1

This is the 4.9.120 stable release

This is the 4.14.63 stable release

This is the 4.17.15 stable release

This is the 4.4.148 stable release

This is the 4.18.1 stable release

This is the bulk of GPIO changes for the v4.19 kernel cycle:

Core changes:

- Add a new API for explicitly naming GPIO consumers, when needed.

- Don't let userspace set values on input lines. While we do not
  think anyone would do this crazy thing we better plug the hole
  before someone uses it and think it's a nifty feature.

- Avoid calling chip->request() for unused GPIOs.

New drivers/subdrivers:

- The Mediatek MT7621 is supported which is a big win for OpenWRT
  and similar router distributions using this chip, as it seems
  every major router manufacturer on the planet has made products
  using this chip:
  https://wikidevi.com/wiki/MediaTek_MT7621

- The Tegra 194 is now supported.

- The IT87 driver now supports IT8786E and IT8718F super-IO
  chips.

- Add support for Rockchip RK3328 in the syscon GPIO driver.

Driver changes:

- Handle the get/set_multiple() properly on MMIO chips with
  inverted direction registers. We didn't have this problem
  until a new chip appear that has get/set registers AND
  inverted direction bits, OK now we handle it.

- A patch series making more error codes percolate upward
  properly for different errors on gpiochip_lock_as_irq().

- Get/set multiple for the OMAP driver, accelerating these
  multiple line operations if possible.

- A coprocessor interface for the Aspeed driver. Sometimes a few
  GPIO lines need to be grabbed by a co-processor for doing
  automated tasks, sometimes they are available as GPIO lines.
  By adding an explicit API in this driver we make it possible
  for the two line consumers to coexist. (This work was
  made available on the ib-aspeed branch, which may be appearing
  in other pull requests.)

- Implemented .get_direction() and open drain in the SCH311x
  driver.

- Continuing cleanup of included headers in GPIO drivers.

ACPI updates for 4.19-rc1

 - Revert two ACPICA commits that are not needed any more (Erik
   Schmauss).

 - Rework property graph support in the ACPI device properties
   framework to make it behave more like the analogous DT code
   and update the documentation of it (Sakari Ailus).

 - Change the default ACPI device status after initialization
   to ACPI_STA_DEFAULT instead of 0 (Hans de Goede).

 - Add a special platform driver for enumerating multiple I2C devices
   hooked up to the same object in the ACPI tables (Hans de Goede).

 - Fix the ACPI battery driver to avoid reporting full capacity on
   systems without support for that and clean it up (Hans de Goede,
   Dmitry Rozhkov, Lucas Rangit Magasweran).

 - Add two system wakeup quirks to the ACPI EC driver (Aaron Ma,
   Mika Westerberg).

 - Add the touchscreen on Dell Venue Pro 7139 to the list of "always
   present" devices to make it work (Tristian Celestin).

 - Revert a special tables handling quirk for Dell XPS 9570 and
   Precision M5530 which is not needed any more (Kai Heng Feng).

 - Add support for a new OEM _OSI string to allow system vendors to
   work around issues with NVidia HDMI audio (Alex Hung).

 - Prevent the ACPI button driver from reporting excessive system
   wakeup events and clean it up (Ravi Chandra Sadineni, Randy Dunlap).

 - Clean up two minor code style issues in the ACPI core and GHES
   handling on ARM64 (Dongjiu Geng, John Garry, Tom Todd).

Power management updates for 4.19-rc1

 - Add a new framework for CPU idle time injection (Daniel Lezcano).

 - Add AVS support to the armada-37xx cpufreq driver (Gregory CLEMENT).

 - Add support for current CPU frequency reporting to the ACPI CPPC
   cpufreq driver (George Cherian).

 - Rework the cooling device registration in the imx6q/thermal
   driver (Bastian Stender).

 - Make the pcc-cpufreq driver refuse to work with dynamic
   scaling governors on systems with many CPUs to avoid
   scalability issues with it (Rafael Wysocki).

 - Fix the intel_pstate driver to report different maximum CPU
   frequencies on systems where they really are different and to
   ignore the turbo active ratio if hardware-managend P-states (HWP)
   are in use; make it use the match_string() helper (Xie Yisheng,
   Srinivas Pandruvada).

 - Fix a minor deferred probe issue in the qcom-kryo cpufreq
   driver (Niklas Cassel).

 - Add a tracepoint for the tracking of frequency limits changes
   (from Andriod) to the cpufreq core (Ruchi Kandoi).

 - Fix a circular lock dependency between CPU hotplug and sysfs
   locking in the cpufreq core reported by lockdep (Waiman Long).

 - Avoid excessive error reports on driver registration failures
   in the ARM cpuidle driver (Sudeep Holla).

 - Add a new device links flag to the driver core to make links go
   away automatically on supplier driver removal (Vivek Gautam).

 - Eliminate potential race condition between system-wide power
   management transitions and system shutdown (Pingfan Liu).

 - Add a quirk to save NVS memory on system suspend for the ASUS
   1025C laptop (Willy Tarreau).

 - Make more systems use suspend-to-idle (instead of ACPI S3) by
   default (Tristian Celestin).

 - Get rid of stack VLA usage in the low-level hibernation code on
   64-bit x86 (Kees Cook).

 - Fix error handling in the hibernation core and mark an expected
   fall-through switch in it (Chengguang Xu, Gustavo Silva).

 - Extend the generic power domains (genpd) framework to support
   attaching a device to a power domain by name (Ulf Hansson).

 - Fix device reference counting and user limits initialization in
   the devfreq core (Arvind Yadav, Matthias Kaehlcke).

 - Fix a few issues in the rk3399_dmc devfreq driver and improve its
   documentation (Enric Balletbo i Serra, Lin Huang, Nick Milner).

 - Drop a redundant error message from the exynos-ppmu devfreq driver
   (Markus Elfring).

Devicetree updates for 4.19:

- Remove an obsolete hack for PPC32 longtrail systems

- Make of_io_request_and_map() "name" arg optional

- Add vendor prefixes for bitmain, Asus, and Y Soft

- Remove 'interrupt-parent' from bindings as it is implicit

- New properties for wm8994 audio codec

- Add 'clocks' property support to SRAM binding

- Add binding for ASPEED coprocessor interrupt controller

- Various binding spelling and link fixes

regulator: Changes for v4.19

The biggest set of changes in here is the addition of the Qualcomm RPMH
driver.  As well as the regualtor driver itself being quite large due to
the usual involved Qualcomm regulator stuff there's also some code
shared with the arm-soc tree, a bus driver required to communicate with
the hardware that actually winds up being much larger than the regulator
driver itself and a LLCC driver that was part of the same signed tag
used with the arm-soc tree.

Other than that it's a fairly standard and quiet release, highlights
include:

 - Addition of device links from regulator consumers to their
   regulators, helping the core avoid dependency issues during suspend.
 - Support for the entertainingly innovative suspend implementation in
   the BD9571MWV.
 - Support for switch regulators on the PFUZE100, this required two goes
   due to backwards compatibility issues with old DTs that were
   discovered.
 - Support for Freescale PFUZE3001 and SocioNext UniPhier.
 - The aforementioned Qualcomm RPMH driver together with the driver
   changes required to support it.