linux: mm: Triage non-applicable BSP 4.1.x display commits as Abandoned tasks

Move display-related BSP 4.1.x upport candidates that are considered not
to be applicable to upstream to abandoned tasks. This allows grouping
commits logically, providing more detailed comments than the non-target
file.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

12 files changed, 177 insertions, 0 deletions

diff --git a/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-hotplug-support.yaml b/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-hotplug-support.yaml
new file mode 100644
index 0000000..273f9c6
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-hotplug-support.yaml
@@ -0,0 +1,13 @@
+title: "BSP 4.1.x upport: drm/bridge: adv7511: Add hotplug support"
+team: MM
+key: 9a07b143-a810-4338-8c68-f082fe39ce08
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 0f987e5a275b623b842b0ec8588624c273a3538c # drm: adv7511: Enable HPD interrupts to support hotplug
+
+comments:
+ - The change is incorrect according to the ADV7511 datasheet, as bits 5 and 6
+   are documented as reserved and required to be set to 1. More information is
+   needed to know if this should be upported, and why.
diff --git a/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-suspend-resume-support.yaml b/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-suspend-resume-support.yaml
new file mode 100644
index 0000000..4588cfa
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_drm-bridge-adv7511-Add-suspend-resume-support.yaml
@@ -0,0 +1,12 @@
+title: "BSP 4.1.x upport: drm/bridge: adv7511: Add suspend/resume support"
+team: MM
+key: 3f540771-0339-4165-a6a0-e044043ce0cf
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - e773484765f0ccde590690cbf2ac0cbfdabef291 # drm/bridge: adv7511: Add function of suspend and resume
+
+comments:
+ - The DU driver disables the display pipeline on suspend, no special handling
+   is needed in the adv7511 driver
diff --git a/projects/linux/mm/done/bsp41x_r8a779[78]0-Enable-dual-link-LVDS.yaml b/projects/linux/mm/done/bsp41x_r8a779[78]0-Enable-dual-link-LVDS.yaml
new file mode 100644
index 0000000..a7f6687
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_r8a779[78]0-Enable-dual-link-LVDS.yaml
@@ -0,0 +1,12 @@
+title: "BSP 4.1.x upport: r8a779[78]x: Enable dual link LVDS"
+team: MM
+key: 5a382a67-8390-49cf-bda7-392f0730bd62
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 7556e081e01cfd0e1108676605b28b9ea1912bc6 # arm64: dts: renesas: v3x: Set thc63lvd1024 dual link mode
+
+comments:
+ - This is a hack to overclock the THC63LVDS1024, dual-link mode isn't actually
+   in operation. If overclocking is required, it should be handled differently.
diff --git a/projects/linux/mm/done/bsp41x_r8a779xx-Add-display-panel-to-DT.yaml b/projects/linux/mm/done/bsp41x_r8a779xx-Add-display-panel-to-DT.yaml
new file mode 100644
index 0000000..f403b12
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_r8a779xx-Add-display-panel-to-DT.yaml
@@ -0,0 +1,23 @@
+title: "BSP 4.1.x upport: r8a779xx: Add display panel to DT"
+team: MM
+key: 1cec3027-3193-44f5-8da1-916aac7f7e57
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 71f9cc45c79ebe8f09ded3fba10cd92372ec99b4 # arm64: dts: r8a77965-salvator-x: Add lvds node for du
+ - 0d2393b4987872ca7aa336313347221bbd6b1028 # arm64: dts: r8a7796-salvator-x: Add lvds node for du
+ - 29a312314c4ab9e5008a50a75b75f3df49f06ea0 # arm64: dts: r8a7795-salvator-x: Add lvds node for du
+ - f12522c1e1e6af8988d3b0862eb8e37e6dd3656c # arm64: dts: r8a7795-es1-salvator-x: Add lvds node for du
+ - 2f825210fc02b952a7fe2553a0d298218680f7cf # arm64: dts: salvator-common: Add lvds driver relation node
+ - a2fe679df3f7dc400425fd5079c95ac51fe3536d # arm64: dts: r8a77995-draak: Enable display driver relation node
+ - f140da5a610ab866d8f1781213baa5e16772588e # arm64: dts: r8a77990-ebisu: Add LVDS panel nodes
+
+comments:
+ - None of those boards have a fixed display panel. As this is meant to support
+   a configurable hardware option, the best solution is to support panels
+   through DT overlays.
+
+   While the Linux kernel doesn't support applying overlays at runtime, they
+   can be applied to the device tree either at build time (with the fdtoverlay
+   tool), or by U-Boot before booting the kernel.
diff --git a/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml b/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml
new file mode 100644
index 0000000..6e39b5a
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_r8a779xx-ulcb-Fix-source-clock-for-DU.yaml
@@ -0,0 +1,16 @@
+title: "BSP 4.1.x upport: r8a779xx-ulcb: Fix source clock for DU"
+team: MM
+key: 194edb13-53ca-436d-aa57-7b56a38c2b68
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - ac9c016b8ed5d22c76d1caa389a2ce9895ddbbd3 # arm64: dts: r8a77965-m3nulcb: Fix source clock for DU
+ - dcd9de3348cb79719c79eef6f7eb98b86ec5a8dc # arm64: dts: r8a7796-m3ulcb: Fix souce clock for DU
+ - 0dd514568ab43a3dbb12d6841190062f459f0705 # arm64: dts: r8a7795-h3ulcb: Fix souce clock for DU
+ - 95d2ee008fb96ac8def7471a4870a16f8bbf2f32 # arm64: dts: r8a7795-h3ulcb: Fix source clock for DU2
+
+comments:
+ - These commits are workarounds, as stated in the commit messages. If the
+   issue is still present, it should be addressed in the clk-versaclock5
+   driver. More information is needed about what is broken.
diff --git a/projects/linux/mm/done/bsp41x_rcar-du-Add-writeback-support.yaml b/projects/linux/mm/done/bsp41x_rcar-du-Add-writeback-support.yaml
new file mode 100644
index 0000000..b6369a5
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_rcar-du-Add-writeback-support.yaml
@@ -0,0 +1,14 @@
+title: "BSP 4.1.x upport: rcar-du: Disable unused DPAD outputs"
+team: MM
+key: 116a688e-e51d-4455-bdf9-5fb8fa364d55
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 922f13d41561664c61411bdb5264cd08c33492cf # v4l: vsp1: Add write back support
+
+upstream:
+ - torvalds: 12e32f554d8ddd121f17aaaa9cda25d0be612af9 # drm: rcar-du: Add writeback support for R-Car Gen
+
+comments:
+ - Writeback support already upstream, using the DRM/KMS writeback API.
diff --git a/projects/linux/mm/done/bsp41x_rcar-du-Assign-VSPDL-planes-to-single-CRTC.yaml b/projects/linux/mm/done/bsp41x_rcar-du-Assign-VSPDL-planes-to-single-CRTC.yaml
new file mode 100644
index 0000000..2a92183
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_rcar-du-Assign-VSPDL-planes-to-single-CRTC.yaml
@@ -0,0 +1,21 @@
+title: "BSP 4.1.x upport: rcar-du: Assign VSPDL planes to single CRTC"
+team: MM
+key: 8c3875a2-fb1f-427d-8c36-5dce3e0b39fb
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - b46748099c0d2c9bebfc9cf2301d727a25d78edf # drm: rcar-du: Fix possible crtcs for plane when using VSPDL
+ - e8ac6d4fbdd4977ea343106a9ce68f85086caee6 # arm64: dts: r8a77965: Add brs option
+ - fb183191b068d4862d0a519b5d306281366ef4a9 # arm64: dts: r8a7795: Add brs option
+
+comments:
+ - DRM/KMS doesn't support moving planes between active CRTCs, and fails atomic
+   commits that attempt to do so (with a message printed to the kernel log if
+   debugging is enabled). These commits attempt to address the problem by not
+   sharing planes between CRTCs in the first place.
+
+   Userspace shouldn't attempt to move planes between active CRTCs in the first
+   place, as this isn't allowed. The issue needs to be fixed in userspace, not
+   by disabling plane sharing between CRTCs as that's a potentially useful
+   feature.
diff --git a/projects/linux/mm/done/bsp41x_rcar-du-Fix-DPLL-clock-divider.yaml b/projects/linux/mm/done/bsp41x_rcar-du-Fix-DPLL-clock-divider.yaml
new file mode 100644
index 0000000..de22004
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_rcar-du-Fix-DPLL-clock-divider.yaml
@@ -0,0 +1,11 @@
+title: "BSP 4.1.x upport: rcar-du: Fix DPLL clock divider"
+team: MM
+key: b6a411f3-f38f-4db4-b3ce-02dd870ebdc6
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 42beaeb93347eab04ad468dd243e164ce0b01360 # drm: rcar-du: Fix DPLL clock divider judgement
+
+comments:
+ - More information about the exact problem is needed.
diff --git a/projects/linux/mm/done/bsp41x_rcar-du-Force-VGA-connector-status.yaml b/projects/linux/mm/done/bsp41x_rcar-du-Force-VGA-connector-status.yaml
new file mode 100644
index 0000000..956bc17
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_rcar-du-Force-VGA-connector-status.yaml
@@ -0,0 +1,18 @@
+title: "BSP 4.1.x upport: rcar-du: Force VGA connector status"
+team: MM
+key: 849f1c56-7958-4e2c-bbe4-bc77a29504f1
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 7e6a484db71f1a0b936d62671ca64c5845bb52b0 # drm/bridge: dumb-vga-dac: Add connector status setting option
+ - 100b9c3cdb870203098d2d5e531c208d231ac63f # arm64: dts: r8a77995-draak: Add no use ddc option for VGA connector
+ - d713bb0b4dff0d4439d282253232634adb3f023a # arm64: dts: r8a77990-ebisu: Add no use ddc option for VGA connector
+ - ca7c7682bb2c4a1fb169465d71233f3bb33daafa # arm64: dts: salvator-common: Add no use ddc option for VGA connector
+
+comments:
+ - The kernel shouldn't cheat when it can't detect the monitor, userspace
+   should be able to cope with connectors have an unknown state. If there's a
+   valid reason why userspace can't handle these connectors correctly, the
+   exact reason and use case needs to be reported, to be discussed with
+   upstream.
diff --git a/projects/linux/mm/done/bsp41x_rcar-du-Rework-error-handling-to-avoid-warnings.yaml b/projects/linux/mm/done/bsp41x_rcar-du-Rework-error-handling-to-avoid-warnings.yaml
new file mode 100644
index 0000000..471f29f
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_rcar-du-Rework-error-handling-to-avoid-warnings.yaml
@@ -0,0 +1,13 @@
+title: "BSP 4.1.x upport: rcar-du: Rework error handling to avoid warnings"
+team: MM
+key: ce89f99f-60e5-41c8-8a60-1d0dc2514957
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 9dfcca631e0cfe409ade8a84e3f929752c7656c9 # drm/rcar_du: rework error handling in to avoid warnings
+
+comments:
+ - "This shouldn't be needed anymore since torvalds
+   ea6aae151887070936a7bc5c91654bd8845335a0 ('drm: rcar-du: Embed drm_device in
+   rcar_du_device')."
diff --git a/projects/linux/mm/done/bsp41x_vsp-Add-alpha-blending-support.yaml b/projects/linux/mm/done/bsp41x_vsp-Add-alpha-blending-support.yaml
new file mode 100644
index 0000000..0d8ac75
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_vsp-Add-alpha-blending-support.yaml
@@ -0,0 +1,13 @@
+title: "BSP 4.1.x upport: vsp: Add alpha blending support"
+team: MM
+key: aaf5739d-d893-4fdc-bec6-c222063cc4d1
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - 35d8bdb4bcc29c27967f86a72779af1f87408833 # v4l: vsp1: Add pixel alpha blending supoprt
+
+comments:
+ - Alpha blending is already supported upstream. The use case for this change
+   isn't clear, and is needed to decide whether addition upstream work is
+   required.
diff --git a/projects/linux/mm/done/bsp41x_vsp-Add-vmute-function.yaml b/projects/linux/mm/done/bsp41x_vsp-Add-vmute-function.yaml
new file mode 100644
index 0000000..bb47b40
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_vsp-Add-vmute-function.yaml
@@ -0,0 +1,11 @@
+title: "BSP 4.1.x upport: vsp: Add vmute function"
+team: MM
+key: dfa05cf1-bcda-473d-bc59-0af57f444868
+status: Abandoned
+assignee: Laurent
+
+bsp41x:
+ - a72679bdc5908055684d24ef052f3607d620607b # v4l: vsp1: Add Vmute function support
+
+comments:
+ - More information about use case is needed.