Tags

amd-drm-fixes-5.6-2020-03-18:

amdgpu:
- VCN clockgating fixes
- GPR debugfs fix for umr
- GPU reset fix
- eDP fix for MBP
- DCN2.x fix

One more fix for v5.6:
- drm/lease: fix WARNING in idr_destroy

drm-misc-fixes for v5.6:
- Fix AVI frame colorimetry in the dw-hdmi bridge.
- Fix compiler warning in komeda by annotating functions as __maybe_unused.
- Downgrade bochs pci_request_region failure from error to warning to
  workaround firmware fb.

This is the 5.5.10 stable release

This is the 5.4.26 stable release

This is the 4.19.111 stable release

drm-misc-next for 5.7:

UAPI Changes:

Cross-subsystem Changes:

Core Changes:
  - dp-mst: Remove register_connector callback, add drm_dp_destroy_connector
  - Changes to scnprintf on multiple instances

Driver Changes:
  - meson: Support for YUV420
  - panel: Support Ortustech COM37H3M, idk-1110wr and idk-2121wr,
           multiple dotclock fixes

This is the 4.19.110 stable release

Linux 5.6-rc6

drm fixes for 5.6-rc6

core:
- DP MST bandwidth regression fix.

i915:
- hard lockup fix
- GVT fixes
- 32-bit alignment issue fix
- timeline wait fixes
- cacheline_retire and free

amdgpu:
- Update the display watermark bounding box for navi14
- Fix fetching vbios directly from rom on vega20/arcturus
- Navi and renoir watermark fixes

exynos:
- iommu object cleanup fix

`

UAPI Changes: None

Cross-subsystem Changes: None

Core Changes: Fixed regressions introduced by commit cd82d82cbc04
("drm/dp_mst: Add branch bandwidth validation to MST atomic check"),
which would cause us to:

* Calculate the available bandwidth on an MST topology incorrectly, and
  as a result reject most display configurations that would try to enable
  more then one sink on a topology
* Occasionally expose MST connectors to userspace before finishing
  probing their PBN capabilities, resulting in us rejecting display
  configurations because we assumed briefly that no bandwidth was
  available

Driver Changes: None

UAPI Changes: None

Cross-subsystem Changes: None

Core Changes: Fixed some issues introduced by commit cd82d82cbc04
("drm/dp_mst: Add branch bandwidth validation to MST atomic check"),
which caused the DP MST helpers to incorrectly reject display
configurations in drm_dp_mst_atomic_check() as a result of
miscalculating the available bandwidth. Additionally, another issue that
was required for this to work was fixed where we would reject display
configurations because we would accidentally expose MST connectors to
userspace before having probed their available bandwidth.

Driver Changes: None

This is the 5.4.25 stable release

This is the 5.5.9 stable release

UAPI Changes: None

Cross-subsystem Changes: None

Core Changes: Re-write the bandwidth helper checks in
drm_dp_mst_atomic_check() to fix some regressions that were introduced
by commit cd82d82cbc04 ("drm/dp_mst: Add branch bandwidth validation to
MST atomic check"). This was put into a topic branch per-request of
airlied.

Driver Changes: None

amd-drm-fixes-5.6-2020-03-11:

amdgpu:
- Update the display watermark bounding box for navi14
- Fix fetching vbios directly from rom on vega20/arcturus
- Navi and renoir watermark fixes

This is the 4.14.173 stable release

This is the 4.19.109 stable release

This is the 4.9.216 stable release

This is the 4.4.216 stable release