Tags

Qualcomm Device Tree Changes for v4.11

* Add Coresight components for APQ8064
* Fixup PM8058 nodes
* Add APQ8060 gyro and accel support
* Enable SD600 HDMI support
* Add RIVA supprort for Sony Yuga and SD600
* Add PM8821 support
* Add MSM8974 ADSP, USB gadget, SMD, and SMP2P support
* Fix IPQ8064 clock frequencies

Qualcomm ARM Based defconfig Updates for v4.11

* Enable APQ8060 Dragonboard related devices
* Enable AHCI, PCIE, USB, thermal sensors, and ATL1C related configs
* Enable RPM/RPM-SMD clocks

Qualcomm ARM Based Driver Updates for v4.11

* Fix issues with SCM compile testing
* Add SCM set remote state API
* Mask APQ8064 SCM clock dependency issue
* Add Qualcomm DMA folder to MAINTAINERS
* Fix EBI2 dependencies

GPIO fixes for v4.10:

- Fix a lockdep issue: the threaded irqchips also need their unique
  key, and take this opportunity to get rid of the horrible macro and
  replace it with a static inline.

Final block of feature work for 4.11:

- gen8 pd cleanup from Matthew Auld
- more cleanups for view/vma (Chris)
- dmc support on glk (Anusha Srivatsa)
- use core crc api (Tomue)
- track wedged requests using fence.error (Chris)
- lots of psr fixes (Nagaraju, Vathsala)
- dp mst support, acked for merging through drm-intel by Takashi
  (Libin)
- huc loading support, including uapi for libva to use it (Anusha
  Srivatsa)

drm fixes across the board

Linux 4.10-rc5

This is the 4.4.44 stable release

This is the 4.9.5 stable release

Linux 3.18.47

Linux 4.1.38

Linux 4.10-rc4

This is the 4.9.4 stable release

This is the 4.4.43 stable release

This is the 4.9.3 stable release

This is the 4.4.42 stable release

Allwinner fixes for 4.10

A few fixes here and there to enable the build of some DT leftover, prevent
display issues or setup a proper muxing.

wireless-drivers fixes for 4.10

Only two fixes at this time. The rtlwifi fix is an important one as it
fixes a reported oops and Linus was already asking about it. The
orinoco fix is not tested on a real device, because it's old legacy
hardware and hardly no-one use it, but it should fix a (theoretical)
issue with VMAP_STACK.