projects: linux: mm: Validate max VGA dot clock

Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

1 files changed, 29 insertions, 0 deletions

diff --git a/projects/linux/mm/bsp392_validate-max-vga-dot-clock.yaml b/projects/linux/mm/bsp392_validate-max-vga-dot-clock.yaml
new file mode 100644
index 0000000..7c4369a
--- /dev/null
+++ b/projects/linux/mm/bsp392_validate-max-vga-dot-clock.yaml
@@ -0,0 +1,29 @@
+title: "Validate max VGA dot clock"
+team: MM
+key: c2bfaee0-0695-4119-805a-085158941815
+status: Abandoned
+assignee: Simon
+
+relationships:
+
+bsp-commits:
+  - 6c59e13ad0dbc11c40e0120104eb2c80ecea3b52 # arm64: dts: r8a77995-draak: Set max dot clock for vga
+  - ab99897bb0960d6988ae72ce156379e7187fce2a # arm64: dts: salvator-common: Set max dot clock for vga
+  - 27aafebfab0452e2025ad480e6cbc206473c1c78 # arm64: dts: r8a77990-ebisu: Set max dot clock for vga
+  - 59c65194d7306634450c5cabe7f615e4c96a42b8 # drm/brdige: dumb-vga-dac: Add dot clock valid check
+
+comments:
+  - These patches are not suitable for upstream in their current form
+
+    The maximum dot clock frequency isn't a property of the VGA connector,
+    rather, it is a property of the DU and/or the LVDS encoders. It seems
+    most appropriate to make it a property of the DU in which case it
+    should not be specified in DT, but rather be included in the driver in
+    the crtc .mode_valid() operation.
+
+    Furthermore, the values in the BSP seem quite low and it is suggested
+    that they are validated against the hardware limits derived from the DU.
+    And as discuss the results of the investigation with the BSP team
+    as necessary.
+
+  - Above text is derived from a conversation with Laurent.