Bug 2446622

1. Please describe the problem:
Some of the Lenovo 2026 platforms have hit issues with specific panels where panel_replay does not work correctly.
This has been fixed by Intel upstream so looking to backport the fixes into the 6.19 kernel for inclusion in the Fedora preloads for those systems.

This bug is to track the fixes - I'll submit a MR to kernel-ark shortly (just wrapping up testing)

List of commits needed:
f861e54 - Add-panel-granularity-information-into-
1cc85464 - psr-Use-SU-granularity-information-availabl
5a423626 - Compute-Panel-Replay-Adaptive-Sync-coex
8d251442 - Move-pr_dpcd-and-psr_dpcd-to-intel_conn
a7e427ff - Clear-pr_dpcd-as-well-on-disconnect
93bba79e - Move-Panel-Replay-DSC-sink-support-data
2691ec67 - Move-sink-PSR-and-Panel-Replay-booleans
11bbc345 - Move-sink_sync_latency-to-intel_connect
1f5df537 - Set-plane-id-bit-in-crtc_state-async_fl
e540c47f - Perform-full-frame-update-on-async-flip
d400dad6 - display-Allow-async-flip-when-Selective-Fet
ace7dcc8 - Add-definition-for-Panel-Replay-full-line-gra
a99cac46 - Fix-for-Panel-Replay-X-granularity-DPCD

I reviewed the patch list with the Intel engineer who wrote them to confirm complete.
Tested on a T14 G7 Intel.

2. What is the Version-Release number of the kernel:
7.0

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
No

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Didn't test - but it's fixed in 7.0-rc3 so probably not.

6. Are you running any modules that not shipped with directly Fedora's kernel?:


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.