summaryrefslogtreecommitdiff
path: root/projects/linux/mm
diff options
context:
space:
mode:
authorJacopo Mondi <jacopo@jmondi.org>2021-03-09 16:12:33 +0100
committerJacopo Mondi <jacopo@jmondi.org>2021-03-21 18:06:16 +0100
commitda223cd497b6cca427fce0ac0153e394349df733 (patch)
tree0727a156b3bf68acabd58f4e538fc73273d692ed /projects/linux/mm
parent05c227d91540884187bad99808b2872244e30f1c (diff)
linux: mm: Add bsp41x_validate-max-vga-dot-clock
Add a task to track the max VGA dot clock handling. Text copied from mm/bsp392_validate-max-vga-dot-clock.yaml task The selected patches have been moved to bsp-41x-non-target.yaml ticket. Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
Diffstat (limited to 'projects/linux/mm')
-rw-r--r--projects/linux/mm/done/bsp41x_validate-max-vga-dot-clock.yaml32
1 files changed, 32 insertions, 0 deletions
diff --git a/projects/linux/mm/done/bsp41x_validate-max-vga-dot-clock.yaml b/projects/linux/mm/done/bsp41x_validate-max-vga-dot-clock.yaml
new file mode 100644
index 0000000..00bc5f8
--- /dev/null
+++ b/projects/linux/mm/done/bsp41x_validate-max-vga-dot-clock.yaml
@@ -0,0 +1,32 @@
+title: Validate max VGA dot clock
+team: MM
+key: 2f0026f2-80ea-11eb-8800-00e04c68641b
+status: Abandoned
+
+relationships:
+
+bsp41x:
+ - fccc46cf75fd45b867c8c8501c526a92efc4d49b # arm64: dts: r8a77995-draak: Set max dot clock for vga
+ - 64ee34a191cefc9fd10042f785996c811c336992 # arm64: dts: r8a77990-ebisu: Set max dot clock for vga
+ - a117af5977b652da0abece0b1a17049db4a76d09 # arm64: dts: salvator-common: Set max dot clock for vga
+ - ae5ed0b2888c3c084849e3b1b77001c4b3519f5d # drm/bridge: dumb-vga-dac: Add dot clock valid check
+
+upstream:
+
+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 copied from bsp392_validate-max-vga-dot-clock.yaml task
+
+ - Above patches moved to bsp-41x-non-target.yaml